30 ms·

I checked a little bit ago but I might have missed it so please correct me. Are there plans to expand self-hosting support? The migrations are a big step forwa

I checked a little bit ago but I might have missed it so please correct me. Are there plans to expand self-hosting support? The migrations are a big step forward. Are you intending to fill the roll of being a framework akin to a "super django" type of deal? Again the migrations help a ton, but I've been hesitant to use Supabase for random projects because I don't want to rely on the platform, and I don't want random people on github who want to try or contribute to require a supabase account. I'd love to use it more as a modular ORM for miscellaneous projects instead of the current "hosted platform", currently none of the tutorials (or github projects) seem to explain this route at all. I think you actually do work for this purpose, and I think the docs mostly cover the bare minimum for self hosting, and I understand your business kinda relies on the hosted platform, but I'd love to see further tutorials and thorough explinations of all the features - currently some like the AI features aren't really explained if they work in the self-hosted or not, or if you have to do anything special for that. EDIT: Also I do appreciate your business being opensource, and contributing to postgres so much! Sorry for the rambling, and I apologize if I'm blind and missed some obvious docs.

kiwicopple 3y ago
> Are you intending to fill the roll of being a framework akin to a "super django" type of deal? We don't plan to replace any specific framework. We simply want to make Postgres easier to use. You can use Django (or any other framework) and Supabase together. We provide some additional tooling on top, but we aim to make this tooling 100% compatible with other tools. As an example, here[1] is a change we made recently so that our Storage service works better with Clerk (a popular Auth service, which is a good alternative to our own Auth service). We plan to document this better - it was one of the promises I made in the OP. > Are there plans to expand self-hosting support? we made a few updates[0] this week to improve self-hosting based on the common feedback. if there is anything missing just let me know and i will do another round of improvements. > currently some like the AI features aren't really explained if they work in the self-hosted or not, or if you have to do anything special for that. nothing is feature-gated so everything works on self-hosted. That said, I agree that we can be better at explaining the self-hosting. We are putting a lot more effort into improving our docs in general. For self-hosting we can certainly be clearer about the boundaries where you are responsible (eg, you need to take care of your own backups, the AI features will require external acconts). we're working on this, but feel free to open issues where it's unclear we can address anything specific [0] https://github.com/supabase/supabase/pull/16097 https://github.com/supabase/supabase/pull/16097 [1] https://github.com/supabase/storage-api/pull/340 https://github.com/supabase/storage-api/pull/340

kiwicopple 3y ago

> Are you intending to fill the roll of being a framework akin to a "super django" type of deal? We don't plan to replace any specific framework. We simply want to make Postgres easier to use. You can use Django (or any other framework) and Supabase together. We provide some additional tooling on top, but we aim to make this tooling 100% compatible with other tools. As an example, here[1] is a change we made recently so that our Storage service works better with Clerk (a popular Auth service, which is a good alternative to our own Auth service). We plan to document this better - it was one of the promises I made in the OP. > Are there plans to expand self-hosting support? we made a few updates[0] this week to improve self-hosting based on the common feedback. if there is anything missing just let me know and i will do another round of improvements. > currently some like the AI features aren't really explained if they work in the self-hosted or not, or if you have to do anything special for that. nothing is feature-gated so everything works on self-hosted. That said, I agree that we can be better at explaining the self-hosting. We are putting a lot more effort into improving our docs in general. For self-hosting we can certainly be clearer about the boundaries where you are responsible (eg, you need to take care of your own backups, the AI features will require external acconts). we're working on this, but feel free to open issues where it's unclear we can address anything specific [0] https://github.com/supabase/supabase/pull/16097 https://github.com/supabase/supabase/pull/16097 [1] https://github.com/supabase/storage-api/pull/340 https://github.com/supabase/storage-api/pull/340