- Notifications
You must be signed in to change notification settings - Fork17
Move to Django static assets.#96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
- removes uwsgi need for development- removes need for custom dev scripts- makes it more standard Django app
JelteF commentedNov 2, 2025
Let's keep this as is. The reason is indeed to not require an extra collectstatic command that's needed in the deployment. I don't control the deployment. |
simi commentedNov 2, 2025
This can be configured to work also without the special deployment step. The main motivation was to keep it as simple as possible and close to new Django project. For me it wasn't easy to follow how to run it locally, since the usual command was not working. Any idea who control the deployment? Happy to help there. |
I have no idea how app is deployed, happy to help changing deployment scripts to collect static files and expose over reverse proxy (or include static files serving to app in production non-debug mode).