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.
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 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 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 |
Deployment guides for popular programming stacks
Choose a step-by-step guide for the framework and language your project uses:
- Python and AI For Python web frameworks, see the guide to deploying Django, FastAPI, and Flask on Python hosting Deplomo.
- JavaScript and TypeScript Documentation Deploy a Node.js app For Express and NestJS, see the guide Node.js cloud hosting and the guide Deploy nextjs for server-side rendering with Next.js hosting Deplomo.
- Front-end and static sites For single-page apps, see the guide to deploy react For hosting HTML and CSS files, see the guide to Static site deployment static sites.
- PHP frameworks and modern languages Practical guide Deploy Laravel for business websites and documentation Deploy golang for compiled languages.
Production deployments and external dependencies
During a build, dependencies are fetched from the registries your project uses, including pip, npm, Composer, and Cargo. Check credentials, registry availability, and network requirements before deploying; third-party access policies still apply.
Deployment guide FAQs
Answers to common questions about deployments, cloud tools, and publishing software: