GLWS · Containers
Deploy applications, databases and services using a self-hosted deployment platform.
Common uses of Coolify.
Plan persistent volumes, database backups and deployment credentials separately from the application’s source repository.
Planning examples, not official minimum requirements.
Containers
Check the current supported operating systems, deployment methods, dependencies and licence terms. What you need depends on your workload, not just the application's name.
Large datasets and busy workloads can need far more memory, storage or different hardware. Any external API or service subscriptions are separate.
Read the Coolify documentation ↗ (opens in a new tab)Advice specific to this application.
List the repository, build process, application runtime and persistent storage. A deployment host may need extra resources while building an update, even if the application is small once it is running. Budget for those temporary demands and review failed-build behaviour.
Repository tokens, environment secrets and access to the deployment dashboard can affect a live application. Restrict each to its intended role. Preserve application data independently and keep notes on how to rebuild the service outside the original dashboard.
Linux guides that help with this setup.
Add Docker's official repository, install the engine and Compose plugin, run a test container and avoid the published-port firewall trap.
Read guide →Proxy a domain to an app on a local port, issue a Let's Encrypt certificate with Certbot and confirm automatic renewal.
Read guide →Watch resource use with htop, run Uptime Kuma to check your sites and get disk-space alerts from a small scheduled script.
Read guide →Four steps that make the environment easier to maintain.
Read the publisher's instructions and choose a supported installation method.
Protect the dashboard, credentials and network endpoints before you expose any service.
Work out where the application keeps its state and store it separately from replaceable runtime files.
Back up the data and configuration, then check that you can restore them.
Run through it before and after you install.
$ application-checklist --name coolify
[ ] Supported deployment method
[ ] Authentication and access restrictions
[ ] Independent data backup
[ ] Updates and restoration tested
root@glws:~#
Quick answers before you choose resources.
No. The configurator only saves your application preference. It does not connect to any infrastructure or run an installer.
Use the planning example as a starting point only. Check the publisher's requirements and measure the whole stack under a realistic workload.
You do. Self-hosted applications need updates, configuration and recovery planning from the operator. The publisher's documentation describes supported maintenance.
The knowledge base covers Linux access, packages, services, firewalls and backups.
Other tools you might run alongside or instead.
Manage container environments through a browser-based administration interface.
Explore application →Website, email, DNS and database management in a hosting dashboard.
Explore application →A self-hosted assistant for connecting model-powered tasks with tools and messaging.
Explore application →An agent workspace for conversations, tools and automation on infrastructure you control.
Explore application →