Coolify

Appearance

No Vendor Lock-in ​

All data that is configured or used by Coolify is available on the host filesystem. If something goes wrong with Coolify, you will be still able to manage your applications.

This includes:

  • Deployment related configurations, like docker-compose.yaml files.
  • SSH related configurations.
  • Proxy configurations.

Persistent Directories ​

TypeHost SystemInside Coolify's container
Base/data/coolify/var/www/html/app/storage/coolify
Applications/data/coolify/applications/var/www/html/app/storage/coolify/applications
SSH related Configs/data/coolify/ssh/var/www/html/app/storage/coolify/ssh
Proxy/data/coolify/proxy/var/www/html/app/storage/coolify/proxy
Traefik Dynamic Configurations/data/coolify/proxy/dynamic/var/www/html/app/storage/coolify/proxy/dynamic

Applications ​

You can always find the latest successfully deployed application details.

bash
├── applications
│   ├── <uuid>
│   │   ├── docker-compose.yaml
│   │   ├── .env
│   ├── <uuid>
│   │   ├── latest
│   │   │   ├── docker-compose.yaml
│   │   ├── <deployment timestamp>
├── applications
│   ├── <uuid>
│   │   ├── docker-compose.yaml
│   │   ├── .env
│   ├── <uuid>
│   │   ├── latest
│   │   │   ├── docker-compose.yaml
│   │   ├── <deployment timestamp>

SSH ​

  1. Private SSH keys used to connect to Coolify's host server and all remote servers (/data/coolify/ssh/keys)
  2. Muliplexed SSH connection related temporary files. (/data/coolify/ssh/mux)

Proxy ​

  1. docker-compose.yaml file to manage the proxy. (/data/coolify/proxy/docker-compose.yml)

Traefik ​

  1. acme.json that has all the SSL certificates. (/data/coolify/proxy/acme.json)
  2. dynamic configurations, generated by Coolify or manually by you. (/data/coolify/proxy/dynamic)