Skip to content

doc/update the doc for dev jobs schemas and modules name changing #594

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Zetazzz wants to merge 5 commits into
base: main
Choose a base branch
from
Open

doc/update the doc for dev jobs schemas and modules name changing #594

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
6ba8574
name changing
Zetazzz Jan 9, 2026
e2ad767
Initial plan
Copilot Jan 9, 2026
871af88
Remove deprecated app-svc-local mentions from documentation
Copilot Jan 9, 2026
fafac10
Update jobs/DEVELOPMENT_JOBS.md
Anmol1696 Jan 9, 2026
e088349
Merge pull request #595 from constructive-io/copilot/sub-pr-594
Anmol1696 Jan 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 13 additions & 5 deletions jobs/DEVELOPMENT_JOBS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,17 +69,23 @@ From the `constructive-db/` directory (with `pgenv` applied):

```sh
pgpm admin-users bootstrap --yes
```

If you need seeded test users, run:

```sh
pgpm admin-users add --test --yes
```

3. Deploy the main app and jobs packages into DB:
3. Deploy the main app and metaschema packages into DB:

```sh
pgpm deploy --yes --database "$PGDATABASE" --package app-svc-local
pgpm deploy --yes --database "$PGDATABASE" --package app
pgpm deploy --yes --database "$PGDATABASE" --package metaschema
pgpm deploy --yes --database "$PGDATABASE" --package pgpm-database-jobs
```

NOTE: The `app` package pulls in `pgpm-database-jobs`, so you don't need to deploy it separately.

At this point, the app schema and `database-jobs` should be installed and `app_jobs.*` should be available in the `constructive` database.

---
Expand Down Expand Up @@ -128,7 +134,9 @@ In dry-run mode:

Constructive selects the API by the HTTP `Host` header using rows in `services_public.domains`.

For local development, `app-svc-local` seeds `admin.localhost` as the admin API domain. `docker-compose.jobs.yml` adds a Docker network alias so other containers can resolve `admin.localhost` to the `constructive-server` container, and `send-email-link` uses:
For local development, you need a domain route for `admin.localhost` in `services_public.domains`. Seed a domain route yourself (or skip the `send-email-link` test).

`docker-compose.jobs.yml` adds a Docker network alias so other containers can resolve `admin.localhost` to the `constructive-server` container, and `send-email-link` uses:

- `GRAPHQL_URL=http://admin.localhost:3000/graphql`

Expand Down Expand Up @@ -179,7 +187,7 @@ You should then see the job picked up by `knative-job-service` and the email pay

`send-email-link` queries GraphQL for site/database metadata, so it requires:

- The app/meta packages deployed in step 3 (`app-svc-local`, `metaschema-schema`, `services`, `metaschema-modules`)
- The app/meta packages deployed in step 3 (`app`, `metaschema-schema`, `services`, `metaschema-modules`)
- A real `database_id` (use `$DBID` above)
- A GraphQL hostname that matches a seeded domain route (step 5)
- For localhost development, the site/domain metadata usually resolves to `localhost`.
Expand Down