Awesome video! I'd love to see more detail on best practices for backups and recovery workflows on coolify generally. Hetzner persistent volume usage? S3 backups? etc
What are the limitations of the self hosted use case, versus the paid one? I have been looking for a comparision table but couldnt find it. On Reddit people complain self hosted is very limited, but these are a year old messages as well so things might have changed
Biggest advantage for any opensource that can be paid to have it on their cloud is that you don't have to worry that much about updates and you get support. Usually it all depends on your own experience. I'm myself still exploring both sides at this time.
great video i notice you are using coolify v3, I assume that is because v4 is only on beta? Also have you used something like data grip to connect to that db? Thanks for the video
I'm working on a self-hoisted machine on my own network, not a VPS in the cloud. Coolify wants Supabase to listen on port 8000. It is set where you set the domain. However when I access it from the outside it seems to be mapped to port 443. I point this out because when I do log in with the credentials, it eventually time out with no response. I don't know if I'm having some kind of port mapping and/or firewall problems. Any thoughts?
443 is SSL. So when you hit a site with it will go to 443 by default unless you add a :8000 after example the IP. But what you actually want is to have something that maps the the domain to the ip which refer to your service at 8000. So for me it would be a Nginx-Proxy Manager-server with firewall open to 443... which when a domain hits it, it will route to specific local-ip:port ... you could have other services than just nginx doing this, you could use something like Traefik as well.
This works great. But the endpoints don't have SSL when specifying a custom domain. I'm guessing we need to modify the docker compose to enable SSL on kong?
More to come!!@@haidarezio Also looking for some coolify experts that have some time to help me out, so that I can create more and faster tutorials. If you happen to know them.. 😁
I wish i could help in that regard @@360Creators, I'm in their discord talking to other folks about setting up portainer and some monitoring for the VPS, but i went with netdata, super nice to have as well but yeah most of my knowledge there is me going through discord threads and old messages for some small bug fixes xD
You're welcome! 😁 You can have a minio bucket storage using coolify. Video is a bit long, but you can skip to the parts which contains minio content. ua-cam.com/video/bnDhW1eTHnw/v-deo.html
Depends on the server. For this tutorial I thought it was easier to have an external one for it to deactivate after this tutorial. And what jaradaty88 says, I think it's good practise to seperate coolify from other apps. If one of the apps makes the server crash, you can still access coolify to throw it off the server.
One confusing thing is, when you point your domain to the Supabase instance in coolify you can access your dashboard as intended but then I run into all sorts of CORS errors when trying to interface with the storage frontend, as changing the domain on the studio/Kong doesn't change the other urls/certs for api endpoints.
Mmm I haven't had that yet, also haven't played enough with the Supabase at this point. What I think that might help is to go within Service Stack > Edit Compose File and then search for the domain it's currently incorrectly pointing to. And then replace that with the custom subdomain and try again by clicking Pull Latest Images & Restart.
@@360Creators I tried this and couldn't find a way to get it to work. I may have missed something. I think it has to do with the proxy/router that coolify implements but not sure. Honestly gave up lol, just going to use minio and postgress. Would be cool to be able to quickly spin up something like supabase though.
Hi, thank you for video, but i can't understant, what wrongs Saved configuration files to /data/coolify/services/jo0kc40. Creating Docker network. Starting service. Pulling images. validating /data/coolify/services/jo0kc40/docker-compose.yml: services.realtime-dev Additional property supabase-realtime is not allowed can't to deploy supabase
I'm sorry to read that. I'm not at the stage of understanding these types of errors yet. Better to check in with the Coolify discord community. I feel that it could be really nice if there were some developers specialized in Coolify to offer some support service to help with these type of things.
Awesome video! I'd love to see more detail on best practices for backups and recovery workflows on coolify generally. Hetzner persistent volume usage? S3 backups? etc
Me too, haven't figured that out yet.
The best coolify guides I've found, thanks!
Amazing! 😁 You're welcome!
wow! I'd like to ask if it's possible to host multiple projects within a single Supabase instance on Coolify. thanks!
Thank you for this ! would love to know if it's super easy to have a next app with image optimization enabled,
You're welcome man! Not sure about that, probably better to check in at the discord community of coolify!
What are the limitations of the self hosted use case, versus the paid one?
I have been looking for a comparision table but couldnt find it. On Reddit people complain self hosted is very limited, but these are a year old messages as well so things might have changed
Biggest advantage for any opensource that can be paid to have it on their cloud is that you don't have to worry that much about updates and you get support. Usually it all depends on your own experience. I'm myself still exploring both sides at this time.
u get all that bandwidth for dirt cheap with self-hosted tho.
How to connect to that postgres instance?
great video i notice you are using coolify v3, I assume that is because v4 is only on beta? Also have you used something like data grip to connect to that db? Thanks for the video
v4 wasn't there 3 months ago. I haven't used something like data grip. Glad you like the video!
I'm working on a self-hoisted machine on my own network, not a VPS in the cloud. Coolify wants Supabase to listen on port 8000. It is set where you set the domain. However when I access it from the outside it seems to be mapped to port 443. I point this out because when I do log in with the credentials, it eventually time out with no response. I don't know if I'm having some kind of port mapping and/or firewall problems. Any thoughts?
443 is SSL. So when you hit a site with it will go to 443 by default unless you add a :8000 after example the IP. But what you actually want is to have something that maps the the domain to the ip which refer to your service at 8000. So for me it would be a Nginx-Proxy Manager-server with firewall open to 443... which when a domain hits it, it will route to specific local-ip:port ... you could have other services than just nginx doing this, you could use something like Traefik as well.
I haven't reached that level yet to host it locally.
This works great. But the endpoints don't have SSL when specifying a custom domain. I'm guessing we need to modify the docker compose to enable SSL on kong?
Glad it works, but I'm not sure about that.
Also is it easy to just wrap a frontend + backend + DB inside a docker compose file and just deploy it there?
That's still a level too high for me to explain, probably I'd say, but don't know.
ah i feel you @@360Creators thank you though ! your work is AWESOME !
More to come!!@@haidarezio
Also looking for some coolify experts that have some time to help me out, so that I can create more and faster tutorials. If you happen to know them.. 😁
I wish i could help in that regard @@360Creators, I'm in their discord talking to other folks about setting up portainer and some monitoring for the VPS, but i went with netdata, super nice to have as well
but yeah most of my knowledge there is me going through discord threads and old messages for some small bug fixes xD
Yes I believe you can.
Thank you for this. Could you please make a video on adding custom SSL to coolify projects?
You're welcome. I'm not sure.
how to update coolify and supabase if version came out?
I'm not sure yet.
hey, nice tuto thanks! What about the bucket storage, can we have that too on the same server?
You're welcome! 😁
You can have a minio bucket storage using coolify.
Video is a bit long, but you can skip to the parts which contains minio content.
ua-cam.com/video/bnDhW1eTHnw/v-deo.html
Why use an external server for supabase instead of hosting both of them locally?
You can but it is not recommended, heavy on your server if you want to run more apps on it
Depends on the server. For this tutorial I thought it was easier to have an external one for it to deactivate after this tutorial. And what jaradaty88 says, I think it's good practise to seperate coolify from other apps. If one of the apps makes the server crash, you can still access coolify to throw it off the server.
Hello, am done with everything, but I can't find my supabase anon key anywhere in the dashboard can you please help me
It is called admin user, and admin password in coolify, use them
I think it should be in the environment variables.
How to setup the auth part though?
I don't know, maybe the (discord) community can help out here.
how to protect against brute force attacks on username / password ?
I don't know, maybe the (discord) community can help out here.
I can't connect to the deployed supabase with pg-admin. Why?
I don't know.
Perfect :)
One confusing thing is, when you point your domain to the Supabase instance in coolify you can access your dashboard as intended but then I run into all sorts of CORS errors when trying to interface with the storage frontend, as changing the domain on the studio/Kong doesn't change the other urls/certs for api endpoints.
Mmm I haven't had that yet, also haven't played enough with the Supabase at this point. What I think that might help is to go within Service Stack > Edit Compose File and then search for the domain it's currently incorrectly pointing to. And then replace that with the custom subdomain and try again by clicking Pull Latest Images & Restart.
@@360Creators I tried this and couldn't find a way to get it to work. I may have missed something. I think it has to do with the proxy/router that coolify implements but not sure. Honestly gave up lol, just going to use minio and postgress. Would be cool to be able to quickly spin up something like supabase though.
Hi, thank you for video, but i can't understant, what wrongs
Saved configuration files to /data/coolify/services/jo0kc40.
Creating Docker network.
Starting service.
Pulling images.
validating /data/coolify/services/jo0kc40/docker-compose.yml: services.realtime-dev Additional property supabase-realtime is not allowed
can't to deploy supabase
I'm sorry to read that. I'm not at the stage of understanding these types of errors yet. Better to check in with the Coolify discord community. I feel that it could be really nice if there were some developers specialized in Coolify to offer some support service to help with these type of things.