Align website tooling with govoplan-website rename
This commit is contained in:
@@ -519,8 +519,8 @@ Regenerate the browsable module directory from an existing catalog/keyring:
|
||||
|
||||
```sh
|
||||
./.venv/bin/python tools/release/release-catalog.py module-directory \
|
||||
--catalog ../addideas-govoplan-website/public/catalogs/v1/channels/stable.json \
|
||||
--keyring ../addideas-govoplan-website/public/catalogs/v1/keyring.json \
|
||||
--catalog ../govoplan-website/public/catalogs/v1/channels/stable.json \
|
||||
--keyring ../govoplan-website/public/catalogs/v1/keyring.json \
|
||||
--output-dir runtime/module-directory-preview \
|
||||
--channel stable
|
||||
```
|
||||
|
||||
@@ -98,4 +98,4 @@ Generated from `repositories.json`. Use that JSON file as the machine-readable s
|
||||
|
||||
| Repository | Subtype | Local path | Gitea |
|
||||
| --- | --- | --- | --- |
|
||||
| `addideas-govoplan-website` | `public-site` | `../addideas-govoplan-website` | [addideas-govoplan-website](https://git.add-ideas.de/add-ideas/addideas-govoplan-website) |
|
||||
| `govoplan-website` | `public-site` | `../govoplan-website` | [govoplan-website](https://git.add-ideas.de/add-ideas/govoplan-website) |
|
||||
|
||||
@@ -49,7 +49,7 @@ installed into a GovOPlaN runtime.
|
||||
|
||||
Current website repository:
|
||||
|
||||
- `addideas-govoplan-website`: public website and release catalog publication target.
|
||||
- `govoplan-website`: public website and release catalog publication target.
|
||||
|
||||
## Meta Repository Role
|
||||
|
||||
@@ -93,7 +93,7 @@ Current shared profiles:
|
||||
- `dev/postgres`
|
||||
- `dev/production-like`
|
||||
|
||||
Website-specific serving profiles stay with `addideas-govoplan-website`.
|
||||
Website-specific serving profiles stay with `govoplan-website`.
|
||||
|
||||
Module-specific test beds stay in the owning module repository. Examples:
|
||||
|
||||
@@ -104,13 +104,13 @@ Module-specific test beds stay in the owning module repository. Examples:
|
||||
This keeps local module tests close to the code while giving operators one
|
||||
repository for product deployment.
|
||||
|
||||
## addideas-govoplan-website and Release Logic
|
||||
## govoplan-website and Release Logic
|
||||
|
||||
`addideas-govoplan-website` should be treated as the public website and catalog publication
|
||||
`govoplan-website` should be treated as the public website and catalog publication
|
||||
target, not as the release orchestrator.
|
||||
|
||||
The release workflow should be invoked from `govoplan`. It may write signed
|
||||
catalog artifacts into `addideas-govoplan-website/public/catalogs/...` and then build or
|
||||
catalog artifacts into `govoplan-website/public/catalogs/...` and then build or
|
||||
deploy the website.
|
||||
|
||||
A separate `govoplan-release` repository should only be introduced if release
|
||||
|
||||
Reference in New Issue
Block a user