LanguageGB
App Deployment

Start from a working starter app

Deploy a small app we keep working for every runtime, check that it runs, then deploy your own code the same way.

What this covers

Our public repository cmcloudhosting-demo holds one starter per runtime: static, Node.js, FastAPI, Flask, Django, Laravel and Java. Each sits in its own folder with a README that gives the exact deploy-form values. Deploying one first shows the whole path working on your own plan (clone, install, build, health check and traffic swap) before your own code is involved. If your app then fails where the starter worked, you know the problem is in the app, not in the setup.

Before you start

You need an App Hosting plan or a free trial. Java needs App Business or higher and a managed PostgreSQL database. The repository is public, so no GitHub token is needed. PocketBase has no starter folder because it needs no code: see Deploy a PocketBase backend.

How to do it

  1. Pick the folder closest to your project: static, node, python-fastapi, python-flask, python-django, laravel or java.
  2. Open that folder's README on GitHub. It lists every field of the deploy form.
  3. In the portal, open your App Hosting service and go to the deploy form.
  4. Set Repository to https://github.com/cirro-admin/cmcloudhosting-demo and Branch to main.
  5. Set Subdirectory to the folder name, for example python-flask. For Java it is java/backend.
  6. Choose the Runtime and fill the remaining fields from the README, then click Redeploy App.
  7. Follow the deploy log: clone, install, build, start, health check, swap. Then open your app's address, and /api/info to see the runtime, memory and uptime the app actually has.
  8. To deploy your own code, set Repository to your repository. Empty Subdirectory if your app is at the root of your repository, and empty the Start command if a starter's README set one: emptying a saved field clears it. Your environment variables stay set.

Starter code and references

What our team checks

If a starter fails to deploy on your plan, that is ours to fix: open a ticket with the deploy log. If the starter works and your own app does not, compare your repository with the starter's README first. Most failures come down to the start command, the port or a missing environment variable.

Next step

Open the starter repository, choose the folder for your runtime and deploy it.

Contact Support