Prepare redesign for public deployment
This commit is contained in:
7 files changed
+27
-7
No files matched your search
@@ -74,8 +74,10 @@ Then open:
|
||||
The app reads these from `.env`:
|
||||
|
||||
- `SECRET_KEY`
|
||||
- `APP_ENV`
|
||||
- `DATABASE_URL`
|
||||
- `APP_BASE_URL`
|
||||
- `RATELIMIT_STORAGE_URI`
|
||||
- `MAIL_SERVER`
|
||||
- `MAIL_PORT`
|
||||
- `MAIL_USE_TLS`
|
||||
@@ -84,6 +86,8 @@ The app reads these from `.env`:
|
||||
- `MAIL_PASSWORD`
|
||||
- `MAIL_DEFAULT_SENDER`
|
||||
|
||||
For public deployments, set `APP_ENV=production`. Production mode enables secure cookies and refuses to start with the development `SECRET_KEY`. Set `RATELIMIT_STORAGE_URI` to a shared backend such as Redis so login and signup limits are enforced across processes.
|
||||
|
||||
## Site Admin Access
|
||||
|
||||
Internal admin access uses normal database-backed accounts, not hardcoded `.env` credentials.
|
||||
|
||||
Reference in new issue
Block a user