-
-
Notifications
You must be signed in to change notification settings - Fork 187
Additional AMI "bundles" #46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Will add to #44 |
Btw, do we already have names in mind to easily distinguish one from the others? At the top of my head, all I could think of are:
|
I think those names are good - just make sure it's |
Will be closing this as we will discontinue our public AMI builds in favor of our Docker offerings as the recommended option for self-hosting Supabase. (ref) For more information on the overview of our self-hosted setup, you can refer to our documentation here. You can refer here on how to set up Supabase through Docker. |
Context
We'd like to build a few different bundles for: a) the AWS marketplace and b) internal usage.
Bundles
We would like to produce AMI bundles
Postgres
-> this one we already havePostgres
+PgBouncer
Postgres
+PostgREST
Postgres
+PgBouncer
+PostgREST
Marketplaces
The top priority is to produce these images for the AWS marketplace. We can target other marketplaces (DO, GCP etc) in a separate issue.
The text was updated successfully, but these errors were encountered: