feat(deploy): voie de déploiement VPS + build partagé - #71
Merged
Conversation
Calqué sur ai-driven-dev.fr : build+signe en cloud GitHub (clé privée jamais sur le VPS), image nginx statique poussée sur GHCR, runner self-hosted fait docker compose pull+up. Gaté workflow_dispatch tant que le VPS n'est pas câblé ; Pages reste actif. Extrait l'assemblage dans build-site.sh (partagé Pages/VPS). Dockerfile+nginx.conf+compose testés en local (endpoints, content-types, CORS, healthcheck). docs/DEPLOY-VPS.md pour les étapes VPS et la bascule. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Prépare le passage à l'hébergement VPS (tout sur le site), en calquant
ai-driven-dev.fr. Pages reste actif ; la voie VPS est gatée.Sécurité (le point clé)
Le build+signe tourne sur un runner GitHub-hosted (env
signing) : la clé privée ne touche jamais le VPS. Seule l'image nginx (sortie publique_sitesignée) est poussée sur GHCR ; le runner self-hosted[self-hosted, aidd-central]faitdocker compose pull && up. GitHub jamais sollicité par un visiteur.Contenu
Dockerfile(nginx:alpine sert_sitesur 8080) +nginx.conf(content-types mjs/jwt/json, CORS) +docker-compose.yml. Testés en local : endpoints 200, types corrects, CORS, healthcheck healthy.deploy-vps.yml(gatéworkflow_dispatch) : build+signe → GHCR → deploy self-hosted (healthcheck + smoke test). Actions figées par SHA..github/scripts/build-site.sh: assemblage extrait, partagé par Pages et VPS (évite la divergence). emit-and-deploy refactoré pour l'appeler. Testé (membre de test → _site correct).docs/DEPLOY-VPS.md: étapes côté VPS (compose, reverse proxy, DNS) + bascule Pages→VPS.Rien ne casse
Pages continue via
emit-and-deploy.yml(utilise le mêmebuild-site.sh). Le VPS ne se déclenche que manuellement, tant que le collègue n'a pas câblé compose + reverse proxy + DNS.🤖 Generated with Claude Code