Editing your config on the dashboard

Your appmecca.yaml lives in your repository, and that stays the normal way to change it. But you can also edit an app's config on the dashboard, which is useful in two cases:

• your repository has no appmecca.yaml yet and you want the app running before you commit one;
• you want to change a value without a commit and a rebuild.

Open it at your group → the app → Config.

Two editors, one config

The Config tab offers two ways to edit the same thing.

The field editor lists every value your config already sets, one row each, and lets you change them. It is the safer of the two: you cannot mistype a key, because you are not typing keys.

Edit as YAML gives you the whole config as text. Use it when the field editor cannot express what you need — adding a section your repository does not define, editing a list, or pasting a config you already have.

Both save to the same place and are validated the same way.

Your repository still wins where you have not overridden

The dashboard's config is applied on top of your repository's, field by field. Change one value here and everything else keeps following your repository — so a later commit still flows through for every field you did not touch.

That is also why there is one thing you cannot do here:

Deleting a line does not unset a field

Because the dashboard's config is layered on top, there is no way to express "unset this". If you delete a field your repository defines, the save is refused and names the field — rather than being accepted and quietly doing nothing.

To remove a field, remove it in appmecca.yaml.

If your app has no config yet

An app whose repository has no appmecca.yaml is quarantined: it will not build or deploy, and the app page shows the verdict instead of the usual tabs. That card now has a Configure button — write a config there and the app is unblocked without touching your repository.

If you would rather be asked questions than write YAML, the card also links to the config wizard. The wizard gives you a file to commit, so after you commit it press Re-check on the app.

What happens when you save

Saving re-runs the repository check automatically, because a config change can make an app buildable — or unbuildable. The result appears on the app within a few seconds.

Occasionally the save succeeds but the re-check cannot be queued. The editor says so and asks you to press Re-check; your config is saved either way.

Some changes take effect immediately and some need a deploy. The editor tells you which after each save.

Common refusals

What you see	What it means
That is not valid YAML: … line 4, column 3	A syntax error, with the position. Indentation is the usual cause.
That YAML is not a config object	The document parsed, but to a list or a bare value rather than a set of top-level keys.
Removing a field the repository defines is not supported here	See the warning above — remove it in appmecca.yaml.
containers section is required…	The merged config is not a valid appmecca.yaml. The message is the same validation your repository's file gets.

Quoting matters in YAML

no, on, yes and off are booleans in YAML, 22:30 is a number, and 1.10 is the float 1.1. If you mean the text, quote it: note: "no".

This is why the platform reads your YAML with the same parser that reads the file out of your repository — so what you see on the dashboard is what a commit would have done.