-
-
Notifications
You must be signed in to change notification settings - Fork 958
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adjust DEFAULT_PULL_MESSAGE in docker compose #7204
Comments
This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you! |
This issue seems to be a good fit for newbie contributors. You are welcome to contribute to Weblate! Don't hesitate to ask any questions you would have while implementing this. You can learn about how to get started in our contributors documentation. |
I've since had some time to experiment with this. I've tried setting I've therefore taken a look at the code and found these parts for weblate/weblate/settings_docker.py Lines 229 to 242 in c32f48f
I suppose adding How long do you suppose the review process will take for such a small addition? Would it be useful to build and deploy my own image to for the time being until a new release is made? |
Allow changing `DEFAULT_PULL_MESSAGE` in a docker compose environment using the environment variable `WEBLATE_DEFAULT_PULL_MESSAGE`. Document behaviour in `docker.rst` and `config.rst`. Closes #7204
Thank you for your report; the issue you have reported has just been fixed.
|
Describe the issue
I'd like to adjust
DEFAULT_PULL_MESSAGE
in my docker compose setup.This is currently not possible and not documented in https://docs.weblate.org/en/weblate-4.10.1/admin/install/docker.html?highlight=pull%20request#docker-environment-variables.
I already tried
Steps to reproduce the behavior
No response
Expected behavior
No response
Screenshots
No response
Exception traceback
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: