Hugo and Astro produce nothing but static files when they build. A homepage-only project therefore gets by with an ordinary webspace with FTP or SFTP access, to which the platform uploads the built files.
This option exists only for projects without an app and without a backend, because apps and backends run as Docker containers and need one of the other server types.
Storing the access
- Open Servers in the sidebar and click Add server.
- Choose the Webspace (FTP/SFTP) tile.
- Choose the protocol, SFTP or FTP, and enter the host, user, port, and the remote path, for example
/html. - Choose authentication by password or, for SFTP only, by SSH key, and save.
SFTP with a password or key is the usual way; classic FTP supports a password only. When saving, the platform only checks that the fields are complete and plausible; it does not log in as a test, so a typo in the password only shows up on the first upload. The credentials are stored encrypted; afterwards the interface shows host, user, protocol, and remote path.
Selecting it in a project
When you create or edit a project that contains only homepages, choose Webspace (FTP/SFTP) under hosting and assign the stored access. If a project contains several homepages, they share the same remote path.
How the homepage gets onto the webspace
On every change to main, the pipeline builds the static site, the public/ folder for Hugo and dist/ for Astro, and uploads it to the remote path over FTP or SFTP. Docker images and GitOps deployments are skipped. If the upload fails, you find the error message in the GitLab job publish-webspace. How pipelines work in general is described under Git workflow and deployment.