documenting and translating env variables #958

Open
opened 2026-10-29 20:17:28 +00:00 by fauno · 3 comments
Owner

just leaving this here as an idea we discussed with @ChasquiLabo. in order to translate the .env.sample comments, currently we'd need to maintain a fork of each recipe with guaranteed merge conflicts.

but if the comments/documentation where to be separated in a language-specific file, each variable could have a better documentation and become translatable even with tools like weblate.

then abra app config could show both variables and their documentation on the operator's language just by merging both in a single file. and operators working on the same server reading different languages can collaborate :)

just leaving this here as an idea we discussed with @ChasquiLabo. in order to translate the .env.sample comments, currently we'd need to maintain a fork of each recipe with guaranteed merge conflicts. but if the comments/documentation where to be separated in a language-specific file, each variable could have a better documentation and become translatable even with tools like weblate. then `abra app config` could show both variables and their documentation on the operator's language just by merging both in a single file. and operators working on the same server reading different languages can collaborate :)
fauno added the enhancementi18n labels 2026-10-29 20:17:28 +00:00
Author
Owner

while adding features to different recipes a feedback i get often is that an env var should be documented and have some examples either on the .env.sample or the README, but it's difficult to map things on the README to the .env, and the .env feels like it shouldn't have a lot of text, so this proposal would also help with that i think.

while adding features to different recipes a feedback i get often is that an env var should be documented and have some examples either on the .env.sample or the README, but it's difficult to map things on the README to the .env, and the .env feels like it shouldn't have a lot of text, so this proposal would also help with that i think.
Owner

I have something like a recipe.yaml in my head where you can define env variables and their documentation (in different languages). Abra could then generate the env sample or part of the readme

I have something like a recipe.yaml in my head where you can define env variables and their documentation (in different languages). Abra could then generate the env sample or part of the readme
Owner
https://git.coopcloud.tech/toolshed/organising/issues/695
Sign in to join this conversation.
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/abra#958