When installing several instances of wordpress with the webapp-config tools, the wordpress/wp-config.php contains a unique password and database name for all websites (USE="vhosts"). This make the installation useless if you want to install wordpress for many hosts. Looking at the wordpress-2.0.3.ebuild, I'd rather see something similar to this: webapp_serverowned ${MY_HTDOCSDIR}/wp-settings.php webapp_serverowned -R ${MY_HTDOCSDIR}/wp-admin webapp_serverowned -R ${MY_HTDOCSDIR}/wp-includes webapp_configfile ${MY_HTDOCSDIR}/wp-config.php rather than: webapp_serverowned ${MY_HTDOCSDIR}/index.php webapp_serverowned ${MY_HTDOCSDIR}/wp-admin/menu.php webapp_serverowned ${MY_HTDOCSDIR} Also: the following instructions cause the emerge to fail in case you unmerge then re-emerge wordpress, it won't find the local docs="license.txt readme.html" files. dodoc ${docs} for doc in ${docs} INSTALL; do rm -f ${doc} done
Sorry, that you *can* use multiple instances of WordPress within a single database doesn't mean I want to be responsible for supporting it. It's not the way it was designed. One install, one database. That's how it was made, anything else is a kludge. As to the second issue... WORKSFORME.
That's exactly my problem, the webapp-config won't let me install different databases, all the 'wp-config.php' files point to the same database and username, it's not what I want!!! Each time I make a new WordPress installation via webapp-config the wp-config.php in all vhosts are reset to the same unique database. (In reply to comment #1) > Sorry, that you *can* use multiple instances of WordPress within a single > database doesn't mean I want to be responsible for supporting it. It's not the > way it was designed. One install, one database. That's how it was made, > anything else is a kludge. > > As to the second issue... WORKSFORME. >
Aaron, What's the problem w/ marking wp-config.php as webapp_configfile? Eric's problem is happening because wp-config.php in /var/www/... is a hard-link to the copy in /usr/share/webapps/... . Marking the file as webapp_configfile will stop this happening. Best regards, Stu
Fixed in 2.0.5
