docs/maintainers/handbook.md aktualisiert #278

Merged
lambdabundesverband merged 2 commits from lambdabundesverband-patch-1 into main 2025-10-08 12:45:34 +00:00

Thats how I until now understood process of adding an env var. Thought it might help other's who are new. I am very open to suggestions, other best practices, corrected typos...

Thats how I until now understood process of adding an env var. Thought it might help other's who are new. I am very open to suggestions, other best practices, corrected typos...
lambdabundesverband added 1 commit 2025-06-04 16:41:00 +00:00
Thats how I until now understood process of adding an env var. Thought it might help other's who are new. I am very open to suggestions, other best practices, corrected typos...
decentral1se reviewed 2025-06-05 07:58:05 +00:00
decentral1se left a comment
Owner

💖

💖
@ -127,0 +135,4 @@
# ... other existing envs
```
With `${REQUIRE_AUTH_FOR_PROFILE_REQUESTS:-false}` you set a default value (`false`), ensuring not to break existing deployments.
Owner

I think the only missing point here is that you know sometimes you are breaking stuff. In that case, you can let the rest know they need to take action with a release note. I think that would be a good addition to add somewhere.

I think the only missing point here is that you know sometimes you are breaking stuff. In that case, you can let the rest know they need to take action with [a release note](https://docs.coopcloud.tech/maintainers/handbook/#how-do-i-write-version-release-notes). I think that would be a good addition to add somewhere.
decentral1se marked this conversation as resolved
lambdabundesverband added 1 commit 2025-06-05 09:13:51 +00:00
Author
Member

thanks, added this advice.

thanks, added this advice.
p4u1 requested changes 2025-07-04 06:20:39 +00:00
@ -127,0 +151,4 @@
#REQUIRE_AUTH_FOR_PROFILE_REQUESTS=true
```
3. now you can use the environment-variable in your `.tmpl` files, e.g. add to `homserver.yaml.tmpl`
Member

I think when you use env vars in .tmpl files you don't need to set the environment variable in the docker-compose file. You could split the example in two:

  1. adding a new env variable to a compose file
  2. adding a new env variable to a .tmpl file
I think when you use env vars in .tmpl files you don't need to set the environment variable in the docker-compose file. You could split the example in two: 1. adding a new env variable to a compose file 2. adding a new env variable to a .tmpl file
Author
Member

Thanks for the idea.

I don't have time at the moment to do this, but I keep that in mind and would use the next time I add an env var to a recipe to update this :)

Thanks for the idea. I don't have time at the moment to do this, but I keep that in mind and would use the next time I add an env var to a recipe to update this :)
Owner

@lambdabundesverband any updates on this one?

@lambdabundesverband any updates on this one?
lambdabundesverband merged commit b882b102fa into main 2025-10-08 12:45:34 +00:00
Author
Member

ah sorry I lost track of this. now i did "rebase" here and wasn't aware that would directly merge to main. hope i didn't break something @decentral1se

ah sorry I lost track of this. now i did "rebase" here and wasn't aware that would directly merge to main. hope i didn't break something @decentral1se
Owner

That's cool, it's done so @lambdabundesverband 😃 Idk if you wanna loop back and deal with https://git.coopcloud.tech/toolshed/docs.coopcloud.tech/pulls/278/files#issuecomment-25086 but it's up to you! Feel free to do whatever. Thanks!

That's cool, it's done so @lambdabundesverband 😃 Idk if you wanna loop back and deal with https://git.coopcloud.tech/toolshed/docs.coopcloud.tech/pulls/278/files#issuecomment-25086 but it's up to you! Feel free to do whatever. Thanks!
Sign in to join this conversation.
No Reviewers
No Label
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/docs.coopcloud.tech#278
No description provided.