Harris
@harris-
migrated a lot of logic that I would otherwise run from vercel and github into a self hosted coolify + gitea running on that server as well. Can own the whole ci/cd pipeline without much hassle
2 replies
0 recast
11 reactions
Thomas Humphreys
@so
I have been eyeing coolify for a while now. How was your experience compared to vercel?
1 reply
0 recast
2 reactions
Harris
@harris-
It was an interesting setup to be honest. You need a private network like tailscale to set it up automatically I think since it requires you to login and setup over http before the SSL proxy is configured. You can add servers that are remotely accessible via ssh as it is so you could even run coolify itself off a pi and then add server to some remote instance somewhere that has nothing else running. That's my only kind of major complaint right now. On top of that, the wildcard ssl generation needs some config via the docker compose as well depending on the DNS provider. I ran gitea initially on a different port since 22 was taken via the server itself, but in hindsight this was a mistake as trying to deploy a private repo from the gitea instance also resulted in requiring git@ instead of ssh://git@ for a custom port. So I changed the VPS's ssh listening port to a different one and flicked gitea over to 22 instead. That's my experience so far but I'm sure I'll have more to talk about as I go
1 reply
0 recast
2 reactions
Harris
@harris-
I also don't really use vercel to the degree that would require me to host it all myself but I liked the idea of all my DBs and projects there. Let me know if you end up getting it setup or have any issues
1 reply
0 recast
2 reactions
Thomas Humphreys
@so
Super useful write-up – it sounds like you it wasn't a breeze as it required some config on your end. Never loved setting up SSL certificates, would've hoped that was easier than described. Did you not end up interacting with their frontend?
1 reply
0 recast
1 reaction
Harris
@harris-
Yep, to clarify about the SSL certificates: that's purely for wildcard domains to generate you a random subdomain for a project if you don't already have an A record or something, you can just set the A record to * and then have to do a little extra config (2 lines or something) in the traefik proxy's config. You still do it through the actual frontend, and there's only like 2 or 3 lines that they tell you where to find in the config so wasn't so bad. The only thing was I had to go digging for why it wasn't working in the first place, on top of restarting the actual ubuntu server a few times while trying to mess with ufw and docker compatibility. You can let it handle all the wildcard domains for you if you want to specify subdomains that are project specific, or you can just set up a domain that is completely unrelated as long as your DNS records point to the instance and the proxy should automatically fix it up
2 replies
0 recast
1 reaction
Harris
@harris-
The whole thing is listed here (ran out of room from my previous post): https://coolify.io/docs/knowledge-base/traefik/wildcard-certificates/
0 reply
0 recast
2 reactions
Thomas Humphreys
@so
> The only thing was I had to go digging for why it wasn't working in the first place Religiously following docs while piecing everything together, only to end up with no success is the very reason why I'm scared to touch Coolify (or most new products). Too many times have I burned through time trying to figure out what went wrong. I'll keep an eye on their github repo for updates until I dare myself to set-up. I'm looking to deploy some production code and unsure just yet about it. Will ping you when the time comes !
0 reply
0 recast
2 reactions
