3 ms·
FWIW I have a /private directory in the root of all vhosts, so it looks like: /srv/www/domain.com/public_html/ |--------->/private/
by thaumaturgy 11y ago
FWIW I have a /private directory in the root of all vhosts, so it looks like:
/srv/www/domain.com/public_html/
|--------->/private/
|--------->/logs/
|--------->/tmp/
Anything stored in /private/ is not publicly accessible by the web server process, but can be read or written by anything running under the user's username.
It's specifically for storing things like configuration files.
I think this should be standard practice.
- raquo 11y agoWhy do you store such stuff under /public_html anyway? One level higher would be more appropriate I think.
- thaumaturgy 11y agoIt's not under public_html. It's under /srv/www/domain.com. It is one level higher.
- raquo 11y agoOh, that makes more sense. Sorry I got confused by the ascii tree.
- dangero 11y agoThanks for the tip. How do you keep passwords and keys in sync amongst team members safely?
- thaumaturgy 11y agoI only just recently had to figure that out. I opted for setting up a .kdb KeePass file in a private git repo and giving everyone ("everyone" = myself + one other) access to that. I'm pretty sure that's not a very good solution.