On Sat, Mar 25, 2006 at 09:49:47PM +0100, frantisek holop wrote:
> hmm, on Sat, Mar 25, 2006 at 09:36:38PM +0100, Joachim Schipper said that
> > On Sat, Mar 25, 2006 at 09:06:17PM +0100, frantisek holop wrote:
> > > hi there,
> > >
> > > i am trying to make a port of textpattern.
> > > this is a regular php+mysql web application cms.
> > >
> > > naturally i went had a look at other web application Makefiles already
> > > in the ports.
> > >
> > > i noticed that most of them (wordpress, smarty, horde) install into
> > > /var/www/ instead of /var/www/htdocs and symlink back.
> >
> > I don't have much of an opinion about the rest, but I'd imagine that
> > installing into /var/www gives the administrator that much more freedom.
> > Not all wordpress installations are necessarily rooted at
> > (/var/www/htdocs)/wordpress, for instance - quite a few will be at the
> > root of the webpage.
>
> this is certainly an argument to think about.
>
> as i see it, htdocs is a kind of second level jail for me, i prefer stuff
> that should be exposed to the world in htdocs. /var/www is great
> for libs and modules which should not be accessible directly from the
> web, only thru a particular app (horde is right in this i guess).
>
> i find it natural to expect a web app to install stuff under
> htdocs and not "polluting" /var/www .
>
> also i think quite a few admins will leave the name "wordpress" (in this
> case) in the url or htocs namespace.... and so i would prefer to
> install everything in htdocs and let the admin decide what to do with
> it further down the line. in other words, a "vanilla" install.
But what happens if you try to update the package?
Plus, I'm pretty certain I wouldn't want my website rooted under
/wordpress.
Oh well, does anyone with more experience/clout than me have an opinion?
Joachim
