Answer the question
In order to leave comments, you need to log in
Correct setting of the rights of file owners for the public folders of the web server + git?
Advise how to tighten the rights, use software for effective development, project support.
Problem: it is inconvenient now to make changes to the project, roll out updates, etc.
There are
- development
server - server for testing
- productive
software server:
- Red Hat linux everywhere
- apache everywhere
- git on the development server
Current settings in the public folder project:
- apache:apache on all files and folders
- 755 folders, 644 files
Essence
Without sudo it is impossible to change-create a file.
Impossible to commit git without sudo
workaround
Created a devgroup to which I added apache, developer users.
Changed the owner of apache:devgroup
Changed permissions to 775
The server admin just doesn't recommend changing anything in the access settings.
And my actions are therefore not particularly legal.
With my edits, too, no ice:
I upload the file via FTP (netbeans), the rights are automatically changed to smaller ones and the owner is changed to my user.
The question is how well the process of developing-supporting-updating the project should be organized with all the available junk ??
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question