denshooter 30d0e597c2 fix: use production DB/Redis for dev deployment instead of non-existent dev containers ...

The dev-deploy workflow was trying to spin up separate portfolio_postgres_dev
and portfolio_redis_dev containers, which don't exist on the server. Now it
reuses the existing production portfolio-postgres and portfolio-redis on
the portfolio_net network.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

2026-03-04 15:09:04 +01:00

..

ci-cd-with-gitea-vars.yml.disabled

Updating (#65)

2026-02-15 22:04:26 +01:00

ci.yml

chore: add ci.yml to dev branch (Node 22, lint/test/build)

2026-02-25 12:40:47 +01:00

dev-deploy.yml.disabled

fix: use production DB/Redis for dev deployment instead of non-existent dev containers

2026-03-04 15:09:04 +01:00

production-deploy.yml

chore: re-enable production deploy workflow on production branch

2026-02-25 12:40:58 +01:00

staging-deploy.yml.disabled

feat: Setup zero-downtime deployments for production and dev branches

2026-01-09 14:21:03 +01:00