feat(platform)!: Lock Supabase docker-compose code (#9620)

We have been submoduling Supabase for provisioning local Supabase
instances using docker-compose. Aside from the huge size of unrelated
code being pulled, there is also the risk of pulling unintentional
breaking change from the upstream to the platform.

The latest Supabase changes hide the 5432 port from the supabase-db
container and shift it to the supavisor, the instance that we are
currently not using. This causes an error in the existing setup.

## BREAKING CHANGES

This change will introduce different volume locations for the database
content, pulling this change will make the data content fresh from the
start. To keep your old data with this change, execute this command:
```
cp -r supabase/docker/volumes/db/data db/docker/volumes/db/data
```


### Changes 🏗️

The scope of this PR is snapshotting the current docker-compose code
obtained from the Supabase repository and embedding it into our
repository. This will eliminate the need for submodule / recursive
cloning and bringing the entire Supabase repository into the platform.

### Checklist 📋

#### For code changes:
- [x] I have clearly listed my changes in the PR description
- [x] I have made a test plan
- [x] I have tested my changes according to the test plan:
  <!-- Put your test plan here: -->
  - [x] Existing CI
This commit is contained in:
Zamil Majdy
2025-03-15 00:16:13 +07:00
parent 52b4351961
commit 780fddc2a0
29 changed files with 1878 additions and 56 deletions

View File

@@ -84,11 +84,11 @@ To run the backend services, follow these steps:
```
This command will initialize and update the submodules in the repository. The `supabase` folder will be cloned to the root directory.
* Copy the `.env.example` file available in the `supabase/docker` directory to `.env` in `autogpt_platform`:
* Copy the `.env.example` file to `.env` in `autogpt_platform`:
```
cp supabase/docker/.env.example .env
cp .env.example .env
```
This command will copy the `.env.example` file to `.env` in the `supabase/docker` directory. You can modify the `.env` file to add your own environment variables.
This command will copy the `.env.example` file to `.env` in the `supabase` directory. You can modify the `.env` file to add your own environment variables.
* Run the backend services:
```