ai_ml_operations/print_forge
2
0
Fork 0
generated from westfarn/web_django_template
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Point CI and deploy at app_catalog.print_forge on master.

Browse Source 
Gitea was still targeting main and a leftover client-ci compose name, so PRs and server-infra --app print_forge would miss each other.
This commit is contained in:
westfarn
2026-09-06 20:31:42 -05:00
parent 9f2d349974
commit 5ea7cce56b
5 changed files with 9 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+3 -1
View File
@@ -45,7 +45,9 @@ cp .env.prod.example ~/Documents/secrets/print_forge/print_forge_prod.env
./scripts/validate-env.sh ~/Documents/secrets/print_forge/print_forge_prod.env
```
Infra: Postgres on 10.0.0.230, server-infra app_catalog, NPM, CI.
Infra: Postgres on 10.0.0.230, server-infra `app_catalog.print_forge`, NPM, CI.
Gitea deploy calls `deploy.sh --app print_forge` (must match that catalog key).
Secrets: `~/Documents/secrets/print_forge/print_forge_{prod,beta}.env`.
Create a portal user with `createsuperuser` after first deploy.
## Stack