> When a developers needs an apache instance to play with, they would > typically just do something like this: > '/usr/local/sbin/httpd -f /home/foo/proj/conf/httpd.conf'. The only > things they need in conf are the httpd.conf, mime.types and magic. > Typically, they'll declare a server root in the conf file, with a logs > folder below server root. That's pretty muc hall that is needed. Developer playgrounds are something else, and they run them as they please on their workstations. I was describing what we do for shared servers with dev/qa/production workflow stacks. Per security policy, nobody is allowed to run a site out of their home directory (or even have a login on QA or production), and we don't have any of the stack software in /usr/local even on sites which haven't been merged into an /opt/site/sitename stack so they can easily be copied from machine to machine. As with anything else, YMMV with your environment. I probably would consider your setup a little crazy with the kind of superficial exposure we get here, starting with running httpd out of /usr/local (assuming you'll ever want to compile a second version for any reason). > However, we don't do this so much anymore. Now typically, we will > configure a separate freebsd jail for each service. I'd like to be doing something like that, or VMs, but unfortunately those methods have not been so easy to get approved. Sheryl --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|