Migrations/bookorbit
1
0
Fork 0
mirror of https://github.com/bookorbit/bookorbit.git synced 2026-11-03 00:11:37 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs: correct postgresql version references to 18

Browse Source 
docker-compose.dev.yml and e2e-runner.yml have run pgvector/pgvector:pg18
since v2.2.0, but the development and testing guides still described the
container as PostgreSQL 16.
This commit is contained in:
neon
2026-08-09 05:29:54 +00:00
parent 6769bf4b0f
commit 23fa46fca7
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/DEVELOPMENT.md
+2 -2
View File
@@ -30,7 +30,7 @@ graph LR
| ------------ | ------------------------------- | ----------------- | | ------------ | ------------------------------- | ----------------- |
| Frontend | Vue 3, Tailwind CSS v4, Vite | `client/` | | Frontend | Vue 3, Tailwind CSS v4, Vite | `client/` |
| Backend | NestJS 11, Fastify, Drizzle ORM | `server/` | | Backend | NestJS 11, Fastify, Drizzle ORM | `server/` |
| Database | PostgreSQL 16, pgvector | Docker container | | Database | PostgreSQL 18, pgvector | Docker container |
| Shared types | TypeScript | `packages/types/` | | Shared types | TypeScript | `packages/types/` |
| Real-time | Socket.IO | Server + Client | | Real-time | Socket.IO | Server + Client |
@@ -128,7 +128,7 @@ This installs dependencies for all three workspaces (server, client, packages/ty
docker compose -f docker-compose.dev.yml up -d --wait docker compose -f docker-compose.dev.yml up -d --wait
``` ```
This starts a PostgreSQL 16 container (with the `pgvector` extension) on port 5432. The `--wait` flag blocks until the database is healthy. Data is persisted in a named Docker volume across restarts. This starts a PostgreSQL 18 container (with the `pgvector` extension) on port 5432. The `--wait` flag blocks until the database is healthy. Data is persisted in a named Docker volume across restarts.
> **Already have PostgreSQL running?** You can point `DATABASE_URL` in `server/.env` at your existing instance, but you will still need the `uuid-ossp`, `pg_trgm`, `unaccent`, and `vector` extensions installed. Using Docker is the easiest path. > **Already have PostgreSQL running?** You can point `DATABASE_URL` in `server/.env` at your existing instance, but you will still need the `uuid-ossp`, `pg_trgm`, `unaccent`, and `vector` extensions installed. Using Docker is the easiest path.
docs/TESTING.md
+1 -1
View File
@@ -317,7 +317,7 @@ E2E suites are selected by `scripts/e2e/select-matrix.mjs`:
- **Pull request / push to main / manual `CI` dispatch:** E2E is skipped in `.github/workflows/ci.yml`. - **Pull request / push to main / manual `CI` dispatch:** E2E is skipped in `.github/workflows/ci.yml`.
Each selected suite runs as its own GitHub Actions job via the reusable Each selected suite runs as its own GitHub Actions job via the reusable
`.github/workflows/e2e-runner.yml` workflow, which spins up a PostgreSQL 16 + pgvector service `.github/workflows/e2e-runner.yml` workflow, which spins up a PostgreSQL 18 + pgvector service
container and calls `pnpm run e2e:run -- <suite-id>`. container and calls `pnpm run e2e:run -- <suite-id>`.
**Manual full run:** Trigger `.github/workflows/e2e.yml` from the Actions tab. It accepts an **Manual full run:** Trigger `.github/workflows/e2e.yml` from the Actions tab. It accepts an