voussoir/ycdl
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
ycdl/frontends/ycdl_flask/ycdl_flask_prod.py

23 lines
655 B
Python
Raw Normal View History

Rename flask launchers -> _dev, _prod. I want to reduce some complexity around here, part of which is that launch imported entrypoint imported backend, all to do some proxy wrapping which isn't necessary for the dev case anyway. Less layers of wrapping and importing is good. Plus I think this naming is more clear. Additionally, I realized that the entrypoint aka prod launcher was never updated to init the ycdldb as that was only done by the argparse launcher. Now it's hardcoded and I'll consider adding a config file.
2020-09-30 22:03:29 +00:00
'''
This file is the WSGI entrypoint for remote / production use.
Move site.debug to _dev, _prod launchers.
2021-01-29 00:46:54 +00:00
Note that YCDL currenty features no authentication, so using it remotely without
another kind of access control is probably a bad idea!
Rename flask launchers -> _dev, _prod. I want to reduce some complexity around here, part of which is that launch imported entrypoint imported backend, all to do some proxy wrapping which isn't necessary for the dev case anyway. Less layers of wrapping and importing is good. Plus I think this naming is more clear. Additionally, I realized that the entrypoint aka prod launcher was never updated to init the ycdldb as that was only done by the argparse launcher. Now it's hardcoded and I'll consider adding a config file.
2020-09-30 22:03:29 +00:00
If you are using Gunicorn, for example:
gunicorn ycdl_flask_prod:site --bind "0.0.0.0:PORT" --access-logfile "-"
'''
import werkzeug.middleware.proxy_fix
import ycdl
Improve the way prod imports flask backend.
2021-09-09 02:33:05 +00:00
from ycdl_flask import backend
Rename flask launchers -> _dev, _prod. I want to reduce some complexity around here, part of which is that launch imported entrypoint imported backend, all to do some proxy wrapping which isn't necessary for the dev case anyway. Less layers of wrapping and importing is good. Plus I think this naming is more clear. Additionally, I realized that the entrypoint aka prod launcher was never updated to init the ycdldb as that was only done by the argparse launcher. Now it's hardcoded and I'll consider adding a config file.
2020-09-30 22:03:29 +00:00
backend.site.wsgi_app = werkzeug.middleware.proxy_fix.ProxyFix(backend.site.wsgi_app)
site = backend.site
Move site.debug to _dev, _prod launchers.
2021-01-29 00:46:54 +00:00
site.debug = False
Rename flask launchers -> _dev, _prod. I want to reduce some complexity around here, part of which is that launch imported entrypoint imported backend, all to do some proxy wrapping which isn't necessary for the dev case anyway. Less layers of wrapping and importing is good. Plus I think this naming is more clear. Additionally, I realized that the entrypoint aka prod launcher was never updated to init the ycdldb as that was only done by the argparse launcher. Now it's hardcoded and I'll consider adding a config file.
2020-09-30 22:03:29 +00:00
# NOTE: Consider adding a local .json config file.
Use worms, add more ycli functions.
2021-10-16 04:00:04 +00:00
backend.common.init_ycdldb()
Rename flask launchers -> _dev, _prod. I want to reduce some complexity around here, part of which is that launch imported entrypoint imported backend, all to do some proxy wrapping which isn't necessary for the dev case anyway. Less layers of wrapping and importing is good. Plus I think this naming is more clear. Additionally, I realized that the entrypoint aka prod launcher was never updated to init the ycdldb as that was only done by the argparse launcher. Now it's hardcoded and I'll consider adding a config file.
2020-09-30 22:03:29 +00:00
backend.common.start_refresher_thread(86400)
Reference in a new issue Copy permalink