FS#50378 - [gitlab] Assets need to be in /var
Attached to Project:
Arch Linux
Opened by Tobias Hunger (hunger) - Saturday, 13 August 2016, 03:15 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 29 August 2016, 22:57 GMT
Opened by Tobias Hunger (hunger) - Saturday, 13 August 2016, 03:15 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 29 August 2016, 22:57 GMT
|
Details
Description:
Assets need to be in /var/lib/gitlab, not in /usr. Additional info: * 8.10.4-2 Steps to reproduce: * Upgrade gitlab * Try to upgrade the assets Expected Result: * Assets are updated Actual Result: * Access to assets is denied since /usr is read-only. This can be fixed by moving /usr/share/webapps/gitlab/public/assets to /var/lib/gitlab/assets and then creating a symlink. |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Monday, 29 August 2016, 22:57 GMT
Reason for closing: Not a bug
Monday, 29 August 2016, 22:57 GMT
Reason for closing: Not a bug
In addition to that: I also see no reason for a web-accessible piece of software to be able to write files in /usr. In fact nothing but a package manager should ever write into /usr *ever*. So I mount /usr from a read-only btrfs snapshot. But that is a personal setup issue:)
I grabbed a script to update my gitlab installations and that includes an update of the assets. That might actually be unnecessary with the package...
Need to test that:)