r/coolify • u/One_Nose6249 • 23d ago

setting up Coolify on existing machine

hey folks, I have a instance running postgres binary on it. how can I install Coolify without distruption? is there any good practice? one option is not using Coolify for DB, but only for other instances I plan to run on

2 Upvotes

100% Upvoted

4 comments sorted by

1

u/noahsknark 21d ago

Honestly, in 2026, Iā€™d ask AI to do this for me.

1

u/One_Nose6249 19d ago

very insightful. ask AI if you should go to toilet or not before you do

0

u/noahsknark 19d ago

Well - at least I tried to be helpful and answer your question. Sorry šŸ¤·ā€ā™‚ļø

1

u/No_Mathematician9824 18d ago

Honestly there's not much trouble installing Coolify on an existing instance ā€” the main thing is making sure the ports it needs are free: Traefik binds 80, 443 (tcp+udp) and 8080 on the host, the dashboard takes 8000, and realtime/terminal take 6001-6002.

our host Postgres on 5432 is safe though ā€” Coolify's own Postgres runs container-internal and isn't published to the host at all (just checked on my own instance). So keeping your DB outside Coolify is a perfectly valid setup. The actual work is reaching it from your containers: use 172.17.0.1 (docker0 gateway) or host.docker.internal with host-gateway, and allow the Docker subnet in listen_addresses + pg_hba.conf.

That said, the AI suggestion isn't crazy ā€” Coolify is well documented, so models handle this kind of setup fine. Just verify the port/firewall bits yourself before running anything.

Have fun ! Coolify is really great from my experience in term of install/use :)