Applications & deployment
How services are defined, built, released and exposed on Notploy.
This section covers everything about turning a source into a running service: choosing where code comes from, how it is built, how it is configured and exposed, and how the deployment lifecycle behaves.
A service in Notploy is one of three kinds — an Application, a Database, or a Docker Compose stack — and all three share the same operational surface. This section is organized around that surface.
Start here
Sources & providers
GitHub, GitLab, Bitbucket, Gitea, Git URLs, images and uploads.
Build types
Dockerfile, Nixpacks, Railpack, buildpacks, or prebuilt images.
Docker Compose
Multi-service stacks from a compose file.
Databases
PostgreSQL, MySQL, MariaDB, MongoDB and Redis with backups.
Projects, environments and services
A project groups related services; an environment is the deployment context inside it (for example production and staging); a service is what actually runs. Configuration resolves from broad to specific — project, then environment, then service.
The deployment lifecycle
Every service moves through the same lifecycle:
- Source is fetched (Git clone, image pull, or upload).
- Build produces an image according to the service's build type.
- Release starts the new container as a Swarm service; the old one is drained.
- Route — Traefik exposes the service on its domains.
- Record — the deployment is stored with its logs and status.
Health checks, logs, rollbacks and zero-downtime behavior all attach to this lifecycle.
What you can configure on a service
All service types share these tabs, with the same meaning everywhere:
| Tab | Purpose |
|---|---|
| General | Source, build configuration and lifecycle actions (deploy, stop, delete). |
| Environment | Variables and secrets, addressed by scope. |
| Domains | Hostnames, ports and TLS. |
| Deployments | History, logs, cancel and rollback. |
| Logs | Real-time runtime output. |
| Monitoring | CPU, memory, disk and network. |
| Advanced | Commands, resources, volumes, ports, Traefik and cluster settings. |
Learn this surface once on an Application, and it applies to Databases and Compose unchanged.
Going further
- Environment variables and secrets across scopes.
- Domains and routing for Applications vs. Compose.
- Advanced settings for resources, volumes, ports and Traefik.
- Preview deployments and auto-deploy for automation.
- Scheduled jobs, watch paths and patches.
- Going to production — a checklist before you ship.
Keyboard shortcuts
Service pages support GitHub-style shortcuts: press g then a letter to jump to a tab
(g General, e Environment, u Domains, d Deployments, l Logs, m Monitoring, a Advanced).