[wp-hackers] [hendry@cs.helsinki.fi: Asking for directions]

[Kai Hendry]

Apologies for joining the "multi-blog" discussion a bit late. I am working
on the Debian project on the subject of Web Application packaging:
http://lists.debian.org/debian-devel/2004/08/msg01104.html

Don't like that word "multi-blog". Deployments or multiple instances of
WP sounds a bit better. This whole web application packaging art is
still very much unchartered territory. I've yet to voice my concerns to
W3 TAG as I don't have anything constructive to say yet. ;)

I did skim read the thread started by Tara:
http://wordpress.org/pipermail/hackers_wordpress.org/2004-August/001195.html

And the weblog entries of Ruben and Stephanie (aka Tara?).

I am a bit concerned about this need for other mysql users. Can't
wordpress manage its own users?
I see HTTP_HOST doesn't seem to be enough. Selling a DNS dependency for
a web application does seem to be a tall order.

Below is a mail I wrote about my concerns on the matter after packaging
WP for Debian directly to Matt:

Summary: Use the one database and one user and leave the FS alone
pleasie except for one file: wp-config.php and a symlink. 

Best wishes,

----- Forwarded message from Kai Hendry <hendry at cs.helsinki.fi> -----

From: Kai Hendry <hendry at cs.helsinki.fi>
To: Matt Mullenweg <m at mullenweg.com>
Subject: Asking for directions
Date: Wed, 11 Aug 2004 22:59:49 +0300

http://wordpress.org/development/archives/2004/05/28/the-road-ahead/

Regarding "multiple blogs". Typical Debian users with vhost aliasing
I'll assume just want to:

ln -s /usr/share/wordpress /web/wp.natalian.org
ln -s /usr/share/wordpress /web/anotherblog.natalian.org
ln -s /usr/share/wordpress /web/andanother.dabase.com

Then wordpress notices the HTTP_HOST and serves the right blog, for the
right vhost. All the users and stuff are in the one wordpress database.

bilbo$ sudo cat /etc/wordpress/wp-config.php
<?php
/** WordPress's debianised config file **/

define('DB_NAME', 'wordpress');
define('DB_USER', 'wordpress');
define('DB_PASSWORD', 'ZcgBJb6Q4IWYjLGg');
define('DB_HOST', 'localhost');

$table_prefix  = 'wp_';

$server = DB_HOST;
$loginsql = DB_USER;
$passsql = DB_PASSWORD;
$base = DB_NAME;

define('ABSPATH', dirname(__FILE__).'/');

require_once(ABSPATH.'wp-settings.php');



I do not want to see more than one wp-config.php or more table_prefixes.
WP could imo manage this in one db.

As for the right index.php and .css for each of the vhosts. It would be also be
nice if wordpress managed this instead of Debian.

----- End forwarded message -----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : /pipermail/hackers_wordpress.org/attachments/20040827/7c43acf9/attachment.bin