Self-hosting Supabase
Deploying Domain Locker on top of a self-hosted Supabase instance gives you full access to all features. However, the setup process is much more complex and requires considerably higher system resources.
Backstory
In the self-hosted version of Domain Locker, there's some features which are not available. This isn't us trying to restrict you or gate-keep anything, but rather that Domain Locker was initially built to run on a serverless architecture (Deno functions) and was very tightly integrated with the Supabase ecosystem.
It wasn't until much later, when people started asking for an easier way to self-host Domain Locker, that I started porting the API to a Node-based architecture and the DB to Postgres (which makes running in Docker, Kubernetes and self-hosting systems).
Anyway, you can get access to all pro features (like we have on the domain-locker.com version), by self-hosting your own Supabase instance (instead of using Postgres and Node). The only caveat being that... Supabase is a bloody pain to get running!
Usage
- Firstly, setup a Supabase instance. Either with Kubernetes with these Helm charts or using Docker with like this Dockerfile. For step-by-step instructions, take a look at the official setup guide.
- Then, fork the domain locker supabase repo and deploy all it's functions, schemas and config to your new Supabase instance, by following the instructions in the readme.
Support
Sorry, but I cannot offer support for the Supabase version 😔. I just found debugging other peoples Supabase setups too time consuming and complex (which was the reason I made the Node Postgres version!).
So to get help, you will need to look at the official Supabase docs and use their support channels. Please don't open issues or send emails with questions about getting Supabase running.