It is very important that the naming convention of the config matches the whole way down. In the above example, that is nginx_config in the configs: stanza, nginx_config in name: ${STACK_NAME}nginx_config${NGINX_CONFIG_VERSION} and finally NGINX_CONFIG_VERSION in the abra.sh. This is the naming convention that abra will perform to carry out the lookup of all matching names/values. See #693 for more.
From the Good Work of @nicksellen
> https://codeberg.org/nicksellen/gists/src/branch/main/2026-01-02-hometown-migration.md#spurious-warnings
I believe this is due to 👇
https://git.coopcloud.tech/coop-cloud/mastodon/src/commit/7f1ba44869bbcd77c593bb79ecff7fb37229a1ea/compose.yml#L242-L243
`entrypoint_sh` != `entrypoint_conf`
> https://docs.coopcloud.tech/maintainers/handbook/#manage-configs
>
> It is very important that the naming convention of the config matches the whole way down. In the above example, that is nginx_config in the configs: stanza, nginx_config in name: ${STACK_NAME}_nginx_config_${NGINX_CONFIG_VERSION} and finally NGINX_CONFIG_VERSION in the abra.sh. This is the naming convention that abra will perform to carry out the lookup of all matching names/values. See #693 for more.
Seems like a custom validator could be useful to run in CI. I had a quick peak at yamllint, but you can't add custom rules. Wouldn't be too hard to write a script, although probably better to be done in golang and included in abra.
Seems like a custom validator could be useful to run in CI. I had a quick peak at yamllint, but you can't add custom rules. Wouldn't be _too_ hard to write a script, although probably better to be done in golang and included in abra.
I think let's meditate on the general linting in toolshed/abra#747 indeed.
For Mastodon, I think a zero-impact quick-fix could be to change entrypoint_sh to entrypoint_conf? I'll try that out ASAPest.
I think let's meditate on the general linting in toolshed/abra#747 indeed.
For Mastodon, I think a zero-impact quick-fix could be to change `entrypoint_sh` to `entrypoint_conf`? I'll try that out ASAPest.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
From the Good Work of @nicksellen
I believe this is due to 👇
entrypoint_sh!=entrypoint_confSeems like a custom validator could be useful to run in CI. I had a quick peak at yamllint, but you can't add custom rules. Wouldn't be too hard to write a script, although probably better to be done in golang and included in abra.
I think let's meditate on the general linting in toolshed/abra#747 indeed.
For Mastodon, I think a zero-impact quick-fix could be to change
entrypoint_shtoentrypoint_conf? I'll try that out ASAPest.