You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 16, 2023. It is now read-only.
Description
I faced a couple of problems while setting up the development environment using vagrant up. Many of them were system dependent which were fixed by simple manual overrides. However I saw that there are some permission issues while launching librecores.devel/ that it can't get permissions to write into cache/ and logs/ directory.
Issue Logs
1. Unable to create the storage directory (/var/www/lc/site/var/cache/dev/profiler).
2. Unable to write into (/var/www/lc/site/var/cache/dev/easy_admin). The file is not writable.
Possible Fixes
After some time of searching I found that these are some common permission issues in the filesystem. So the simple fix was chmod or chown. However either of them didn't work for me inside the vagrant virtual-machine until this solution did. Turns out it was a common issue for vagrant as well.
@imphil Do you want these mount_options and owner fields added to our Vagrantfile that would fix this issue for many of the users?
The text was updated successfully, but these errors were encountered:
I thought we already have all required options in the Vagrantfile, but since all of this is a bit of mess, it could be that we're missing something. Would you mind doing a PR with the proposed changes?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
OS: Fedora 29
Description
I faced a couple of problems while setting up the development environment using
vagrant up
. Many of them were system dependent which were fixed by simple manual overrides. However I saw that there are some permission issues while launchinglibrecores.devel/
that it can't get permissions to write intocache/
andlogs/
directory.Issue Logs
Possible Fixes
After some time of searching I found that these are some common permission issues in the filesystem. So the simple fix was
chmod
orchown
. However either of them didn't work for me inside the vagrant virtual-machine until this solution did. Turns out it was a common issue for vagrant as well.@imphil Do you want these
mount_options
andowner
fields added to our Vagrantfile that would fix this issue for many of the users?The text was updated successfully, but these errors were encountered: