Deployment guides # Deployment guides for every language and framework Practical guides to deploying Python, Node.js, Laravel, Go, Ruby, Rust, React, Next.js, Vue, Svelte, Astro, and static sites on Deplomo, from Git to a custom domain and SSL. [## Deploy cloud containers Compare cloud container platforms by price, scaling, Git and Docker deployment, databases and support. Use a real workload to assess the fit.](/guides/cloud-containers) [## Deploy Monorepo Turborepo, pnpm workspace and multiple services from one Git repository](/guides/deploy-monorepo) [## Deploy Python Django, FastAPI and Flask](/guides/deploy-python) [## Deploy Node.js Express, NestJS and Fastify](/guides/deploy-nodejs) [## Deploy Laravel and PHP Laravel, PHP and Artisan](/guides/deploy-laravel) [## Deploy Go Gin, Echo, Fiber and net/http](/guides/deploy-go) [## Deploy Ruby Rails, Sinatra and Rack](/guides/deploy-ruby) [## Deploy Rust Axum, Actix Web and Rocket](/guides/deploy-rust) [## Deploy React React, Vite and SPA](/guides/deploy-react) [## Deploy Next.js SSR, App Router and API Routes](/guides/deploy-nextjs) [## Deploy Vue and Nuxt Vue SPA and Nuxt SSR](/guides/deploy-vue) [## Deploy Svelte and SvelteKit Svelte SPA, SvelteKit SSR and static sites](/guides/deploy-svelte) [## Deploy Astro Astro static and SSR](/guides/deploy-astro) [## Deploy Static website HTML/CSS/JS, Vite and Static Generators](/guides/deploy-static-sites) ## Deployment guide: prepare your code and deploy it to a stable cloud environment A key stage in the software development lifecycle is moving code from a developer’s local environment to production. New developers often ask what deployment means and what it takes to make an app available on the web. Deployment turns source code into a running service that can reliably respond to user requests. Modern PaaS platforms automate work that once required configuring web servers, firewalls, and databases by hand. ### Key steps in the project deployment process Follow these basic practices to help your software keep running reliably when you deploy a project: - **Manage dependencies and packages:** Keep standard package manager files, such as package.json, requirements.txt, composer.json, or Cargo.toml, in the repository root so the cloud platform can prepare the right runtime environment. - **Keep environment variables separate** Do not store secret keys, database connection details, or private URLs in your code. Set them as environment variables instead. - **Set the PORT variable** Modern web servers should read the listening port from the PORT environment variable and bind to 0.0.0.0 so they can receive traffic from the cloud network. ### Deploying software on a cloud platform vs. traditional hosting With traditional hosting, deploying software meant signing in to a control panel such as cPanel or connecting to a Linux server over SSH to run web server commands by hand. This made mistakes more likely and scaling up during traffic peaks difficult. With [PaaS service](/products/paas) Deplomo, each push to a Git repository or CLI command can trigger an automatic deployment. For details about the platform, see the [PaaS deployment guide](/support/docs/paas) is available to you.
| Deployment criteria | Deplomo cloud platform | Unmanaged VPS | Traditional hosts (cPanel/DirectAdmin) |
|---|---|---|---|
| Deployment method | Connect Git or use the Deplomo CLI | Manual SSH commands or complex CI/CD setup | Upload files manually with FTP or a file manager |
| Health-checked deployment rollout | Built-in support | Requires complex rollout and proxy setup | Uploads may interrupt service |
| SSL certificates and domains | Automatic issuance and renewal | Install Certbot and renew certificates with cron jobs | Configure manually in the control panel |
| Scaling resources | Plan resources within fixed package limits | Upgrade hardware and restart the server | Buy a more expensive annual plan |