Wow, appreciate this Theo! I just have two concerns stopping me from going all in on VPS 1. storage Currently while using supabase cloud, in my next.js code I'm using supabase's sdk storage procedures for uploading and storing files. Is it a straightforward setup to create our own s3 buckets and link them to the coolify's supabase instance? Would love a tutorial on that if possible, on making storage work while still using supabase's procedures for it 2. managing development & prod envs for supabase I'm sure for next.js we can just use branching for dev and prod, but how easy or difficult would it be to manage a development and prod environment for supabase, in this kind of a setup? how would the architecture work? would love a tutorial covering this if possible
Hey thank you for the kind words! For Storage, you still have the ability to create storage buckets on the supabase admin dashboard on your self hosted instance, you can also link S3 buckets as backup directly on the Coolify UI of your project. For different envs topic, when creating projects, you can choose the environment at the top of the screen, you can then use different branches in your git to handle your NextJS deployments differently as well as different DB schemas.
hi, i have trouble with my next js env concerning supabase. I dont know what are supposed to be the supabase public url and DATABASE_URL, i'm kinda lost in there
If you are using the same Supabase deployment as me then you need the keys that are auto generated in the "Environment" tab at the left of the Coolify UI on your project. See at 17:40 when I didn't enter the keys I had the same error as you do probably.
@@theointechs i don't get it. when i use to do it without coolify and i needed some env variable in my next app, related to supabase. (such as NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_KEY etc..) And i have trouble finding what to use for DATABASE_URL and NEXT_PUBLIC_SUPABASE_URL. I think i missed the auto generated part oO
![[Limbus Company - Teaser] Season5 - Oblivion](http://i.ytimg.com/vi/8anKuEeZLeI/mqdefault.jpg)
Wow, appreciate this Theo!
I just have two concerns stopping me from going all in on VPS
1. storage
Currently while using supabase cloud, in my next.js code I'm using supabase's sdk storage procedures for uploading and storing files. Is it a straightforward setup to create our own s3 buckets and link them to the coolify's supabase instance? Would love a tutorial on that if possible, on making storage work while still using supabase's procedures for it
2. managing development & prod envs for supabase
I'm sure for next.js we can just use branching for dev and prod, but how easy or difficult would it be to manage a development and prod environment for supabase, in this kind of a setup? how would the architecture work? would love a tutorial covering this if possible
Hey thank you for the kind words! For Storage, you still have the ability to create storage buckets on the supabase admin dashboard on your self hosted instance, you can also link S3 buckets as backup directly on the Coolify UI of your project. For different envs topic, when creating projects, you can choose the environment at the top of the screen, you can then use different branches in your git to handle your NextJS deployments differently as well as different DB schemas.
hi, i have trouble with my next js env concerning supabase.
I dont know what are supposed to be the supabase public url and DATABASE_URL, i'm kinda lost in there
If you are using the same Supabase deployment as me then you need the keys that are auto generated in the "Environment" tab at the left of the Coolify UI on your project. See at 17:40 when I didn't enter the keys I had the same error as you do probably.
@@theointechs i don't get it.
when i use to do it without coolify and i needed some env variable in my next app, related to supabase. (such as NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_KEY etc..)
And i have trouble finding what to use for DATABASE_URL and NEXT_PUBLIC_SUPABASE_URL.
I think i missed the auto generated part oO
Thank you for this. Some Astro stuff would be great too!
Thank you! never used Astro in the past ngl but I might check it out!
hey Theo, did you open the port for supabase-studio: and not for supabase-db: ?
I opened only the Postgres db port to be able to remote access, otherwise my domains are using a reverse proxy so its more secure.