Skip to content
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

[QUESTION] @linux people: Which rights does the /public/avatars folder really need ? #143

Closed
panique opened this issue Aug 16, 2013 · 4 comments
Labels

Comments

@panique
Copy link
Owner

panique commented Aug 16, 2013

Can somebody please specify which rights the /public/avatars folder in 4-full-mvc-framework really needs ? The script didn't wrote into that folder until I changed the rights to 777 (which is too much imo). Everything below 777 didn't work :(

The setup is a simply-as-possible ubuntu/apache2/mysql/php stack, no stunts, no special configs, nothing unusual.

Goal is to give users a clean info on how to make that folder writeable.

@panique
Copy link
Owner Author

panique commented Aug 16, 2013

The readme says 775 btw

@panique
Copy link
Owner Author

panique commented Aug 16, 2013

Quote from StackOverflow:

755 will be enough if the server owns the directory, 775 if the server does not own the directory, but is in the same group. if neither matches, he should chown the directory to the server, not make it writable for everyone

Reality is, that in my current setup only 777 (!) works. Weird linux.

@GrahamCampbell
Copy link
Contributor

@panique I have a similar problem too with some of my apps when using apache. I just roll with 777, and all's good.

@panique
Copy link
Owner Author

panique commented Aug 20, 2013

POSSIBLE SOLUTION: this depends under which user you have installed apache / php ! As servers are usually delivered with root-password, people tend to install everything directly as the root user. Like me ;)

This goes to far to a login script, so we should put some information about this into the install instruction in the readme.md, but not go into detail on how to setup a server "correctly".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants