Hi excellent tutorial! question im work on aws but want to know do i need the second server is accessible with public IP ? So if I have to have several workers, will they all be displayed directly on the internet?
Check out one of my other videos. There you can see how to add a custom domain to a new app. I'm not familiar with Vercel. What type of users? Within Coolify or within the app that you're deploying? For example this video: ruclips.net/video/AQqlpj4HrGI/видео.htmlsi=STqtk9NoR1QeT9R_&t=55
Could work. I think one of the main things missing out from running it locally is the server monitoring. When a server goes does, to get notified about that. If your local computer is turned off and that would happen, you'd probably not get a notification about it.
@@360Creators Exactly, that's why I'd prefer running Coolify on a shared Intel vCPU and hosting multiple apps on a remote server with a dedicated vCPU, probably in the same location. I think this setup ensures efficient loading of the remote servers while providing enough capacity for smooth operation.
Hey just wanted to ask, If I run coolify on my local machine(my laptop) instead of a server and buy a single server to run my apps such as react and spring boot with postgres? Is it possible to do this with 2 core and 2gb/4gb ram?
Is it possible to auto scale based on load server is getting, one app sharing multiple servers to serve instead of what you shown in the video Thank you
I think what is important that you missed here is why you would want another server to spin up these services from than coolify itself. Otherwise great video.
I see! My main reason for it at this time is that I don't want Coolify to go down as soon as one of the applications crashes the server in which Coolify is on as well. Because then I can't manage the applications anymore such as removing it or whatever I think is needed.
This is perfect tutorial! thanks - one question, during purchasing the hetzner, could i use the same public ssh key that the coolify generated for the localhost (which is on another server), or better to generate a key for each new vps you add?
Yes I believe it still is in beta. I'm not sure if it's production ready, I guess that also depends on what you have in mind for your projects. If you'd like to have applications deployed for clients, you can turn off auto update for that app, to keep something working for long period of time.
Thank you for sharing, Crystal clear tutorial.
massively underrated video. Keep to good work
Thank you man!!
Thanks for sharing - this is just what I needed!
Glad you like it!! 😁
Thanks for this, was looking for how to setup a second server with coolify residing on a dedicated machine!
Awesome, glad it was helpful 😁
Man! What an awesome tut. Subscribed
You're totally welcome 😁
wonderfully clear walkthrough, thanks!!
Nice!! Glad it's appreciated, you're welcome!! 😁
Thank you so much, need more content of coolify
You're welcome! 😁
Thank you so much !! really needed this
Nice!! Glad to read that 😁
Hi excellent tutorial! question im work on aws but want to know do i need the second server is accessible with public IP ?
So if I have to have several workers, will they all be displayed directly on the internet?
I don't know, maybe the (discord) community can help out here.
Thank u man! I love uuu
You're welcome! 😁
thanks alot my man😁
You're totally welcome 😁
Is there a way to put a load balancer in front of both coolify servers and have an automatic failover if one goes down ?
Maybe, but I don't know that yet.
Thanks for the tutorial! Is there a specific reason for disable cloudflare proxy on the DNS A record?
No, I've followed that from other tutorials. There's probably some logic to it, but I wouldn't know.
Thanks!
You're welcome! 😁
please can you make video on how we add domain to each new app, and if we can make users to create their account like vercel
Check out one of my other videos. There you can see how to add a custom domain to a new app. I'm not familiar with Vercel. What type of users? Within Coolify or within the app that you're deploying?
For example this video: ruclips.net/video/AQqlpj4HrGI/видео.htmlsi=STqtk9NoR1QeT9R_&t=55
Is it a bad idea to set up Coolify on a local computer and deploy apps on Hetzner? What are the pros and cons?
Could work. I think one of the main things missing out from running it locally is the server monitoring. When a server goes does, to get notified about that. If your local computer is turned off and that would happen, you'd probably not get a notification about it.
@@360Creators Exactly, that's why I'd prefer running Coolify on a shared Intel vCPU and hosting multiple apps on a remote server with a dedicated vCPU, probably in the same location. I think this setup ensures efficient loading of the remote servers while providing enough capacity for smooth operation.
yes it's a bad idea, if your home computer is not open 24/7
I run it on one of my home servers, just the Zimaboard single board computer. Runs 24/7 very efficiently and silently.
Hey just wanted to ask, If I run coolify on my local machine(my laptop) instead of a server and buy a single server to run my apps such as react and spring boot with postgres? Is it possible to do this with 2 core and 2gb/4gb ram?
I don't know, maybe the (discord) community can help out here.
Is it possible to auto scale based on load server is getting, one app sharing multiple servers to serve instead of what you shown in the video
Thank you
I don't know! Maybe someone else might have the answer for you here or in the discord community of coolify
I think what is important that you missed here is why you would want another server to spin up these services from than coolify itself. Otherwise great video.
I see!
My main reason for it at this time is that I don't want Coolify to go down as soon as one of the applications crashes the server in which Coolify is on as well. Because then I can't manage the applications anymore such as removing it or whatever I think is needed.
I learnt the hard way. Yep.
This is perfect tutorial! thanks - one question, during purchasing the hetzner, could i use the same public ssh key that the coolify generated for the localhost (which is on another server), or better to generate a key for each new vps you add?
Glad you like it! I'd say it's better to generate a key for each new vps.
Topper!
😁
Coolify still in beta version? It possible to use in Production?
Yes I believe it still is in beta. I'm not sure if it's production ready, I guess that also depends on what you have in mind for your projects. If you'd like to have applications deployed for clients, you can turn off auto update for that app, to keep something working for long period of time.
@@360Creators yeah definitely will give it a try
@@noahperez9631 Awesome!