Plan CI/CD setup with cloud and hosting #171
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
- Define multi-environment strategy (dev/prod) with separate Supabase projects - Document GitHub Actions workflows for CI, dev deployment, and prod deployment - Include Netlify configuration with security headers and SPA redirects - Outline testing strategy with Vitest and React Testing Library - Plan future Docker containerization for self-hosted client deployments - Add implementation roadmap and rollback procedures
- Add CI workflow for PRs (lint, type-check, build, test) - Add deploy-dev workflow for dev branch deployments - Add deploy-prod workflow for main branch deployments - Add netlify.toml with SPA routing and security headers - Simplify deployment plan documentation
- Add Dockerfile with multi-stage build (node + nginx) - Add nginx.conf with SPA routing and security headers - Add docker-compose.yml for simple deployment - Add docker-compose.prod.yml with Caddy for automatic SSL - Add Caddyfile for reverse proxy configuration - Update deploy-prod workflow: build Docker → push to GHCR → deploy to Hetzner via SSH - Update deployment plan with Hetzner setup instructions Production architecture: - Docker image built and pushed to GitHub Container Registry - Automatic deployment to Hetzner server via SSH - Caddy handles SSL certificates (Let's Encrypt) - Supabase Cloud (EU) for database
- Add release.yml for manual releases with test → migrate → deploy sequence - Migrations require GitHub Environment approval for safety - Simplify deploy-prod.yml to just build and push Docker image - Update documentation with release process instructions Release workflow options: - run_migrations: Run database migrations (requires approval) - deploy_functions: Deploy Supabase Edge Functions
- Remove deploy-dev.yml (Netlify workflow) - Remove netlify.toml - Update docs: Lovable for dev, Docker for prod/local/on-premise - Add customer on-premise deployment instructions
- ci.yml: Remove dev branch reference (using Lovable for dev) - ci.yml: Use PROD secrets for build verification - Dockerfile: Add ENV declarations so Vite picks up build args - README: Add CI/CD section with deployment environments table - README: Link to CICD_DEPLOYMENT_PLAN.md in documentation list
SheetMetalConnect
force-pushed
the
claude/plan-cicd-deployment-01QEWidqmQKZJFNZtiVn9zd4
branch
from
61f1998 to
c6d31d1
Compare
SheetMetalConnect
deleted the
claude/plan-cicd-deployment-01QEWidqmQKZJFNZtiVn9zd4
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.