Are they needed? I just deployed correctly without them, since they're only used on the app.ini template
> Missing the `compose.*yml` threading of env vars?
Are they needed? I just deployed correctly without them, since they're only used on the app.ini template
I'm pretty sure you can deploy without them but then if you run env | grep GITEA_ENABLE_PUSH_CREATE_USERinside the container, it won't be exposed in the environment? The app_ini is in the config of the service.
I'm pretty sure you can deploy without them but then if you run `env | grep GITEA_ENABLE_PUSH_CREATE_USER`inside the container, it won't be exposed in the environment? The `app_ini` is in the config of the service.
inside the container, it won't be exposed in the environment?
yeah i think that'd happened, but it's not required since gitea is already ignoring env vars prefixed GITEA_. i can add them if it's least surprise for operators
> inside the container, it won't be exposed in the environment?
yeah i think that'd happened, but it's not required since gitea is already ignoring env vars prefixed GITEA_. i can add them if it's least surprise for operators
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.
Missing the
compose.*ymlthreading of env vars?Are they needed? I just deployed correctly without them, since they're only used on the app.ini template
I'm pretty sure you can deploy without them but then if you run
env | grep GITEA_ENABLE_PUSH_CREATE_USERinside the container, it won't be exposed in the environment? Theapp_iniis in the config of the service.yeah i think that'd happened, but it's not required since gitea is already ignoring env vars prefixed GITEA_. i can add them if it's least surprise for operators
i'm waiting for approval on this pr before releasing :D
Ahhh I get it with the env var / template stuff, thanks!