DOC: Update backend docs for development database setup

Author: Jason Moggridge

packages/backend/.env.development

@@ -1,2 +1,3 @@
-DATABASE_URL=postgres://postgres-user:password@localhost:5432/catcolab
+DATABASE_URL=postgres://catcolab:password@localhost:5432/catcolab
+DATABASE_SUPERUSER_URL=postgresql://postgres:password@localhost:5432/postgres
 FIREBASE_PROJECT_ID=catcolab-next

packages/backend/README.md

@@ -9,15 +9,8 @@ You can find the auto-generated documentation for this Rust crate at [next.catco
 ## Setup
 
 1. Install Rust, say by using [rustup](https://rustup.rs/)
-2. Install and run PostgreSQL and create a new database named `catcolab`
-    - (E.g. by using Docker)
 
-    ```sh
-    docker run --name catcolab-postgres -e POSTGRES_USER=postgres-user \
-        -e POSTGRES_PASSWORD=password -e POSTGRES_DB=catcolab -p 5432:5432 -d postgres:15
-    ```
-
-3. Make sure the required packages are built and installed:
+2. Make sure the required packages are built and installed:
 
    ```sh
    cd packages/notebook-types
@@ -26,10 +19,43 @@ You can find the auto-generated documentation for this Rust crate at [next.catco
    pnpm install
    ```
 
-4. Change to the migrator directory: `cd ../backend`
-5. Copy the .env.development to both folders (`cp .env.development .env && cp .env.development ../migrator/.env`) and update the `DATABASE_URL` variable with
-   database username, password, and port. (If you used the above Docker command _as is_ it should already be correct.)
-6. Run the initial database migration: `cargo run -p migrator apply`
+3. Set up PostgreSQL (choose one of the options below)
+
+### Option A: Using Docker (Recommended)
+
+Run PostgreSQL in a Docker container:
+
+```sh
+docker run --name catcolab-postgres -e POSTGRES_PASSWORD=password \
+    -e POSTGRES_DB=catcolab -p 5432:5432 -d postgres:15
+```
+
+This creates a PostgreSQL instance with:
+- Superuser: `postgres` with password `password`
+- Initial database: `catcolab` (will be set up in next steps)
+
+The default `.env.development` file is pre-configured to work with this Docker setup.
+
+### Option B: Using local PostgreSQL installation
+
+Install and run PostgreSQL locally. Ensure you have superuser access (typically the `postgres` user).
+
+**Note:** The default `.env.development` assumes the PostgreSQL superuser is `postgres` with password `password`.
+If your local PostgreSQL has different superuser credentials, you'll need to update `DATABASE_SUPERUSER_URL`
+in your `.env` file (see next step).
+
+### Complete the setup
+
+4. Change to the backend directory: `cd packages/backend`
+5. Copy the `.env.development` file: `cp .env.development .env`
+   - If you're using the Docker command above as-is, the defaults will work perfectly
+   - If you're using local PostgreSQL with different superuser credentials, update `DATABASE_SUPERUSER_URL` in `.env`
+6. Run the database setup: `../../infrastructure/scripts/cc-utils db setup`
+   - This command connects as the PostgreSQL superuser and automatically creates:
+     - The `catcolab` database user with appropriate permissions
+     - The `catcolab` database owned by that user
+   - It then runs all database migrations
+   - The command is idempotent and safe to run multiple times
 7. Build the backend binary: `cargo build`
 8. Run the unit tests: `cargo test`
 
@@ -72,10 +98,21 @@ pnpm run dev
 
 ## Running migrations
 
-This package runs databaes migrations using `migrator` subcommand which uses the
+This package runs database migrations using the `migrator` subcommand which uses the
 [sqlx_migrator](https://github.com/iamsauravsharma/sqlx_migrator) framework.
 
-### Usage
+### Recommended: Using cc-utils
+
+The easiest way to set up and migrate the database is using the `cc-utils` script:
+
+```sh
+../../infrastructure/scripts/cc-utils db setup
+```
+
+This command handles database creation, permissions, and migrations automatically.
+
+### Advanced: Direct migrator usage
+
 The migrator tool can be run from any directory using the `cargo run -p backend migrator ...` command.
 The migrator tool uses the default CLI interface provided by `sqlx_migrator`, which is very similar to
 the `sqlx` CLI.