Wordpress package default installation

[Ryan Schmidt]

On Apr 6, 2012, at 10:29, Michael Parchet wrote:

> Why the wordpress package is installed in www folder and isn't into apache2 htdocs folder by default ?

There hasn't been any great effort to standardize how the various web app ports work. In my opinion, they should probably all install into a directory ${prefix}/www/${name}. It is then up to the user to configure their web server to use the software from that location.

The ports should not install into ${prefix}/apache2/htdocs because most of them do not specifically require the apache2 server; they would probably work fine with other web servers like lighttpd or nginx.

I might not be opposed to a webapp portgroup that somehow automates the task of configuring popular web servers to expose a given web app at a predictable URL. This might involve modifying each web server so that it looks for additional config files in a particular directory, then having the webapp portgroup write a config file for each such web server. The webapp could even add a notes entry telling the user what URL to open to use the web app. That would be pretty nice.

On the other hand, it's hard to anticipate where a user will want the web app exposed in the web space. For a user's personal development machine, sure, we could default to making e.g. phpmyadmin available at http://localhost/phpmyadmin. But what about a production server? What if this server serves several vhosts? Should we expose the web apps on the default vhost only? Or all of them? What if the user wants each web app available at its own vhost? Since there is so much variation possible, it may be simplest to just install the web app's files, and leave configuring the web server to serve them up to the individual user.