Differences

This shows you the differences between two versions of the page.

--- archive_blog_service [2006/05/28 12:20] – _bung
+++ archive_blog_service [2026/09/27 04:07] (current) – removed - external edit (Unknown date) 127.0.0.1
@@ Line 1: / Line 1: @@
-Tardis has wordpress 2.0.1 installed now
-Wordpress isn't really designed out of the box for mass hosting. Wordpress on debian makes some changes in order to deal with multiple sites, but it isn't really suited for us either. For now I'm looking at doing the following. Users can have their own blogs hosted off http://blog.tardis.ed.ac.uk/<user>/ . This will read the config from /var/autofs/www/users/<user>/webconf/blog-config.php following some rewriting in our hacked up version of the debian master config.
-You should get an admin to create /var/autofs/www/users/<user>/webconfig/ with perms 0750 <user>:www-data
-This will allow the webserver to read the config, but not allow other users to do so.
-A sample configuration would look like
-<code>
-<?php
-// ** MySQL settings ** //
-define('DB_NAME',       'kev');            // The name of the database
-define('DB_USER',       'kev');            // Your MySQL username
-define('DB_PASSWORD',   'BIGMASSIVECATS'); // ...and password
-define('DB_HOST',       'db');
-// You can have multiple installations in one database if you give each a unique prefix
-$table_prefix  = 'wp_';   // Only numbers, letters, and underscores please!
-?>
-</code>
-Users will still need a MySQL database, and have tables on that database configured for use with wordpress. I'll check out our [[my_sql_service|MySQL docs]] now to see what access we give to users.
-Uploads may (or may not) be set up in a dodgy way. The same filespace is used for everyone, so we may find users can overwrite other users stuff. Testing would be nice. So would users.