Publish the backend

The pipeline builds a Docker image from your backend and deploys it to the server of the project; for production you need a domain for the API. The deploy flow is described in Git workflow and deployment.

What ships with the backend

The MySQL database runs as its own container on the same server, with its data stored under ./backend-mysql. In the project configuration you enable phpMyAdmin and Easy Backup. Traefik forwards the API domain to the container, and the platform sets up HTTPS.

Uploads

User uploads belong in ./upload locally and in /app/upload inside the container. On the server, the deployment mounts ./backend-uploads at this path. Multer, the FastAPI upload handler, or Laravel Storage must point to this path and not to directories such as user-uploads or /app/uploads. The generated Dockerfile creates the folder with RUN mkdir -p upload.

Configuration and secrets per environment

The configuration per environment lives in the gitops-configuration repository under configurations/. The platform maintains generated.yaml, including hostnames, the registry, and encrypted secrets. You add your own environment variables to custom.yaml under additional_env_variables; a commit to main of this repository rolls them out. The details are in Environment variables.

For sending email, you select a mail account from the Connections in the project, as described in Email delivery.

Your backend’s addresses

The platform shows the DNS records for the API domain in the domain detail; the steps are described in Configure DNS. A web app of the same project receives the backend URL through the generated env files (Publish web apps).

Errors appear in your Sentry project once you enable Sentry for the component under Features (Error tracking); how to take back a release is described in Operations.