pattern-shop-tracker settings
What pattern-shop-tracker needs from you before it installs. It goes in one small file, pattern-shop-tracker.yaml, which you pass to
helm install and helm upgrade after site.yaml, as Install shows.
Starter file
pattern-shop-tracker.yaml holds every setting on this page with its description. Save it, replace each
<PLACEHOLDER> and remove the optional lines you don't need.
pattern-shop-tracker.schema.json describes the file to editors that check YAML against a JSON schema.
Settings
Plain values, under settings in pattern-shop-tracker.yaml.
| Setting | Required | Default | Description |
|---|---|---|---|
settings.adminRole | No | "admin" | The name of the role that lets a person edit the pattern shop's parts, customers and employees; leave it out unless people sign in through an app registration of your own that names the role differently, such as PatternShopTracker.Admin |
Made for you
The platform makes these once and keeps them in the Secret pattern-shop-tracker-generated. There is nothing to set.
SESSION_SECRET
In site.yaml
pattern-shop-tracker answers on pattern-shop.<domain>, under your global.rigfab.domain. To give it another name, set
global.rigfab.hosts.pattern-shop to the full host name.
Check before you install
Once the base chart is installed, and before you install or upgrade this product:
rft check --chart oci://registry.rigfab.com/rft/apps/pattern-shop-tracker/charts/pattern-shop-tracker --version <VERSION> --release pattern-shop-tracker --namespace rft-app-pattern-shop-tracker --values site.yaml --values pattern-shop-tracker.yamlIt renders the chart with your files and asks the cluster whether it would accept the result, and changes
nothing. A setting that is missing or misspelt in your files stops it with a message that names the setting. It
doesn't look inside a Secret of your own. A misspelt name under global.rigfab is the base chart's to refuse, so
check site.yaml with the base chart after every change to it, as Install shows.