http://wiki.dreamwidth.net/wiki/api.php?action=feedcontributions&user=124.6.182.55&feedformat=atomDreamwidth Notes - User contributions [en]2024-03-29T07:55:17ZUser contributionsMediaWiki 1.23.0//wiki.dreamwidth.net/wiki/index.php/Talk:Dreamwidth_Scratch_InstallationTalk:Dreamwidth Scratch Installation2009-05-18T03:01:17Z<p>124.6.182.55: ask about warning</p>
<hr />
<div>Is the warning about needing dw-nonfree still necessary? From feedback from folks on IRC I'm under the impression we don't need it anymore if all we want is to get a basic installation up and running. <br />
<br />
(Though we still have some assumptions made in the payments system, etc, which means we're not fully ready to start a new production installation out of the box. Much closer, though!)<br />
<br />
- Afuna</div>124.6.182.55//wiki.dreamwidth.net/wiki/index.php/Dreamwidth_Scratch_InstallationDreamwidth Scratch Installation2009-05-18T02:54:12Z<p>124.6.182.55: add instructions to install bundle::cpan</p>
<hr />
<div>These are the instructions to install a Dreamwidth system from scratch, assuming you are running Ubuntu. See [[Setting up Dreamwidth on Linode]] for instructions on setting up a system to the point where you can log in and start this. After you set up, you can keep updated with the instructions on [[Dev Maintenance]].<br />
<br />
If you have difficulties or problems or suggestions for installation procedures, please report them to [http://www.dwscoalition.org/show_bug.cgi?id=61 Bug 61]. Also look at [[Production Setup: Webserver]]. <br />
<br />
== Bringing the system up to date ==<br />
<br />
Before you start installing anything else, you might want to make sure your system is up to date. You should log in as root and update the packages on your system:<br />
<br />
apt-get update<br />
apt-get upgrade<br />
<br />
If you want man pages on your system: <br />
<br />
apt-get install man<br />
<br />
== Installing necessary packages ==<br />
<br />
This will install necessary packages you'll need to run Dreamwidth. You'll want to be root when running these commands.<br />
<br />
apt-get install mercurial subversion apache2-mpm-prefork \<br />
libapache2-mod-perl2 libapache2-mod-apreq2 libapache2-request-perl \<br />
mysql-server wget unzip links vim libclass-autouse-perl \<br />
libcompress-zlib-perl libdatetime-perl libdigest-sha1-perl \<br />
libgd-gd2-perl libhtml-template-perl libwww-perl libmime-lite-perl \<br />
libnet-dns-perl liburi-perl libxml-simple-perl libclass-accessor-perl \<br />
libclass-data-inheritable-perl libclass-trigger-perl libcrypt-dh-perl \<br />
libmath-bigint-gmp-perl liburi-fetch-perl libgd-graph-perl \<br />
libgnupg-interface-perl libmail-gnupg-perl perlmagick \<br />
libproc-processtable-perl libsoap-lite-perl librpc-xml-perl \<br />
libstring-crc32-perl libtext-vcard-perl libxml-atom-perl libxml-rss-perl \<br />
libimage-size-perl libunicode-maputf8-perl libgtop2-dev build-essential \<br />
libnet-openid-consumer-perl libnet-openid-server-perl<br />
<br />
This will download about 123MB of files and use around 446MB of disk space.<br />
<br />
You will also want to install some perl libraries with CPAN. Defaults during CPAN's setup should be okay:<br />
<br />
perl -MCPAN -e 'install Bundle::CPAN'<br />
perl -MCPAN -e 'install GTop' # this will guide you through setting up CPAN<br />
perl -MCPAN -e 'install Unicode::CheckUTF8'<br />
perl -MCPAN -e 'install Captcha::reCAPTCHA'<br />
perl -MCPAN -e 'install IP::Country::Fast'<br />
<br />
You will also want to install and configure Postfix so your DW can send out email:<br />
<br />
apt-get install postfix<br />
<br />
If you choose not to configure on the install, you can do so later with:<br />
<br />
dpkg-reconfigure postfix<br />
<br />
== Setting up the DW user account ==<br />
<br />
{{Note|text=If you still find yourself unable to make sudo commands even after <code>usermod</code>, please see [[Making your DW user a sudo account]] for alternatives.}} Create a user account that will be used for the code. This can be your own personal account if you wish, but it is recommended that you setup a new user that is only going to be used for running the code. That way if you have any insecure code running (i.e., a bad page, or a patch you're working on doesn't have security implemented yet) you don't have to worry about someone getting access to your personal files.<br />
<br />
To set up the user account:<br />
<br />
adduser <i>username</i><br />
<br />
Fill out the user's info and put them in the sudo group:<br />
<br />
usermod -a -G sudo <i>username</i><br />
<br />
So, to use <code>dw</code> as a username:<br />
<br />
adduser dw<br />
usermod -a -G sudo dw<br />
<br />
Now, we will get the $LJHOME variable set. Log into your user:<br />
<br />
su - dw<br />
<br />
We will assume that you use the bash shell. If you do not, then this section does not apply. You will have to find the shell specific way of setting environment variables.<br />
<br />
For bash, you should look in the home directory of the user account you just created for a file .profile. You will want to add one more line to this file:<br />
<br />
export LJHOME=/home/dw<br />
<br />
Or whatever your user account's home directory is. Yes, the variable is named LJHOME. We'll live with it for now. ;-)<br />
<br />
Test this. Log out of your user account and log back in, then type:<br />
<br />
echo $LJHOME<br />
<br />
You should see /home/dw or whatever you set it to. If you don't, then you didn't get the export line in the right place. (Hey, I'm not here to teach basic sysadmin stuff. You should know how to set environment variables.)<br />
<br />
== Downloading the Dreamwidth code ==<br />
<br />
You should do this as the user you want to run Dreamwidth as. If you are root, you can switch with:<br />
<br />
su - dw<br />
<br />
We have put together a bootstrap script that will download all of the code. You can obtain this file with your favorite tool (wget, curl, etc):<br />
<br />
wget http://hg.dwscoalition.org/dw-free/raw-file/tip/bin/bootstrap.pl<br />
<br />
The next step is fairly automatic. Assuming that your $LJHOME environment variable is good to go, you should be able to just do this:<br />
<br />
perl bootstrap.pl<br />
<br />
The script will start doing some work. It should start out by saying 'seems we need to start at the beginning', which is what you expect. Then you will sit around for half an hour while it checks out various packages and repositories from various locations.<br />
<br />
When it's done, it will say so. It will also say to delete the bootstrap script: <br />
<br />
rm bootstrap.pl<br />
<br />
Do a quick ls in $LJHOME to see if you have a bunch of new directories like cvs, cgi-bin, htdocs, etc. If you do, huzzah! You now have the code checked out.<br />
<br />
If you don't, figure out what step didn't work, and try again. All else fails, hit the mailing list or find someone on IRC.<br />
<br />
=== dw-nonfree ===<br />
<br />
{{Warn|text=Currently, doing this step is necessary. We are working on correcting this.}}<br />
<br />
If you are doing development on Dreamwidth custom files (what few there are), then you will need to do another step. This is fairly manual, the bootstrap script does not handle this process for you. But assuming that you did the above steps, you can get dw-nonfree code like this:<br />
<br />
cd $LJHOME/cvs<br />
hg clone http://hg.dwscoalition.org/dw-nonfree dw-nonfree<br />
cp dw-nonfree/cvs/multicvs-local.conf .<br />
<br />
You may want to look at [[Keeping your site configs from wiping during updates]] if you want to keep your config files from getting wiped during subsequent updates if you're using <tt>dw-nonfree</tt>.<br />
<br />
=== Updating to the tip ===<br />
<br />
As of right now, you have the code that existed up until the end of the initial branch with no name, ending in changeset [http://hg.dwscoalition.org/dw-free/rev/1defc551af6c 1defc551af6c] from October 13th 2008. However, with the next commit on January 14th 2009, named branches were introduced, and the dw-free repository now uses all named branches. (currently there is only one named branch that is up to date, 'production')<br />
<br />
That means that the code you currently have is out of date, and you will need to explicitly update to the tip:<br />
<br />
cd $LJHOME/cvs/dw-free<br />
hg update -C tip<br />
cd $LJHOME<br />
bin/cvsreport.pl -sync -cvsonly<br />
bin/cvsreport.pl -sync -cvsonly<br />
<br />
You need to do the last line twice, since the multicvs.conf file has changed since then. Any future updates should now work as described on the [[Dev Maintenance]] page.<br />
<br />
== Database setup ==<br />
<br />
You should have a local MySQL installation and know the root login to the database. To sign into MySQL as root:<br />
<br />
mysql -u root -p <br />
<br />
These MySQL commands wil create your development database:<br />
<br />
create database dw;<br />
grant all on dw.* to 'dw'@'localhost' identified by 'somePassword';<br />
quit;<br />
<br />
You might want to pick a more appropriate database username/database name/password.<br />
<br />
== Editing the config files ==<br />
<br />
Next you need to configure the site configuration scripts. This is probably the most tricky part of the whole process, since there are so many things you can tweak. However, you can get by with just tweaking etc/config-local.pl for now:<br />
<br />
cd $LJHOME<br />
cp doc/config-local.pl.txt etc/config-local.pl<br />
cp doc/config-private.pl.txt etc/config-private.pl<br />
vim etc/config-local.pl<br />
<br />
Or use your editor of choice, of course. Do a search for the phrase 'CHANGE THIS' which is in three places. You will want to change at least your <var>$DOMAIN</var> and the <var>%DBINFO</var> structure.<br />
<br />
The base configuration file is under source control, and is already in etc/config.pl. You should not need to change anything very much in this, but you might have to change some stuff. If you find you do have to touch this, please see [http://bugs.dwscoalition.org/show_bug.cgi?id=165] first.<br />
<br />
Note that the <var>$IS_DEV_SERVER</var> flag is set to 1 in the template given. Be sure to set this to 0 for a production site, as there are big security issues involved with leaving the flag set to 1.<br />
<br />
Apart from this, the configuration should be fairly self-explanatory, except for one thing - do not place your database password in the <tt>config-local.pl</tt> file! Instead, place it in the <tt>config-private.pl</tt> file:<br />
<br />
cd $LJHOME<br />
cp doc/config-private.pl.txt etc/config-private.pl<br />
<br />
(if you didn't already do that above)<br />
<br />
chmod go-rwx etc/config-private.pl<br />
vim etc/config-private.pl<br />
<br />
In this file, uncomment the lines in the <var>%DBINFO</var> block, and place your database password in quotes on the "pass => ," line, before the comma. For example:<br />
<br />
%DBINFO = (<br />
master => {<br />
pass => 'mypassword',<br />
},<br />
);<br />
<br />
As mentioned, there are also settings to check out in <tt>etc/config.pl</tt>:<br />
<br />
vim etc/config.pl<br />
<br />
== Make sure things are working with checkconfig.pl ==<br />
<br />
Now, you need to see if everything is working. If you've setup the files as indicated above, run this command:<br />
<br />
cd $LJHOME<br />
bin/checkconfig.pl --no=ljconfig<br />
<br />
If you installed everything given at the top of this page, you should find you have no missing modules. Congratulations! If you don't have all the modules, this is where you need some systems specific knowledge for your system. You will need to install whatever modules are missing. If you get well and truly stuck, find someone on IRC or the mailing list.<br />
<br />
== Populate database with initial data ==<br />
<br />
There are a few commands you can now run to install the database. Just run these and watch for errors.<br />
<br />
<b>Note:</b> If make_system.pl says it can't give the system user admin privileges, something has gone wrong with your database population, even if there were no errors.<br />
<br />
$LJHOME/bin/upgrading/update-db.pl -r --innodb<br />
$LJHOME/bin/upgrading/update-db.pl -r --cluster=all --innodb<br />
$LJHOME/bin/upgrading/update-db.pl -p<br />
$LJHOME/bin/upgrading/make_system.pl<br />
<br />
(That step will ask you for a password for the system account. You can change it later by logging in as system, so just give it something for now.)<br />
<br />
$LJHOME/bin/upgrading/texttool.pl load<br />
$LJHOME/bin/upgrading/copy-emailpass-out-of-user<br />
<br />
== Configure Apache ==<br />
<br />
This step will need to be done as the root user. Below is the Apache 2 configuration running on the Dreamwidth staging site. Put this in a file named "stage" in /etc/apache2/conf.d:<br />
<br />
User dw<br />
Group dw<br />
UseCanonicalName off<br />
<br />
StartServers 1<br />
MaxSpareServers 2<br />
MinSpareServers 1<br />
<br />
DocumentRoot /home/dw/htdocs<br />
<br />
PerlSetEnv LJHOME /home/dw<br />
PerlPassEnv LJHOME<br />
<br />
PerlRequire /home/dw/cgi-bin/modperl.pl<br />
<br />
Then disable the default site:<br />
<br />
a2dissite default<br />
<br />
You might also have to enable the Perl Apache Request module:<br />
<br />
a2enmod apreq<br />
<br />
If you don't want this warning:<br />
<br />
[Thu Jan 15 01:46:54 2009] [warn] NameVirtualHost *:80 has no VirtualHosts<br />
... waiting [Thu Jan 15 01:46:55 2009] [warn] NameVirtualHost *:80 has no VirtualHosts<br />
...done.<br />
<br />
Then use <code>vim /etc/apache2/ports.conf</code> and put a # in front of the NameVirtualHost line:<br />
<br />
# NameVirtualHost *:80<br />
<br />
Restart the server:<br />
<br />
/etc/init.d/apache2 restart<br />
<br />
== Now what? ==<br />
<br />
=== Further setup ===<br />
<br />
There are lots of other articles on setting up and customizing your DW install in the [[:Category: Dreamwidth Installation|DW Installation]] category, including:<br />
<br />
* [[TheSchwartz_Setup]] - TheSchwartz is needed for a handful of features - notably comment posting<br />
* [[Subdomain setup]]<br />
* [[Statistics setup]]<br />
* [[Generating documentation]]<br />
* [[Cssproxy]]<br />
* [[Allow users to register]]<br />
<br />
There is a list of wanted how-tos at [[Installation Wanted How-To]], in case you need to add something to the list.<br />
<br />
=== Starting development ===<br />
<br />
The list of things that need doing are in [http://bugs.dwscoalition.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfie Bugzilla]. You can keep your code update with the instructions in [[Dev Maintenance]]. Instructions on submitting patches are in [[Dev Patches]].<br />
<br />
[[Category: Dreamwidth Installation]]</div>124.6.182.55//wiki.dreamwidth.net/wiki/index.php/Dreamwidth_Scratch_InstallationDreamwidth Scratch Installation2009-02-03T09:39:47Z<p>124.6.182.55: explain about config.pl</p>
<hr />
<div>These are the instructions to install a Dreamwidth system from scratch, assuming you are running Ubuntu. See [[Setting up Dreamwidth on Linode]] for instructions on setting up a system to the point where you can log in and start this. After you set up, you can keep updated with the instructions on [[Dev Maintenance]].<br />
<br />
If you have difficulties or problems or suggestions for installation procedures, please report them to [http://www.dwscoalition.org/show_bug.cgi?id=61 Bug 61]. Also look at [[Production Setup: Webserver]]. <br />
<br />
== Bringing the system up to date ==<br />
<br />
Before you start installing anything else, you might want to make sure your system is up to date. You should log in as root and update the packages on your system:<br />
<br />
apt-get update<br />
apt-get upgrade<br />
<br />
If you want man pages on your system: <br />
<br />
apt-get install man<br />
<br />
== Installing necessary packages ==<br />
<br />
This will install necessary packages you'll need to run Dreamwidth. You'll want to be root when running these commands.<br />
<br />
apt-get install mercurial subversion apache2-mpm-prefork \<br />
libapache2-mod-perl2 libapache2-mod-apreq2 libapache2-request-perl \<br />
mysql-server wget unzip links vim libclass-autouse-perl \<br />
libcompress-zlib-perl libdatetime-perl libdigest-sha1-perl \<br />
libgd-gd2-perl libhtml-template-perl libwww-perl libmime-lite-perl \<br />
libnet-dns-perl liburi-perl libxml-simple-perl libclass-accessor-perl \<br />
libclass-data-inheritable-perl libclass-trigger-perl libcrypt-dh-perl \<br />
libmath-bigint-gmp-perl liburi-fetch-perl libgd-graph-perl \<br />
libgnupg-interface-perl libmail-gnupg-perl perlmagick \<br />
libproc-processtable-perl libsoap-lite-perl librpc-xml-perl \<br />
libstring-crc32-perl libtext-vcard-perl libxml-atom-perl libxml-rss-perl \<br />
libimage-size-perl libunicode-maputf8-perl libgtop2-dev build-essential<br />
<br />
This will download about 123MB of files and use around 446MB of disk space.<br />
<br />
You will also want to install some perl libraries with CPAN. Defaults during CPAN's setup should be okay:<br />
<br />
perl -MCPAN -e 'install GTop' # this will guide you through setting up CPAN<br />
perl -MCPAN -e 'install Unicode::CheckUTF8'<br />
perl -MCPAN -e 'install Captcha::reCAPTCHA'<br />
perl -MCPAN -e 'install IP::Country::Fast'<br />
<br />
You will also want to install and configure Postfix so your DW can send out email:<br />
<br />
apt-get install postfix<br />
<br />
If you choose not to configure on the install, you can do so later with:<br />
<br />
dpkg-reconfigure postfix<br />
<br />
== Setting up the DW user account ==<br />
<br />
{{Note|text=If you still find yourself unable to make sudo commands even after <code>usermod</code>, please see [[Making your DW user a sudo account]] for alternatives.}} Create a user account that will be used for the code. This can be your own personal account if you wish, but it is recommended that you setup a new user that is only going to be used for running the code. That way if you have any insecure code running (i.e., a bad page, or a patch you're working on doesn't have security implemented yet) you don't have to worry about someone getting access to your personal files.<br />
<br />
To set up the user account:<br />
<br />
adduser <i>username</i><br />
<br />
Fill out the user's info and put them in the sudo group:<br />
<br />
usermod -a -G sudo <i>username</i><br />
<br />
So, to use <code>dw</code> as a username:<br />
<br />
adduser dw<br />
usermod -a -G sudo dw<br />
<br />
Now, we will get the $LJHOME variable set. Log into your user:<br />
<br />
su - dw<br />
<br />
We will assume that you use the bash shell. If you do not, then this section does not apply. You will have to find the shell specific way of setting environment variables.<br />
<br />
For bash, you should look in the home directory of the user account you just created for a file .profile. You will want to add one more line to this file:<br />
<br />
export LJHOME=/home/dw<br />
<br />
Or whatever your user account's home directory is. Yes, the variable is named LJHOME. We'll live with it for now. ;-)<br />
<br />
Test this. Log out of your user account and log back in, then type:<br />
<br />
echo $LJHOME<br />
<br />
You should see /home/dw or whatever you set it to. If you don't, then you didn't get the export line in the right place. (Hey, I'm not here to teach basic sysadmin stuff. You should know how to set environment variables.)<br />
<br />
== Downloading the Dreamwidth code ==<br />
<br />
You should do this as the user you want to run Dreamwidth as. If you are root, you can switch with:<br />
<br />
su - dw<br />
<br />
We have put together a bootstrap script that will download all of the code. You can obtain this file with your favorite tool (wget, curl, etc):<br />
<br />
wget http://hg.dwscoalition.org/dw-free/raw-file/tip/bin/bootstrap.pl<br />
<br />
The next step is fairly automatic. Assuming that your $LJHOME environment variable is good to go, you should be able to just do this:<br />
<br />
perl bootstrap.pl<br />
<br />
The script will start doing some work. It should start out by saying 'seems we need to start at the beginning', which is what you expect. Then you will sit around for half an hour while it checks out various packages and repositories from various locations.<br />
<br />
When it's done, it will say so. It will also say to delete the bootstrap script: <br />
<br />
rm bootstrap.pl<br />
<br />
Do a quick ls in $LJHOME to see if you have a bunch of new directories like cvs, bml, cgi-bin, htdocs, etc. If you do, huzzah! You now have the code checked out.<br />
<br />
If you don't, figure out what step didn't work, and try again. All else fails, hit the mailing list or find someone on IRC.<br />
<br />
=== dw-nonfree ===<br />
<br />
{{Warn|text=Currently, this doing this step is necessary. We are working on correcting this.}}<br />
<br />
If you are doing development on Dreamwidth custom files (what few there are), then you will need to do another step. This is fairly manual, the bootstrap script does not handle this process for you. But assuming that you did the above steps, you can get dw-nonfree code like this:<br />
<br />
cd $LJHOME/cvs<br />
hg clone http://hg.dwscoalition.org/dw-nonfree dw-nonfree<br />
cp dw-nonfree/cvs/multicvs-local.conf .<br />
cd $LJHOME<br />
bin/cvsreport.pl -s<br />
<br />
You should see a number of files get copied around.<br />
<br />
=== Updating to production code ===<br />
<br />
With the way things currently are, you're probably wanting to work on the production code:<br />
<br />
cd $LJHOME/cvs/dw-free<br />
hg update -C tip<br />
cd $LJHOME<br />
bin/cvsreport.pl -sync -cvsonly<br />
<br />
== Database setup ==<br />
<br />
You should have a local MySQL installation and know the root login to the database. To sign into MySQL as root:<br />
<br />
mysql -u root -p <br />
<br />
These MySQL commands wil create your development database:<br />
<br />
create database dw;<br />
grant all on dw.* to 'dw'@'localhost' identified by 'somePassword';<br />
quit;<br />
<br />
You might want to pick a more appropriate database username/database name/password.<br />
<br />
== Editing the config files ==<br />
<br />
Next you need to configure the site configuration scripts. This is probably the most tricky part of the whole process, since there are so many things you can tweak. However, you can get by with just tweaking etc/config-local.pl for now:<br />
<br />
cd $LJHOME<br />
cp doc/ljconfig.pl.txt etc/ljconfig.pl<br />
cp doc/config-local.pl.txt etc/config-local.pl<br />
vim etc/config-local.pl<br />
<br />
Or use your editor of choice, of course. Do a search for the phrase 'CHANGE THIS' which is in four places. You will want to change at least your <var>$DOMAIN</var> and the <var>%DBINFO</var> structure.<br />
<br />
The base configuration file is under source control, and is already in etc/config.pl. You should not need to change anything in this. If you find you have to touch this, please see [http://bugs.dwscoalition.org/show_bug.cgi?id=165] first.<br />
<br />
Note that the <var>$IS_DEV_SERVER</var> flag is set to 1 in the template given. Be sure to set this to 0 for a production site, as there are big security issues involved with leaving the flag set to 1.<br />
<br />
Apart from this, the configuration should be fairly self-explanatory, except for one thing - do not place your database password in the config-local.pl file! Instead, place it in the config-private.pl file:<br />
<br />
cd $LJHOME<br />
cp doc/config-private.pl.txt etc/config-private.pl<br />
vim etc/config-private.pl<br />
<br />
In this file, uncomment the lines in the <var>%DBINFO</var> block, and place your database password in quotes on the "pass => ," line, before the comma. For example:<br />
<br />
%DBINFO = (<br />
master => {<br />
pass => 'mypassword',<br />
},<br />
);<br />
<br />
== Make sure things are working with checkconfig.pl ==<br />
<br />
Now, you need to see if everything is working. If you've setup the files as indicated above, run this command:<br />
<br />
cd $LJHOME<br />
bin/checkconfig.pl --no=ljconfig<br />
<br />
It should take a few minutes to run and then tell you that you are missing modules. This is where you need some systems specific knowledge for your system. You will need to install whatever modules it's missing; hopefully with these instructions, none will be. If you get well and truly stuck, find someone on IRC or the mailing list.<br />
<br />
== Populate database with initial data ==<br />
<br />
There are a few commands you can now run to install the database. Just run these and watch for errors.<br />
<br />
<b>Note:</b> If make_system.pl says it can't give the system user admin privileges, something has gone wrong with your database population, even if there were no errors.<br />
<br />
$LJHOME/bin/upgrading/update-db.pl -r --innodb<br />
$LJHOME/bin/upgrading/update-db.pl -r --cluster=all --innodb<br />
$LJHOME/bin/upgrading/update-db.pl -p<br />
$LJHOME/bin/upgrading/make_system.pl<br />
<br />
(That step will ask you for a password for the system account. You can change it later by logging in as system, so just give it something for now.)<br />
<br />
$LJHOME/bin/upgrading/texttool.pl load<br />
$LJHOME/bin/upgrading/copy-emailpass-out-of-user<br />
<br />
== Configure Apache ==<br />
<br />
This step will need to be done as the root user. Below is the Apache 2 configuration running on the Dreamwidth staging site. Put this in a file named "stage" in /etc/apache2/conf.d:<br />
<br />
User dw<br />
Group dw<br />
UseCanonicalName off<br />
<br />
StartServers 1<br />
MaxSpareServers 2<br />
MinSpareServers 1<br />
<br />
DocumentRoot /home/dw/htdocs<br />
<br />
PerlSetEnv LJHOME /home/dw<br />
PerlPassEnv LJHOME<br />
<br />
PerlRequire /home/dw/cgi-bin/modperl.pl<br />
<br />
Then disable the default site:<br />
<br />
a2dissite default<br />
<br />
You might also have to enable the Perl Apache Request module:<br />
<br />
a2enmod apreq<br />
<br />
If you don't want this warning:<br />
<br />
[Thu Jan 15 01:46:54 2009] [warn] NameVirtualHost *:80 has no VirtualHosts<br />
... waiting [Thu Jan 15 01:46:55 2009] [warn] NameVirtualHost *:80 has no VirtualHosts<br />
...done.<br />
<br />
Then use <code>vim /etc/apache2/ports.conf</code> and put a # in front of the NameVirtualHost line:<br />
<br />
# NameVirtualHost *:80<br />
<br />
Restart the server:<br />
<br />
/etc/init.d/apache2 restart<br />
<br />
== Now what? ==<br />
<br />
=== Further setup ===<br />
<br />
There are lots of other articles on setting up and customizing your DW install in the [[:Category: Dreamwidth Installation|DW Installation]] category, including:<br />
<br />
* [[Subdomain setup]]<br />
* [[Statistics setup]]<br />
* [[Generating documentation]]<br />
* [[Cssproxy]]<br />
* [[Allow users to register]]<br />
<br />
There is a list of wanted how-tos at [[Installation Wanted How-To]], in case you need to add something to the list.<br />
<br />
=== Starting development ===<br />
<br />
The list of things that need doing are in [http://bugs.dwscoalition.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfie Bugzilla]. You can keep your code update with the instructions in [[Dev Maintenance]]. Instructions on submitting patches are in [[Dev Patches]].<br />
<br />
[[Category: Dreamwidth Installation]]</div>124.6.182.55//wiki.dreamwidth.net/wiki/index.php/Category:Removed_Database_TablesCategory:Removed Database Tables2009-01-29T08:24:42Z<p>124.6.182.55: New page: Tables that used to exist, but have been ripped out because the corresponding functionality has also been ripped out. Some of these tables may be replaced by similar ones, if the function...</p>
<hr />
<div>Tables that used to exist, but have been ripped out because the corresponding functionality has also been ripped out.<br />
<br />
Some of these tables may be replaced by similar ones, if the functionality is reimplemented.</div>124.6.182.55