Paylood automatically detects the services used by your application (databases, caches, storage) and generates their Docker configuration.
Supported services
| Type | Examples |
|---|---|
| Database | PostgreSQL, MySQL, MongoDB |
| Cache / queue | Redis, RabbitMQ |
| Application | Node.js, PHP (Laravel), static frontend |
| Custom | Any Docker Hub image |
Configuring services
From the Database & Services step of the wizard, or the Services tab of the project:
- Enable/disable a service with its toggle.
- Change the image version (e.g.
postgres:16-alpine). - Adjust the exposed port and the entry path (for app services).
- Add persistent volumes.
Capture à venir
en/services-overview
Cette capture illustrera la vue correspondante. Elle est générée automatiquement par le pipeline Playwright.
Docker Hub search
Use the search field to add a custom service: Paylood queries Docker Hub, inspects the image and pre-fills the recommended ports and variables.
Tip
Image inspection happens in real time: exposed ports, declared volumes and suggested environment variables are filled automatically.
Global environment variables
Variables entered here are injected into all services. You can also import an existing .env file: it is parsed and every key is added.
Build artifacts (frontend apps)
For frontends, Paylood can:
- Build during deployment and serve the generated folder (
dist,build\u2026) through the web server. - Merge frontend + backend into a single Dockerfile when there is no separate domain.
Build options
- Always pull: forces pulling the base image on every build.
- Use cache: reuses the Docker cache between deployments (faster, disable to diagnose).
Scanning a new service on the server
If you added a Docker service manually on your VPS, open the project’s Services tab then Scan services: Paylood lists the detected containers and lets you integrate them into the project.
Services integrated by scan receive a default configuration (SERVICE_DEFAULTS) adapted to their type: PostgreSQL, Redis, MySQL, MongoDB, RabbitMQ.
Troubleshooting
- The image does not exist on Docker Hub: check the full name (
namespace/image:tag). - The service does not start: check the deployment logs and the automatic diagnostic.
- Port already in use: change the exposed port of the service or of the existing container.