This tool makes self hosting simple
ฝัง
- เผยแพร่เมื่อ 10 เม.ย. 2024
- checkout coolify.io/ if you want an easier way to self host on a VPS.
My Products
📖 ProjectPlannerAI: projectplannerai.com
🤖 IconGeneratorAI: icongeneratorai.com
📝 ThumbnailCritique: thumbnailcritique.com
Useful Links
💬 Discord: / discord
🔔 Newsletter: newsletter.webdevcody.com/
📁 GitHub: github.com/webdevcody
📺 Twitch: / webdevcody
🤖 Website: webdevcody.com
🐦 Twitter: / webdevcody
![[TH] VCT Pacific Stage 2 - Week 4 Day 3 // GEN vs TS | PRX vs ZETA](http://i.ytimg.com/vi/nspkjQuZve0/mqdefault.jpg)
Thank you for making a video about it! (the dev behind Coolify here). 💜
Awesome tool, man!
Big props to you!
Man this feels like a lifesaver can't wait to try it out!
Bro you have no idea what you have made, its gonna be life saver for lot of devs like me
Sure thing man, thanks for making it
You're so cool!
Wake up, babe! A new video from Cody just dropped.
😄
I'm just toying with coolify and here you are, dropping the video about it, thanks
As much as I am used to manually configuring everything this looks like a super easy and fun way to just get started with a project
You can also use it to self host open source projects like plausible analytics, supabase etc
thanks for sharing! It looks like a very handy tool when you want to manage your own server and deploy something quickly
Thanks a lot this feels like a lifesaver!
Great video as always, would love to see tutorials on more advanced routing strategies. Such as multiple website on same VPS and other advanced mechanism ( if it's even recommended )
Nice! Basically the architecture of Dokku with the UX of Vercel. I'm a fan.
Gold, thank you sir
very cool, thanks for sharing!
i knew this was coming :) glad others are trying coolify as well. lets take back our servers :)
Thanks for this cool piece of information.
Welcome to the world of self-hosting!
thanks for sharing! I'm curious, when you switched to VPS, did you have to change any SST-related code like how you fetch secrets or binding resources like bind: [table]?
I removed all the sst stuff when I moved to a vps
@@WebDevCody Thanks, makes sense!
Thank You
What about private repositories ? Do we have to add tokens in the coolify dashboard or we have to set it up manually in the vps like the old days ?
I saw a private repo option, so I assume they have a way to setup tooens
I've been waiting for the Cody x Coolify collaboration for a while. Glad to see it's here :)
#teamcoolify 💜
FYI, for anyone who has their NextJS project in a sub folder, it won't work. Make sure your app's main folder is the root folder.
Ex: Don't use a project like 'my-app', and its sub folder is also 'my-app' which has the contents of your git repo's application.
thanks man
How does this tool get along with gitlab ci or github actions?
next video: builds homelab and leaves digital ocean
Hey! Thank you! Could you please tell me your camera and mic setup ?
iPhone for camera and 990mxl for mic
The best thing about Vercel is their Edge Network 😂
Can you have an HA setup with a load balancer in front? Is it out of the box functionality or do we have to do this ourselves with multiple instances of coolify?
I don’t really know. I spent 30 minutes trying this out
tbh using the Home Assistant OS on a dedicated pi or nuc is the way to go. Especially if you plan on hooking in any hardware
Please elaborate? That sounds intriguing@@wchorski
It is possible to customize it for the Node.js application to run in cluster mode, isn't it? I want to utilize all CPU power, previously when I deployed using pm2, there would be an additional option '-i max'
I’m not sure with this tool, but it uses a customizable tool called nixpack which probably allows running with pm2
Could you add monitoring, metrics, CDN to that Coolify instance to make it work similarly to Vercel
I too I'm wondering about the CDN. For static assets will it deploy to S3/cloudfront? This is how vercel basically works.
I have watched all deployment from you and it’s awesome. I do have to ask this question as a noob but why not deploy nextjs on cloudflare?
Is that even possible? I didn’t look into it
@@WebDevCody yeah you can.
4:23 - don’t think that’s a bug, you have to press the save button
Oh ok nice
very nice
How do you set the port? just leave it at 3000? After setting the A record, the server always show bad gateway. Not sure why。
I don’t rememebr needing to set one
Been trying to figure this out on my raspberry pi but cannot get the dns options to work. On a vpc it works fine but a local pi seems to have an issue about something
How does this compare to K3S and ArgoCD? Couldn't you do almost the same thing, with the exception, that Coolify also builds a container? K3S seems less resource hungry + you get the access to the Helm ecosystem. Am I missing something?
It seems Coolify automatically builds your image and also can hook into GitHub webhooks
@@WebDevCody Ok, so a bit simpler than a K3S setup and maybe more resource hungry. Good trade off for self hosting hobby projects if you don't want to dive deep into Kubernetes. I like it :) Does it come with "observability" included, or do you have to tag that on also?
Do you have a good source for the k3s and argocd setup? I'm using caprover (something similar to coolify) at the moment, but want to try other things also :)
@@easylite376 would be interested too
I always wanted to use something like this.
What about Dockploy ?
hey cody, have you used umami?
Never heard of it
@@WebDevCody *umami analytics
Can I run WordPress as well?
How did you get that TLS to work?
it is probably using Let's Encrypt under the hood, so I don't need to do anything
So this is kinda like Portainer?
Yeah, looks pretty similar feature-wise
Tried this earlier, but the biggest pain in the ass for this was to setup the proxy settings for this.
Once its deployed, the actual site itself will lack Lets Encrypt certificates, so it makes the end result website deployment absolutely useless. Just use Vercel, and point it to your actual domain.
I didn't have issue setting up the certs
@@WebDevCody I just wish it were automatic.
Looks convenient af, if it doesn't break unexpectedly. Personally I had some horrific experiences with traefik so I avoid it like the plague.
may i know what that horrific experiences are
@@henri470x A functioning setup would randomly cease working (good luck troubleshooting that). I found configuring traefik confusing and seemingly arbitrary. Documentation often contradicted tutorials, making it difficult to trust either. No matter how much I delved into the docs, it felt more like memorizing trivia than gaining any understanding.
Spent weeks with Traefik, I gave up and switched to HAProxy. Setting up HAProxy took a few hours, and everything worked.
Did enabling the CF proxy cause issues for you?
I never tried, I just used the dns not the proxy
@@WebDevCody got it. id also recommend you harden your ssh config if you are planning on keeping this around.
@@peteredmonds1712 I’ve already deleted it, but if I use this in prod I’ll read more on it
@@WebDevCody got it. id also recommend you harden your ssh config if you are planning on keeping this around.
Network Engineer here, why use this instead of just docker itself and portainer if you want a gui? I have my own dell servers at home for fairly cheap and am self hosting everything, if I need a VM I just create it using my terraform template and it's ready to go in minutes. I feel that adding additional layers on top of the underlying technology here is a bit wasteful resource wise and docker is simple enough to learn if this is the end goal but perhaps I am missing some feature that coolify is more targeted towards.
You know when you get to that point where you’ve already spent years learning something where everything seems easy? I think you’re at that point. I think coolify is geared towards someone who doesn’t want to dive into learning docker, terraform, setting up cicd pipelines with GitHub webhooks to auto deploy on commits. I think coolify already supports scaling out to multiple nodes out of the box
@@WebDevCody That might very well be the case, but I also feel like I am still learning something new everyday, not sure if that ever goes away as I am still fairly early on in my career.
Isn't db in instance a bad practice?
What’s bad about it? As long as you have backups you should be fine. Also keeping the db on the same machine as your web server will results in no latency due to network requests. For a majority of small or medium traffic apps, it’s fine
@@WebDevCody Yeah I feel like I've been scared off this by FE devs that are perhaps more wary of running a db. I'm definitely tempted to do this.
This is false and it comes from heavy marketing from db service sites!
Wasn't this practice common in nearly every PHP website?
Previously I also used to think like this (I am working in small company)
Then my boss told to deploy mongodb on machine.
I am working from 8 month, literally nothing happens.
Just keep backup of everyday.
Game changer
why disable proxy in cloudflare? 4:00
Not sure usually I keep it on
@@WebDevCody Oh okay, I thought there was reason to disable it.
Why would I use this over kubernetes?
It auto builds your images and hooks into GitHub to auto build
Beyond that does it provide the resiliency that kubernetes does? In kubernetes if a pod goes down it'll reschedule it. How does this product do that?
How I miss just FTPing and drag and dropping files into the server
Me too. Too much complexity these days
Portainer +
us this any more useful than portainer
It is easier than ever to self-host. Meanwhile, we are told more than ever by "Merchants of complexity" that it is harder than ever and that we are screwed without their overpriced services.
I mean, hosting a single app on a vps has been easy for 10 years now ever since caddy, lets encrypt, and docker came out. The annoying part is having a robust monitoring and centralized logging setup (which is also easy now because of docker and the abundance of blog posts walking everyone through how to do everything)
@@WebDevCody is there one you recommend?
Oh no... The beard :(
bro I remember when self hosting meant ur own servers...
Serverless?
Serverless adds more complexity imo
@@WebDevCody Until you add k8 in your VPS 😂
@@oscarljimenez5717 I run k8s in serverless to make it less complex
why is needs 30+ GB of storage for the images ??? that's absurd
Docker
why the hell does it need 30gb of storage lmao
Docker
Yeah like Cody said, they want plenty of padding for their Docker images (which typically are pretty large)
"self hosting" using homosexual cloud providers . Where did we devs go wrong
Just why? Grab a node container in docker, add git clone & and build lines to docker compose. And you are done. You failed to explain, why this is better, then anything else.
this can already hook into your git repo and redeploy on code changes, has ssl certs already setup, has the ability to setup a database with a button click. but yes if you want a script to ssh into a machine, git pull latest changes, and re-run docker build + docker compose you can do that. at that point it feels like you are reinventing the wheel
How is that self hosting? It's on digital Ocean...
Self hosting includes renting a vps. No one actually buys servers and hosts from their own facility, and hosting from you house isn’t a real solution
self-hosting = managing your own server
@@WebDevCody Well I have rent servers and VPS for 20 years. Moves to the cloud 3 years ago. And that was not called self hosting. So how do you call hosting on you own server. On a home computer? You say it isn’t a real solution but I disagree with that, local first is growing, the decentralized web too, but whatever. How is it called since people are now using self hosting for regular hosting? Calling hosting "self hosting" just sound strange.
Your server can be anywhere. In fact, Coolify now offers an option to deploy your stuff to your own servers at home. Self hosting just means you manage your own software on the server, even if you are renting the server a data center. I know the term self-hosting is a bit ambiguous.
@@NicholasMaietta Oh that's interesting. I'll give it a try. Thanks.