Adding and starting a project

Existing code or a new template

Add a directory with a docker-compose.yml if you already have an environment set up. The panel detects the services and assigns a port. Port publishing is changed only at your request; the rest of the configuration stays yours.

For a new project, choose a template, for example PHP with MariaDB, Node, PrestaShop or WooCommerce. You get a directory with a Dockerfile, a Compose configuration, a place for your code and random passwords.

Start the project from the panel

Use the start button, including for the first start. The panel then configures publishing through nginx. A manual docker compose up on its own does not perform this part of the configuration.

The public port number and the internal Docker port are separate access points. The public port is served by nginx, with HTTPS and a password if you set one. The port registry prevents the same number from being assigned to different projects.

Keep the application separate from the configuration

In the templates, the web server serves the www/ subdirectory. The Dockerfile, the Compose file and the other environment files stay outside it. Put only content meant to be served by the web server in the public directory.

Databases and other services without a web interface should communicate by name on the Compose network. Do not publish them on 0.0.0.0. If you need access from the host, use 127.0.0.1:PORT:PORT. Generate passwords randomly, for example with openssl rand -hex 24.

Managing a running environment

• Start and stop run docker compose up -d --build and down respectively, with all profiles except one-off jobs.
• Restart is available in the Docker menu.
• Rebuild uses build --no-cache and blocks parallel builds of the same project.
• Logs show recent service events; the limit is 3 × 10 MB per container.
• The directory view gives access to the project files.

The progress of an operation is visible while it runs. After starting, open the application and check that it works as configured.