Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
millido4383yYou have double-checked ownership? Your user could be "hated" even though permissions are 777
I know this.
If you for example:
- add yourself to a specific group
- allow that group to write to a directory
- restart your shell/terminal
and you still can't write to it.
You can in this case either:
- Restart your computer (logout + login may work too)
- Run "$ su -" (gives you a session where it should work)
Also a nifty trick:
Use "# chown g+s DIRECTORY -R" to not change the group when creating files/folders.
Especially handy when you copy files as root into a directory and cant delete these files with you regular user/group.
alkuzad15373yCheck acl too, basic permissions are basic
Might be worth looking up its SELinux label providing its a RHEL based OS. "ls -Z"
@andros705 nah, it's a random directory created on the fly, with chmod 775 by default which is more than fine to begin with, and all of that inside a Laravel project
While Laravel, with such configuration, can write without trouble in this directory, Intervention Image, an external library, CAN'T. WHY.
foniho34238dEver heard of SELinux you absolute muppet?
I bet you've either forgotten to (re)label your file contexts or are writing to a segregated temporary directory (i.e. your /tmp isn't actually in /tmp.)