Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
wp-content folder permission issues #12
@karellm I'm trying to begin developing a wordpress theme.
I clone this repo, cd into repo's folder, do
From another terminal I cd to the repo's directory, a new folder has been created,
Since I began using wordpress-starter two weeks ago, I had the same problem as @vlkz: every time I restart the container, I need to change the permission of volumed files in wp-content before I can edit and save them.
I thought this was normal but it probably isn't. Why aren't the file permissions 664 instead of 644 in run.sh? This way I can simply add myself to the
Or have I missed something obvious in the tutorial?
I just hit this with the themes folder and the plugin folder. It was being mounted as docker:staff. The files could not be read by apache(WP). Using boot2docker.
Narrowed it down to this issue: boot2docker/boot2docker#581
Which brought be to the following workaround(once container is built, inside container run):
This is making it so the mounted volumes and the user running apache are the same UID. Was going to put in a PR for this when I got a second. Just spent about 4-5 hours trying to get this to work on my end.
Thanks @dsifford . Needed to understand what the heck was going on before I attempted a review. Spent several hours understanding how your entire process was working, where docker/vbox/boot2docker all play together. I am rather new to docker, so I had to do a big lift to get the understanding.