In fact, you should prevent this regardless of the scripts you run or even if you don't set Apache user to yourself since you probably don't want random outsiders to be able to see the contents of your localhost. But since this is just a local development environment, that shouldn't be a problem unless you have no rules to block Apache in your firewall and let questionable files like file explorers, shells, scripts that may contain vulnerabilities run under Apache in which case anyone including your public wifi neighbor in a cafe can enter and do whatever those scripts let them to do. Own them: $ sudo chown joao: /var/tmp/sess_*Īfter this, Apache (and PHP et al.) will run as you and will gain read/write permission to all of the files you have read/write permission. If you have active sessions, they are going to give permission errors since they are still owned by _www. In /private/etc/apache2/nf, set User to your username from _User _wwwĪnd then restart Apache: $ sudo apachectl restart I generally fix this by setting the Apache user to myself in local environments and in machines where the only user who uses Apache is me.
I spent a long while chmodding and messing with _Eventually, I just checked the "shared folder" checkbox in the Finder for that folder, and it worked, on the specified domain, with php active, the way I wanted it to. I have an alias specified in OSX server pointing to a user directory.