NYCPHP Meetup

[Anthony Wlodarski]

I myself have used the "/var/www/www.domainname.com" method myself.  Another
scheme I find worthwhile is to do "/var/www/apps/applciation_name" so I
don't need clog the doc root with URL's depending on the client.

-Anthony

On Wed, Jul 1, 2009 at 11:04 AM, Hans Zaunere <lists at zaunere.com> wrote:

> > Perhaps this is one of those things that doesn't matter a helluva lot,
> > but:  when you have a freshly installed Debian-style LAMP (actually
> > Ubuntu server 9.04) and you are looking for a place in the filesystem
> > to install your PHP application files -- where do you like to put them?
> > /usr/local/share/... ? Or /usr/local/lib/php/... ? /opt/...?
>
> Assuming a fairly well organized application:
>
> /usr/local/include/php/com.domainname.www   <-- backend code
>
> /var/www/www.domainname.com   <-- document
> root/front-end/css/images/js/etc
>
> Why?  Yeah, because I'm crazy...
>
> > It's nice if it isn't /something/too/terribly/hideously/long/to/type
> > although there are always shortcuts, like environment vars.
>
> And symlinks.
>
> H
>
>
> _______________________________________________
> New York PHP User Group Community Talk Mailing List
> http://lists.nyphp.org/mailman/listinfo/talk
>
> http://www.nyphp.org/show_participation.php
>



-- 
Anthony W.
ant92083 at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nyphp.org/pipermail/talk/attachments/20090701/25505195/attachment.html>