Publishing your project

Publishing the backend

Bring API, database, and services to dev automatically and to production with one click.

On this page
Prerequisites
Before your backend can go live, complete these steps: server setup (create a server and assign it to the project) and domain setup (for the production API domain).

Your backend (NestJS, FastAPI, or Laravel) runs as a Docker container on your server – together with the database (MySQL) and auxiliary services like phpMyAdmin.

How the deployment works

The flow is the regular Git workflow:

  1. Merge to main → the pipeline builds the Docker image (build-docker).
  2. Dev automatically: publish-docker-dev writes the new image tag into the dev configuration; the deployment runs to the server via Ansible.
  3. Prod with one click: the manual publish-docker-prod job releases the same state for production.

You manage environment variables and secrets per environment via the gitops-configuration repository – see Working with environment variables.

Your backend’s URLs

Environment URL
Dev backend.dev.<project>.<organization-domain> – assigned automatically
Prod Your own API domain from the project configuration
phpMyAdmin (dev) phpmyadmin.dev.<project>.<organization-domain>

See also