I tested Coolify for a few weeks, and I can confirm that the name checks out. Highly recommend giving it a try. *** Update: I wanted to mention that adding WAF protection is worthwhile. You can route your Coolify domain through Cloudflare and utilize their free WAF protection at a minimum.
I must admit, this is the most thoroughly details Coolify installation tutorial out there on RU-vid, and I've seen A LOT of these recently. Thx for your dedication, @RaddyDev! Cheers!
Can you also show in your next videos how to set up a publicly-accessible postgres instance hosted on coolify? Maybe also set up a domain name pointing to that postgres instance using cloudflare tunnel or something so that the connection string doesn't have to depend on a static IP address? I've tried and couldn't get it to work.
I haven't tried setting up a tunnel, but the publicly-accessible Postgres worked for me. I had to open port 5432 and check the "make it public" option. Is that not working for you?
One addition: do not forget to update the password for coolify instance after you've set up HTTPS, because the first time you registered it was sent over HTTP and it is 100% logged somewhere in between your machine & hetzner instance.
That's a valid concern, thank you. If you set it up in public place, like a coffee shop where network traffic might be monitored, that could be a problem.
after applying firewall, I am not able to see the coolify using the ip as expected , but instead I can see the page saying 404 not found what does that mean? I mean isn't it just time out like in the video
After applying the firewall rules, accessing Coolify via the IP address should be blocked, which is expected behaviour. To access Coolify, use the domain name you have set up. If you haven't set up a domain name, you can unblock the port to continue using the IP address. That's what I've done in the video. Configure Coolify via IP -> Lock IP -> Use Coolify with a Domain. I hope that you've managed to set it up
With the Cloud, I guess you'll get to do less maintenance, free email notifications, and potential access to support. I haven't had to do much maintenance and I have no idea how good the support is. If you want to support Coolify and its creator, Andreas, choose the Cloud option. I personally have self-hosted everything on one server since I am only using it for personal projects. If you're using it for clients or important projects, separate servers are the best option. So, ask yourself if you need separate servers, free email notifications, less maintenance and support. That was a wordy answer, but I hope it helps. Let us know what you choose and why.
thank you and I agree with you. It took me a long time to figure out the Traefik redirect. The instructions in the the official documentation didn’t seem work for me
thanks for this very instructive video. So if I got it right, you should register a domain name for the Coolify instance, and then register domain names for every app running on this instance?
Thank you, I appreciate it. Yep, that's it. This way you can easily create websites with subdomains and also enables you to set up preview deployments for testing. Forgot to mention that it might make it easier to add WAF protection from platforms like Cloudflare.
Hey Raddy, you said you have three websites running on Droplet(server). How's that possible, when you have just one public ip address. Am i missing something
Yep, that's correct, you can host multiple websites on a single server. It works similarly to using Nginx, where you can have many domains point to one server IP. Nginx then handles directing traffic to the correct website. Coolify simplifies this process as it acts like a Platform as a service. Like Render and Varcel I guess. You simply create your websites within the platform, point your domain names to hosting IP, and Coolify takes care of everything. This includes routing traffic to the appropriate website, managing SSL certificates, and more
@@ALVIERIDEVELOPER Coolify uses Traefik as a proxy server to route traffic; it listens to incoming requests and, based on rules you set (like domain names), directs traffic to the right web service (e.g., React app on port 3000, Angular app on port 4200), acting like a traffic manager to ensure each request reaches the correct website. As for nginx it's more barebone from the get go, but it has a bigger community and you can configure it to your needs.
In my opinion, Vercel's DX is superior. They make deploying, debugging, and monitoring your application incredibly easy. There's no need to worry about server configuration, security, or scalability. Naturally, these benefits come at a cost. Coolify isn't serverless, but there are other options that you might want to explore like SST and AWS Amplify. SST is more technical, whereas Amplify offers a user experience somewhat similar to Vercel's. Currently, I use Coolify for most of my projects and find it quite nice. However, I wouldn't personally put a big client on it.
Amazing explanation, but i couldn't understand one thing that why do we need two domain names one for colify and one for the project, is it possible to not register colify with a domain name but only my project?
Technically, IP address will work for Coolify. Many server are managed that way, but domain names are easier to remember and look more professional if you care about that. The big thing for me was being able to easily create an application with a custom subdomains like analytics.mydomaincom without messing around too much. Oh and you get SSL on your coolify. Not sure how it works with the IP - it's probably fine. And thank you!
Perfect, this is what I needed to stop feeling paranoid about Vercel. Just one question: How can we achieve the same firewall behaviour of what Hetzner offers, but on some other VPS provider that doesn't have the any firewall features, so the firewall needs to be set up manually with something like ufw. But docker exposes the port 8000 even if you block it using ufw. Any idea?
Hard to say what it could be. If you haven't looked already, check out the logs when you deploy. Hopefully that will give you an indication of what it could be
Did you apply the firewall settings to your server? That's the only thing that I can think of if you followed along. A bit strange, let me know how it goes and if there is anything i can help with
It would be more or less the same. Let's say that you build your API with NodeJs, then the process of deploying will be exactly the same as the NextJs project
You can deploy PHP websites, but it relies on Docker compose for handling the development environment. You could look into some of the articles online on deploying Laravel websites. Maybe that would help clear things up. I haven't deployed any PHP applications on it yet, except for WordPress.
I wouldn't waste your time trying with less than the minimum requirements. The server will probably crash at some point. Ubuntu itself requires 1GB RAM and 1 vCPU or better.
There is a one click deploy option and SSL is automatically generated. I made a video on how I migrated pre-existing wp website and that covers the WP installation: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-wqyHFCu9bFM.html
I haven't used v2, but I do think the UI in v4 could be improved. It's not bad, but there is always room for improvement. With time, it will only get better.
There is an option called Preview Deployments which does that, but only works with Github. It's disabled by default, so you just need to go to Advanced and tick the box. You can configure the domain as well. Here is what the docs are saying: "Preview deployments are a great way to test your application before merging it into the main branch. Imagine it like a staging environment. URL Template You can setup your preview URL with a custom template. Default is {{pr_id}}.{{domain}}. This means that if you open a Pull Request with the ID 123, and you resource domain is example.com the preview URL will be 123.example.com." You can also create another website on coolify with a test/development environment and connect it to the branch you want.
When I create a new instance on Hetzner, it usually comes up to date. As you SSH there should be a message that the system is up to date as far as I remember. (It's most likely on the video when i ssh). It's still a good practice to manually check and run updates. If I log in now, I am sure that there will be some updates available to install. Coolify doesn't do ubuntu updates and with self-hosting, so you'll have to do the security yourself
