Before you start
- The current Kule release installs only Dokploy when you add a server.
- The Coolify option sits in Ayarlar (Settings) marked yakında (coming soon): “Dokploy dışındaki motorlar bir sonraki sürümde” (engines other than Dokploy in the next release).
- If you want Coolify now, see the last section below.
What works today
Every server you add to Kule goes through the connection, the checks and the protections (firewall, fail2ban, automatic security updates, swap, time zone, key-only SSH). At the platform step, the interface installs Dokploy; there is no place to choose Coolify yet.
Everything about Dokploy, from setup to connection and updates, is in the Dokploy guide.
What is ready inside Kule
The part that installs Coolify and talks to the Coolify v4 API is written in Kule’s core. When it reaches the interface, on an empty server it will:
- Set up the protections as with Dokploy, and install Docker. Since Coolify doesn’t use Docker Swarm, the Swarm step is skipped.
- Install Coolify with its official install script. It creates the admin account during installation with the environment variables Coolify supports; it generates the password itself and stores it in the Keychain.
- Wait for the panel to respond at http://203.0.113.24:8000.
curl -fsSL https://cdn.coollabs.io/coolify/install.sh -o /tmp/coolify-install.sh ROOT_USERNAME=kule ROOT_USER_EMAIL=… ROOT_USER_PASSWORD=… bash /tmp/coolify-install.sh
If you want Coolify now
You can install Coolify yourself with its own official command, as root on the server. The minimum Coolify itself recommends is 2 cores, 2 GB of memory and 10 GB of disk.
curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bashDo this knowingly: the current Kule release doesn’t connect to or manage this Coolify. Don’t have Kule install Dokploy on the same server either; both platforms need ports 80 and 443. If one of these ports is taken at the check step, Kule tells you which one and stops. If you want to try Kule with Dokploy, use a separate, empty server.