Why plesk creates directory and files with this permissions in laravel cache directory?
chmod -R 775 storage/
Related
In order to get WordPress updates and other functions of WP-ADMIN to work, I ran the following command to "fix" file persmissions.
sudo chown -R daemon:daemon /your-path-to-wordpress
This worked for the admin functionality, but now I am unable upload any files via ftp with user "bitnami". I can connect but not do anything else. How do I fix this to allow both WordPress admin updates to function and keep FTP access?
How to restore the default chown permissions on a default directory after installation of LAMP web server on my Raspberry pi? and how can I completely remove the LAMP web server?
chown changes ownership, not permissions. I dont know what you mean be default directory, but I would guess you mean the /var/www directory. To reset ownership to some default state, you could set it to the user owning your webserver. Normally www-data. Run ps aux | grep apache and check the user running apache. Afterwards set the directory owner to that user: chown -R user:group /var/www (probably chown -R www-data:www-data /var/www)
Complete removal is done by using the --purge flag: apt-get remove --purge apache2
If your webserver is not apache, just substitute apache with whatever server you are using. Eg ps aux | grep nginx
I'm deploying a PHP app on the AppEngine Flexible environment. I have a command in my post-deploy-cmd scripts in my composer.json file to set permissions for the public/app folder (chmod -R 755 public\/app). However, when I deploy my app, the entire public folder's permissions get overwritten with 550.
I can see in the logs that the following command runs right after my deployment commands - + chmod -R 550 /app/public
How can I run my command after that or stop that command from running at all? Any workarounds?
I've got a strange problem. After creating an application (CakePHP v2.4.9) I've deployed it to virtual server online. It wasn't working so I went through some steps:
chown -R user:group, chmod -R 775, checked for BOM, checked for mod_rewrite etc.
I've tried complete new application on server, same steps and nothing. Only after chmod -R 755, everything worked out.
Now, on a shared server, chmod -R 775 works great. What could cause this behavior? As far I can tell, 755 are less permissions than 775. Even chmod -R 777 wasn't the solution, only 755 was.
Virtual server PHP version: 5.4.27
Shared server PHP version: 4.4.9
Some servers are configured to not run files with permissions that are too open. Especially on shared hosting.
My sqlite db file is this: unable to open database file i chowned all folders until my dbfile to root. but i am still getting this error. but i remember that while creating my django project on server, i created a superuser, and now if i do ls -l i see that the user is that superuser. how is it possible to tell apache that this superuser should have that right to write/read the db file? or how to solve the problem, i am not apache/linux guru..
Execute chown www-data:www-data directory on the directory you want apache to be able to write to.
You should be able to just leave the file as owned by the super user and just change the group so that apache can read/write it as well.
Change the group for the sqlite file and the containing directory. Try this:
cd <directory with sqlite file>
sudo chgrp www-data . <sqlitefile>
You can find write group and www user and change permissions.
Say: cat /etc/passwd - for find right user, It may be apache or http or www.
And say to terminal: cat /etc/group -for find right group.
In my system group=apache, user = apache.