chore: add isolated Academy staging environment#17
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 358b1c3e38
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| Run `docker compose -f docker-compose.staging.yml up --build -d`, then seed only the isolated staging database with `docker compose -f docker-compose.staging.yml exec app python server/seed_staging.py`. | ||
|
|
||
| Open `http://127.0.0.1:5180`. The development usernames are `academy-author`, `academy-reviewer`, `academy-publisher`, and `academy-admin`; the default passphrase is `FemmeVoice staging passphrase 2026`. Set `FEMMEVOICE_STAGING_PASSWORD` before seeding to change it. |
There was a problem hiding this comment.
When an operator follows this instruction and sets FEMMEVOICE_STAGING_PASSWORD in the host shell, the seed command still uses the default passphrase because the Compose app service neither declares that variable nor forwards it with exec -e. Add the variable to docker-compose.staging.yml or update the documented command to pass it explicitly; otherwise the advertised password override has no effect.
Useful? React with 👍 / 👎.
1 participant
Local Compose staging, guarded development accounts, and contributor documentation for the governed Academy workflow.