diff --git a/apps/docs/content/guides/platform/maturity-model.mdx b/apps/docs/content/guides/platform/maturity-model.mdx index 8bcad22377b..b224f6c04d9 100644 --- a/apps/docs/content/guides/platform/maturity-model.mdx +++ b/apps/docs/content/guides/platform/maturity-model.mdx @@ -42,4 +42,4 @@ Resources: For a more secure setup, consider running your workload across several organizations. It's a common pattern to have a Production organization which is restricted to only those team members who are qualified to have direct access to production databases. -Reach out to [growth@supabase.com](mailto:growth@supabase.com) if you need help designing a secure development workflow for your organization. +Reach out to [growth](https://forms.supabase.com/enterprise) if you need help designing a secure development workflow for your organization. diff --git a/apps/docs/content/guides/platform/performance.mdx b/apps/docs/content/guides/platform/performance.mdx index a08e5d5b619..cac8f7005d5 100644 --- a/apps/docs/content/guides/platform/performance.mdx +++ b/apps/docs/content/guides/platform/performance.mdx @@ -199,3 +199,7 @@ Depending on the clients involved, you might be able to configure them to work w ### Allowing higher number of connections You can configure Postgres connection limit among other parameters by using [Custom Postgres Config](/docs/guides/platform/custom-postgres-config#custom-postgres-config). + +### Enterprise + +[Contact us](https://forms.supabase.com/enterprise) if you need help tuning your database for your specific workflow. diff --git a/apps/docs/content/guides/resources/migrating-to-supabase/amazon-rds.mdx b/apps/docs/content/guides/resources/migrating-to-supabase/amazon-rds.mdx index 2a9b2c4110a..519e106616b 100644 --- a/apps/docs/content/guides/resources/migrating-to-supabase/amazon-rds.mdx +++ b/apps/docs/content/guides/resources/migrating-to-supabase/amazon-rds.mdx @@ -53,46 +53,49 @@ Alternatively, you can use [pgloader](https://github.com/dimitri/pgloader), a fl - Install pgloader. - Create a configuration file (e.g., config.load). +1. Install pgloader. +2. Create a configuration file (e.g., config.load). - For your destination, use your Supabase connection string with `Use connection pooling` enabled, and the mode set to `Session`. You can get the string from your [`Database Settings`](https://supabase.com/dashboard/project/_/settings/general). + For your destination, use your Supabase connection string with `Use connection pooling` enabled, and the mode set to `Session`. You can get the string from your [`Database Settings`](https://supabase.com/dashboard/project/_/settings/general). -```sql -load database - from mysql://user:password@host/source_db - into postgres://postgres.xxxx:password@xxxx.pooler.supabase.com:5432/postgres -alter schema 'public' owner to 'postgres'; -set wal_buffers = '64MB', max_wal_senders = 0, statement_timeout = 0, work_mem to '2GB'; -``` + ```sql + load database + from mysql://user:password@host/source_db + into postgres://postgres.xxxx:password@xxxx.pooler.supabase.com:5432/postgres + alter schema 'public' owner to 'postgres'; + set wal_buffers = '64MB', max_wal_senders = 0, statement_timeout = 0, work_mem to '2GB'; + ``` -##Run the migration with pgloader +3. Run the migration with pgloader -```bash -pgloader config.load -``` + ```bash + pgloader config.load + ``` - Install pgloader. - Create a configuration file (e.g., config.load). +1. Install pgloader. +2. Create a configuration file (e.g., config.load). -```sql -LOAD DATABASE - FROM mssql://USER:PASSWORD@HOST/SOURCE_DB - INTO postgres://postgres.xxxx:password@xxxx.pooler.supabase.com:6543/postgres -ALTER SCHEMA 'public' OWNER TO 'postgres'; -set wal_buffers = '64MB', max_wal_senders = 0, statement_timeout = 0, work_mem to '2GB'; -``` + ```sql + LOAD DATABASE + FROM mssql://USER:PASSWORD@HOST/SOURCE_DB + INTO postgres://postgres.xxxx:password@xxxx.pooler.supabase.com:6543/postgres + ALTER SCHEMA 'public' OWNER TO 'postgres'; + set wal_buffers = '64MB', max_wal_senders = 0, statement_timeout = 0, work_mem to '2GB'; + ``` -##Run the migration with pgloader +3. Run the migration with pgloader -```bash -pgloader config.load -``` + ```bash + pgloader config.load + ``` +## Enterprise + +[Contact us](https://forms.supabase.com/enterprise) if you need more help migrating your project. diff --git a/apps/docs/content/guides/resources/migrating-to-supabase/firebase-auth.mdx b/apps/docs/content/guides/resources/migrating-to-supabase/firebase-auth.mdx index b025a5cc015..72302b38401 100644 --- a/apps/docs/content/guides/resources/migrating-to-supabase/firebase-auth.mdx +++ b/apps/docs/content/guides/resources/migrating-to-supabase/firebase-auth.mdx @@ -14,21 +14,21 @@ Supabase provides several [tools](https://github.com/supabase-community/firebase 1. Clone the [firebase-to-supabase](https://github.com/supabase-community/firebase-to-supabase) repository: -```bash -git clone https://github.com/supabase-community/firebase-to-supabase.git -``` + ```bash + git clone https://github.com/supabase-community/firebase-to-supabase.git + ``` 1. In the `/auth` directory, create a file named `supabase-service.json` with the following contents: -```json -{ - "host": "database.server.com", - "password": "secretpassword", - "user": "postgres", - "database": "postgres", - "port": 5432 -} -``` + ```json + { + "host": "database.server.com", + "password": "secretpassword", + "user": "postgres", + "database": "postgres", + "port": 5432 + } + ``` 1. Go to the [Database settings](https://supabase.com/dashboard/project/_/settings/database) for your project in the Supabase Dashboard. 1. Under `Connection parameters`, enable `Use connection pooling` and set the mode to `Session`. Replace the `Host` and `User` fields with the values shown. @@ -85,3 +85,7 @@ For more advanced migrations, including the use of a middleware server component - [Supabase vs Firebase](https://supabase.com/alternatives/supabase-vs-firebase) - [Firestore Data Migration](/docs/guides/migrations/firestore-data) - [Firestore Storage Migration](/docs/guides/migrations/firebase-storage) + +## Enterprise + +[Contact us](https://forms.supabase.com/enterprise) if you need more help migrating your project. diff --git a/apps/docs/content/guides/resources/migrating-to-supabase/firebase-storage.mdx b/apps/docs/content/guides/resources/migrating-to-supabase/firebase-storage.mdx index e3413d93201..d83f6a62acc 100644 --- a/apps/docs/content/guides/resources/migrating-to-supabase/firebase-storage.mdx +++ b/apps/docs/content/guides/resources/migrating-to-supabase/firebase-storage.mdx @@ -14,9 +14,9 @@ Supabase provides several [tools](https://github.com/supabase-community/firebase 1. Clone the [firebase-to-supabase](https://github.com/supabase-community/firebase-to-supabase) repository: -```bash -git clone https://github.com/supabase-community/firebase-to-supabase.git -``` + ```bash + git clone https://github.com/supabase-community/firebase-to-supabase.git + ``` 1. In the `/storage` directory, rename [supabase-keys-sample.js](https://github.com/supabase-community/firebase-to-supabase/blob/main/storage/supabase-keys-sample.js) to `supabase-keys.js`. 1. Go to your Supabase project's [API settings](https://supabase.com/dashboard/project/_/settings/api) in the Dashboard. @@ -64,3 +64,7 @@ If the bucket doesn't exist, it's created as a `non-public` bucket. You must set - [Supabase vs Firebase](https://supabase.com/alternatives/supabase-vs-firebase) - [Firestore Data Migration](/docs/guides/migrations/firestore-data) - [Firebase Auth Migration](/docs/guides/migrations/firebase-auth) + +## Enterprise + +[Contact us](https://forms.supabase.com/enterprise) if you need more help migrating your project. diff --git a/apps/docs/content/guides/resources/migrating-to-supabase/firestore-data.mdx b/apps/docs/content/guides/resources/migrating-to-supabase/firestore-data.mdx index 58a7eb1d177..ba2dda8d397 100644 --- a/apps/docs/content/guides/resources/migrating-to-supabase/firestore-data.mdx +++ b/apps/docs/content/guides/resources/migrating-to-supabase/firestore-data.mdx @@ -13,21 +13,21 @@ The Firestore `collection` is "flattened" and converted to a table with basic co 1. Clone the [firebase-to-supabase](https://github.com/supabase-community/firebase-to-supabase) repository: -```bash -git clone https://github.com/supabase-community/firebase-to-supabase.git -``` + ```bash + git clone https://github.com/supabase-community/firebase-to-supabase.git + ``` 1. In the `/firestore` directory, create a file named `supabase-service.json` with the following contents: -```json -{ - "host": "database.server.com", - "password": "secretpassword", - "user": "postgres", - "database": "postgres", - "port": 5432 -} -``` + ```json + { + "host": "database.server.com", + "password": "secretpassword", + "user": "postgres", + "database": "postgres", + "port": 5432 + } + ``` 1. Go to the [Database settings](https://supabase.com/dashboard/project/_/settings/database) for your project in the Supabase Dashboard. 1. Under `Connection parameters`, enable `Use connection pooling` and set the mode to `Session`. Replace the `Host` and `User` fields with the values shown. @@ -208,3 +208,7 @@ The result is two separate JSON files: - [Supabase vs Firebase](https://supabase.com/alternatives/supabase-vs-firebase) - [Firestore Storage Migration](/docs/guides/migrations/firebase-storage) - [Firebase Auth Migration](/docs/guides/migrations/firebase-auth) + +## Enterprise + +[Contact us](https://forms.supabase.com/enterprise) if you need more help migrating your project. diff --git a/apps/docs/content/guides/resources/migrating-to-supabase/heroku.mdx b/apps/docs/content/guides/resources/migrating-to-supabase/heroku.mdx index 6f5402ebdca..17996649ab4 100644 --- a/apps/docs/content/guides/resources/migrating-to-supabase/heroku.mdx +++ b/apps/docs/content/guides/resources/migrating-to-supabase/heroku.mdx @@ -66,3 +66,7 @@ psql -d "$YOUR_CONNECTION_STRING" -f heroku_dump.sql Run `pg_dump --help` for a full list of options. + +## Enterprise + +[Contact us](https://forms.supabase.com/enterprise) if you need more help migrating your project. diff --git a/apps/docs/content/guides/resources/migrating-to-supabase/mssql.mdx b/apps/docs/content/guides/resources/migrating-to-supabase/mssql.mdx index 3b187acbbab..75a6a0d5b15 100644 --- a/apps/docs/content/guides/resources/migrating-to-supabase/mssql.mdx +++ b/apps/docs/content/guides/resources/migrating-to-supabase/mssql.mdx @@ -50,26 +50,30 @@ Alternatively, you can use [pgloader](https://github.com/dimitri/pgloader), a fl - Install pgloader. - Create a configuration file (e.g., config.load). +1. Install pgloader. +2. Create a configuration file (e.g., config.load). - For your destination, use your Supabase connection string with `Use connection pooling` enabled, and the mode set to `Session`. You can get the string from your [`Database Settings`](https://supabase.com/dashboard/project/_/settings/general). + For your destination, use your Supabase connection string with `Use connection pooling` enabled, and the mode set to `Session`. You can get the string from your [`Database Settings`](https://supabase.com/dashboard/project/_/settings/general). -```sql -LOAD DATABASE - FROM mssql://USER:PASSWORD@HOST/SOURCE_DB - INTO postgres://postgres.xxxx:password@xxxx.pooler.supabase.com:5432/postgres -ALTER SCHEMA 'public' OWNER TO 'postgres'; -set wal_buffers = '64MB', max_wal_senders = 0, statement_timeout = 0, work_mem to '2GB'; -``` + ```sql + LOAD DATABASE + FROM mssql://USER:PASSWORD@HOST/SOURCE_DB + INTO postgres://postgres.xxxx:password@xxxx.pooler.supabase.com:5432/postgres + ALTER SCHEMA 'public' OWNER TO 'postgres'; + set wal_buffers = '64MB', max_wal_senders = 0, statement_timeout = 0, work_mem to '2GB'; + ``` -## Run the migration with pgloader +3. Run the migration with pgloader -```bash -pgloader config.load -``` + ```bash + pgloader config.load + ``` + +## Enterprise + +[Contact us](https://forms.supabase.com/enterprise) if you need more help migrating your project. diff --git a/apps/docs/content/guides/resources/migrating-to-supabase/mysql.mdx b/apps/docs/content/guides/resources/migrating-to-supabase/mysql.mdx index 750dae1fdd0..8f558dfa6ce 100644 --- a/apps/docs/content/guides/resources/migrating-to-supabase/mysql.mdx +++ b/apps/docs/content/guides/resources/migrating-to-supabase/mysql.mdx @@ -51,26 +51,30 @@ Alternatively, you can use [pgloader](https://github.com/dimitri/pgloader), a fl - Install pgloader. - Create a configuration file (e.g., config.load). +1. Install pgloader. +2. Create a configuration file (e.g., config.load). - For your destination, use your Supabase connection string with `Use connection pooling` enabled, and the mode set to `Session`. You can get the string from your [`Database Settings`](https://supabase.com/dashboard/project/_/settings/general). + For your destination, use your Supabase connection string with `Use connection pooling` enabled, and the mode set to `Session`. You can get the string from your [`Database Settings`](https://supabase.com/dashboard/project/_/settings/general). -```sql -load database - from mysql://user:password@host/source_db - into postgres://postgres.xxxx:password@xxxx.pooler.supabase.com:5432/postgres -alter schema 'public' owner to 'postgres'; -set wal_buffers = '64MB', max_wal_senders = 0, statement_timeout = 0, work_mem to '2GB'; -``` + ```sql + load database + from mysql://user:password@host/source_db + into postgres://postgres.xxxx:password@xxxx.pooler.supabase.com:5432/postgres + alter schema 'public' owner to 'postgres'; + set wal_buffers = '64MB', max_wal_senders = 0, statement_timeout = 0, work_mem to '2GB'; + ``` -## Run the migration with pgloader +3. Run the migration with pgloader -```bash -pgloader config.load -``` + ```bash + pgloader config.load + ``` + +## Enterprise + +[Contact us](https://forms.supabase.com/enterprise) if you need more help migrating your project. diff --git a/apps/docs/content/guides/resources/migrating-to-supabase/postgres.mdx b/apps/docs/content/guides/resources/migrating-to-supabase/postgres.mdx index 83ec586b341..b8dc0f54370 100644 --- a/apps/docs/content/guides/resources/migrating-to-supabase/postgres.mdx +++ b/apps/docs/content/guides/resources/migrating-to-supabase/postgres.mdx @@ -49,25 +49,25 @@ The fastest way to migrate your database is with the Supabase migration tool on -### Export your database to a file in console [#export-database] +1. Export your database to a file in console -Use `pg_dump` with your Postgres credentials to export your database to a file (e.g., `dump.sql`). + Use `pg_dump` with your Postgres credentials to export your database to a file (e.g., `dump.sql`). -```bash -pg_dump --clean --if-exists --quote-all-identifiers \ - -h $HOST -U $USER -d $DATABASE \ - --no-owner --no-privileges > dump.sql -``` + ```bash + pg_dump --clean --if-exists --quote-all-identifiers \ + -h $HOST -U $USER -d $DATABASE \ + --no-owner --no-privileges > dump.sql + ``` -### Import the database to your Supabase project [#import-database-to-supabase] +2. Import the database to your Supabase project -Use `psql` to import the Postgres database file to your Supabase project. + Use `psql` to import the Postgres database file to your Supabase project. -```bash -psql -d "$YOUR_CONNECTION_STRING" -f dump.sql -``` + ```bash + psql -d "$YOUR_CONNECTION_STRING" -f dump.sql + ``` -### Additional options +Additional options - To only migrate a single database schema, add the `--schema=PATTERN` parameter to your `pg_dump` command. - To exclude a schema: `--exclude-schema=PATTERN`. @@ -80,3 +80,7 @@ Run `pg_dump --help` for a full list of options. + +## Enterprise + +[Contact us](https://forms.supabase.com/enterprise) if you need more help migrating your project. diff --git a/apps/docs/content/guides/resources/migrating-to-supabase/render.mdx b/apps/docs/content/guides/resources/migrating-to-supabase/render.mdx index 1dbdbef8419..5078aeeee3a 100644 --- a/apps/docs/content/guides/resources/migrating-to-supabase/render.mdx +++ b/apps/docs/content/guides/resources/migrating-to-supabase/render.mdx @@ -51,25 +51,25 @@ The fastest way to migrate your database is with the Supabase migration tool on -### Export your Render database to a file in console [#export-render-database] +1. Export your Render database to a file in console -Use `pg_dump` with your Render credentials to export your Render database to a file (e.g., `render_dump.sql`). + Use `pg_dump` with your Render credentials to export your Render database to a file (e.g., `render_dump.sql`). -```bash -pg_dump --clean --if-exists --quote-all-identifiers \ - -h $RENDER_HOST -U $RENDER_USER -d $RENDER_DATABASE \ - --no-owner --no-privileges > render_dump.sql -``` + ```bash + pg_dump --clean --if-exists --quote-all-identifiers \ + -h $RENDER_HOST -U $RENDER_USER -d $RENDER_DATABASE \ + --no-owner --no-privileges > render_dump.sql + ``` -### Import the database to your Supabase project [#import-database-to-supabase] +2. Import the database to your Supabase project -Use `psql` to import the Render database file to your Supabase project. + Use `psql` to import the Render database file to your Supabase project. -```bash -psql -d "$YOUR_CONNECTION_STRING" -f render_dump.sql -``` + ```bash + psql -d "$YOUR_CONNECTION_STRING" -f render_dump.sql + ``` -### Additional options +Additional options - To only migrate a single database schema, add the `--schema=PATTERN` parameter to your `pg_dump` command. - To exclude a schema: `--exclude-schema=PATTERN`. @@ -82,3 +82,7 @@ Run `pg_dump --help` for a full list of options. + +## Enterprise + +[Contact us](https://forms.supabase.com/enterprise) if you need more help migrating your project.