Going Live
Guidance on deploying SolidX applications to production environments.
Mental Model
Going live with SolidX is about making a working full-stack application repeatable, secure, and operable in a real environment.
- You are deploying both the backend and frontend parts of the application.
- You are also carrying across environment configuration, database access, networking, and operational controls.
- The right deployment path depends more on your infrastructure model and team workflow than on SolidX itself.
These guides are not prescribing one "correct" production shape. They help you choose the deployment model that fits your hosting and operations posture.
This section covers the main production deployment shapes used with SolidX, from traditional virtual machines to container-based platforms.
Deployment Paths
Solid App Template
Start from the generated create-solid-app project shape and choose between a manual runtime or Docker-based deployment.
Virtual Machine
Deploy on a traditional VM with direct control over the host, process management, Nginx, SSL, and runtime operations.
Amazon ECS
Run SolidX on AWS Fargate using containers, ECR, task definitions, services, and load balancing.
Docker
Containerize the application for a reproducible deployment workflow using Dockerfiles and Docker Compose.
Choosing the Right Guide
Use the guides based on the operational model you want:
- Start with Solid App Template when you want the deployment paths explained from the generated project structure.
- Choose Virtual Machine when your team wants direct control over Linux, process management, reverse proxying, and TLS setup.
- Choose Docker when you want a portable runtime definition and a reproducible way to move the same application shape across environments.
- Choose Amazon ECS when you want container-based deployment on AWS without managing the underlying servers directly.
Each guide assumes you already have a working SolidX project and are now deciding how to run it safely in production.