Document hot-reload workflow for AI agents
Rewrite SAAC_DEPLOYMENT.md to lead with the two-domain model: - Production (yourapp.<server>.domain.com) — updates on saac deploy - Hot-reload (yourapp-hot.<server>.domain.com) — auto-rebuilds on git push Added: recommended dev workflow (push → check hot → deploy to prod), nodemon.json explanation, development cycle diagram, customization guide. Updated Dockerfile and docker-compose.yml headers to explain which container uses which file and reference nodemon.json.
This commit is contained in:
@@ -1,6 +1,10 @@
|
||||
# Multi-stage Dockerfile for React + Express application
|
||||
# Multi-stage Dockerfile for React + Express application (PRODUCTION container)
|
||||
# See SAAC_DEPLOYMENT.md for deployment rules and common mistakes.
|
||||
#
|
||||
# This Dockerfile is ONLY used by the production container (yourapp.<server>.domain.com).
|
||||
# The hot-reload container (yourapp-hot.<server>.domain.com) does NOT use this file —
|
||||
# it mounts your source code directly and uses nodemon.json to watch for changes.
|
||||
#
|
||||
# Stage 1 (builder): Installs client deps and builds the React app with Vite.
|
||||
# Stage 2 (production): Installs server deps only, copies built React output.
|
||||
#
|
||||
|
||||
Reference in New Issue
Block a user