-
Notifications
You must be signed in to change notification settings - Fork 17
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
Request Entity Too Large & upgrade #87
Comments
Hello, Normally it's expected that the user don't customize config file managed by the app. So it's not an issue but the expected comportment. Now, I would like to know which file is too big to exceed 200M. We can change this parameter if it make sense. |
hello, |
In this case it should be better to just put |
We can expose this setup inside the yunohost webadmin ? I can try to make a PR. |
now that's interesting, but if it was made this way for everyone, wouldn't it there a risk to crash something for other people if a ressource is too hungry? @stilobique sure, such an option (a value to enter, or "unlimited") within the yunohost webadmin would probably be the best! |
Honestly I'm not sure that adding a specific settings in the control panel is the best solution. For not technical people a setting like this is quite confusing. For some others app I already set this to 0 avoid any issues and I didn't had any bad feedback about this. |
@Josue-T I don't understand why "non technical people" would need to use gitea, honestly... I've upgraded the latest gitea and forget about this issue, I've encountered the problem again (docker images are often more than 200 Mb....) |
Describe the bug
client_max_body_size
option in /etc/nginx/conf.d/domain.d/gitea.conf is maybe too small by default (200M), resulting in errors while pushing imagesExpected behavior
The text was updated successfully, but these errors were encountered: