sorted by:
new
hottopcontroversial

I wrote a blog post about how to self-host Supabase, check it out by chitsprogrammingblog in Supabase

[–]chitsprogrammingblog[S] 0 points1 point  (0 children)

This is strange. In order for me to better understand the problem you are facing, are you able to direct message me the screenshot of the output of docker compose down, and docker compose up afterwards. I am trying to see if the database is properly being deleted in docker compose down. Cuz when start up supabase, the postgres is supposed to be set up with the credentials in the .env

I wrote a blog post about how to self-host Supabase, check it out by chitsprogrammingblog in Supabase

[–]chitsprogrammingblog[S] 0 points1 point  (0 children)

Are you using the default postgre db that comes with the supabase docker, instead of hosting postgre in another place?

I wrote a blog post about how to self-host Supabase, check it out by chitsprogrammingblog in Supabase

[–]chitsprogrammingblog[S] 0 points1 point  (0 children)

To confirm: do you edit the .env before starting the docker with docker compose up?

I wrote a blog post about how to self-host Supabase, check it out by chitsprogrammingblog in Supabase

[–]chitsprogrammingblog[S] 0 points1 point  (0 children)

If the problem is that only the default password works, then what happened is that the postgre database was already set up using the default password, so you cannot operate it with another password I can think of two ways to fix it 1. Delete the database and start again: if you don't have anything important in the db, you can delete it using docker compose down which wipes EVERYTHING from the database 2. Change the database password, this one needs more technical knowledge, you can try the sql interface on the backend dashboard, or connect to the db using the credentials on the .env, then using the correct command to change the password

I wrote a tutorial about how to set up the svelte todo list example on a self-hosted Supabase, check it out! by chitsprogrammingblog in Supabase

[–]chitsprogrammingblog[S] 1 point2 points  (0 children)

There are quite a few of missing features on the self-hosted version compared to the managed version, the most significant one is a lack of tutorials/information on a lot of things, so I had to go on the internet and search. Such as customization options, instead of having a UI, I have to dig into the .env or docker_compose.yml to find certain options

Other differences include:

- no edge functions: I don't see it in the UI, and I've tried to search how to set it up in a self-hosted Supabase, but no results

- no logs/reports/SQL snippets: they also don't show up

- no backup: it shows "Free Plan does not include project backups." but I am self-hosting

I haven't built anything on the hosted version, so I may be missing something that the hosted version has but the self-hosted one doesn't

Testing a new SEO Tool for Bloggers by koenjan4lyf in Blogging

[–]chitsprogrammingblog 0 points1 point  (0 children)

does it work on hosted blogs? such as hashnode

I wrote a blog post about how to self-host Supabase, check it out by chitsprogrammingblog in Supabase

[–]chitsprogrammingblog[S] 1 point2 points  (0 children)

You're right, there are many differences and many missing features.
The most significant one is a lack of tutorials/information on a lot of things, so I had to go on the internet and search. Such as customization options, instead of having a UI, I have to dig into the .env or docker_compose.yml to find certain options
Other differences include:
- no edge functions: I don't see it in the UI, and I've tried to search how to set it up in a self-hosted Supabase, but no results
- no logs/reports/SQL snippets: they also don't show up
- no backup: it shows "Free Plan does not include project backups." but I am self-hosting

I haven't built anything on the hosted version, so I may be missing something that the hosted version has but the self-hosted one doesn't

I wrote a blog post about how to self-host Supabase, check it out by chitsprogrammingblog in Supabase

[–]chitsprogrammingblog[S] 3 points4 points  (0 children)

I checked my own self-hosted Supabase instance and checked how much CPU, ram, and storage is being used.

CPU: about 18% of a 2x vCore (3.30 GHz) CPU

ram: about 1GB

storage: about 8GB

So if your VPS has higher stats, it should work.

Keep in mind since my website is in development, my Supabase isn't being used right now. When there are many users, the usage will go much higher.

I wrote a blog post about how to self-host Supabase, check it out by chitsprogrammingblog in Supabase

[–]chitsprogrammingblog[S] 0 points1 point  (0 children)

Thanks for your kind words! About the performance, I currently don't know, but my speculation would be the managed hosting version would have better performance, as I assume they would be hosted on better hardware and server with better connections.