Demonstrate native configuration authoring
This commit is contained in:
@@ -12,13 +12,17 @@ in the [configuration reference](../docs/config.md).
|
||||
- [Production-shaped pipeline](pipeline.production.yml): S3 storage, publish,
|
||||
external tools, and configured Scriptorium artifacts.
|
||||
- [Production-base/testing-overlay bundle](production-testing/pipeline.yml):
|
||||
explicit `conf.d` imports, one ordinary artifact per `artifacts/<key>.yml`,
|
||||
one family per `artifact-families/<key>.yml`, and the fixed
|
||||
explicit required `conf.d` imports, an optional local import, destination-mounted
|
||||
artifact files, a YAML-filtered directory of keyed families, and the fixed
|
||||
`overlays/testing.yml` overlay. Production values live in the base. The
|
||||
bundle demonstrates an input-only artifact dependency, two character families
|
||||
sharing the campaign party, and a testing-only disabled artifact. The testing
|
||||
overlay's `testing_notes` artifact inherits the recap prompt, inputs, and
|
||||
testing profile while retaining its disabled status and separate output path.
|
||||
The testing overlay upserts the transcript publish rule by `source`. A
|
||||
destination key defines each artifact ID; filenames do not. Full-root and
|
||||
disjoint definitions are also valid. Upsert replaces a matching list record
|
||||
as a whole; empty append or upsert contributions leave existing entries intact.
|
||||
Inspect it offline with:
|
||||
|
||||
```sh
|
||||
@@ -45,7 +49,9 @@ with the sample campaign and a compatible local- or S3-audio session.
|
||||
|
||||
- [Sample campaign](campaigns/sample-campaign/campaign.yml), its
|
||||
[session template](campaigns/sample-campaign/session.template.yml), and its
|
||||
adjacent stable inputs provide a complete campaign directory shape.
|
||||
adjacent stable inputs provide a complete campaign directory shape. Its
|
||||
imported settings and split party demonstrate local secondary imports;
|
||||
relative resources follow the file that supplies each value.
|
||||
- [Local-audio session](session.local-audio.yml) and
|
||||
[S3-audio session](session.s3-audio.yml) are concrete session files.
|
||||
- [Session template](session.template.yml) and the campaign-local equivalent
|
||||
@@ -78,8 +84,8 @@ names, or the Narratio credential lists must be changed to match. See the
|
||||
[Audita v2 migration guide](https://gitea.maximumdirect.net/eric/audita/src/tag/v2.0.0/docs/migrations/v2.md)
|
||||
for maintained downstream configuration examples.
|
||||
|
||||
For a deployed bundle, keep credential files out of source control in a
|
||||
`secrets/` directory beside the root `pipeline.yml`, one file per referenced
|
||||
For a deployed bundle, keep credential files out of source control in the
|
||||
conventional `/usr/local/etc/narratio/secrets` directory, one file per referenced
|
||||
environment-variable name, or select another directory with `--secrets-dir`.
|
||||
Static S3 credentials are optional: omit both S3 credential references to use
|
||||
the AWS SDK discovery chain.
|
||||
|
||||
Reference in New Issue
Block a user