hacking: update db instructions to use schema.sql

Signed-off-by: Vlad-Stefan Harbuz <vlad@vladh.net>
This commit is contained in:
Vlad-Stefan Harbuz 2022-11-14 09:16:46 +00:00 committed by Drew DeVault
parent 3a1ae0d936
commit 1549432496
2 changed files with 7 additions and 6 deletions

View File

@ -126,11 +126,12 @@ its own database login, with full permissions for its database so that it may
manage its own schema migrations.
Once you populate the `connection-string` field in your `config.ini`, you may
use the `<module>-initdb` script to populate the schema and stamp the latest
revision for migrations (e.g., `metasrht-initdb` to set up meta.sr.ht's
database). Note that if you have not configured SSL for your PostgreSQL server,
you may have to append `?sslmode=disable` to your connection string for some
services to work.
use the `schema.sql` file to populate the database (e.g.
`psql -d meta.sr.ht -f schema.sql` to set up meta.sr.ht's database).
Note that if you have not configured SSL for your PostgreSQL server, you may
have to append `?sslmode=disable` to your connection string for some services
to work.
## Schema Upgrades

View File

@ -71,7 +71,7 @@ For each service *except* meta.sr.ht:
For each `SERVICE`:
* `createdb $SERVICE`
* `./$SRV-initdb` (e.g. `./metasrht-initdb`)
* `psql -d $SERVICE -f schema.sql` (e.g. `psql -d meta.sr.ht -f schema.sql`)
To run a service: