Dreamwidth Scratch Installation

These are the instructions to install a Dreamwidth system from scratch, assuming you are running Fedora 11 or 12. After you set up, you can keep updated with the instructions on Dev Maintenance.

Bringing the perl-GnuPG-Interface system up to date

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:

yum update

Installing necessary packages

This will install necessary packages you'll need to run Dreamwidth (and some optional ones). You'll want to be root when running these commands.

yum install perl mysql httpd perl-CPAN perl-IO-stringy perl-MIME-tools perl-Image-Size perl-SOAP-Lite perl-catalyst-runtime* perl-CPAN perl-Test-WWW-Mechanize-Catalyst perl-Test-use-ok perl-String-CRC32 perl-Class-Trigger perl-libapreq2 perl-Crypt-DH perl-Mail-GnuPG perl-Math-BigInt-GMP perl-Proc-ProcessTable perl-RPC-XML perl-Text-vCard perl-URI-Fetch perl-XML-Atom perl-Geography-Countries perl-Captcha-reCAPTCHA perl-Class-Autouse perl-GD perl-Unicode-CheckUTF8 perl-Unicode-MapUTF8 perl-XML-Simple perl-GTop perl-Template* perl-libapreq2 mod_security

Installing third party modules

rpm -Uvh http://perlpackage.googlecode.com/files/perl-IP-Country-2.27-1.fc12.noarch.rpm
rpm -Uvh http://perlpackage.googlecode.com/files/perl-Net-OpenID-Server-1.02-1.fc12.noarch.rpm
rpm -Uvh http://perlpackage.googlecode.com/files/perl-Net-OpenID-Consumer-1.03-1.fc12.noarch.rpm

For 32bit architecture

rpm -Uvh http://perlpackage.googlecode.com/files/perl-Unicode-CheckUTF8-1.01-1.fc12.i686.rpm

For 64 bit architecture

rpm -Uvh http://perlpackage.googlecode.com/files/perl-Unicode-CheckUTF8-1.01-1.fc12.x86_64.rpm

You will also want to install and configure Postfix so your DW can send out email:

yum install postfix

Setting up the DW user account

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

To set up the user account

adduser "username"
passwd "username"
enter some password for this user

So, to use dw as a username:

adduser dw
passwd dw
enter some password for dw

Now, we will get the $LJHOME variable set. Log into your user:

su - dw

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.

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:

export LJHOME=/home/dw

Or whatever your user account's home directory is. Yes, the variable is named LJHOME. We'll live with it for now. ;-)

Test this. Log out of your user account and log back in, then type:

echo $LJHOME

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.)

Downloading the Dreamwidth code

You should do this as the user you want to run Dreamwidth as. If you are root, you can switch with:

su - dw

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):

wget http://hg.dwscoalition.org/dw-free/raw-file/tip/bin/bootstrap.pl

The next step is fairly automatic. Assuming that your $LJHOME environment variable is good to go, you should be able to just do this:

perl bootstrap.pl

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.

When it's done, it will say so. It will also say to delete the bootstrap script:

rm bootstrap.pl

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.

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.

dw-nonfree

Warning: This should not be used on installations that are not Dreamwidth development installations.

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:

cd $LJHOME/cvs
hg clone http://hg.dwscoalition.org/dw-nonfree dw-nonfree
cp dw-nonfree/cvs/multicvs-local.conf .

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 dw-nonfree.

Updating to the tip

As of right now, you have the code that existed up until the end of the initial branch with no name, ending in changeset 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')

Right now, bootstrap.pl gives you the SVN repository, rather than an HG which is currently used and as such cvsreport.pl fails because it expected HG.

Remove it and then do checkout:

cd $LJHOME/cvs/dw-free
hg update -C tip
cd $LJHOME
bin/cvsreport.pl -sync -cvsonly
rm -rf cvs/perlbal/
rm -rf cvs/js/
bin/cvsreport.pl --checkout
bin/cvsreport.pl -sync -cvsonly

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. You will also want to delete files that no longer exist in the repository:

cd $LJHOME; for i in `bin/cvsreport.pl -n -1`; do echo "Removing $i" && rm $i; done

Database setup

You should have a local MySQL installation and know the root login to the database. To sign into MySQL as root:

mysql -u root -p

These MySQL commands wil create your development database:

create database dw;
grant all privileges on dw.* to 'dw'@'localhost' identified by 'somePassword';
quit;

Editing the config files

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 and etc/config-private.pl for now:

cd $LJHOME
cp doc/config-local.pl.txt etc/config-local.pl
vim etc/config-local.pl

Or use your editor of choice, of course. Do a search for the phrase 'CHANGE THIS' which occurs once, before the block of human readable text you should use to describe your development installation.

Note that the $IS_DEV_SERVER 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.

Next, you need to change your local variables in the config-private.pl file. This is where your passwords are configured, as well as many of the variables which define your domain. Do a search for the phrase 'CHANGETHIS'(note the slightly different spacing). You will want to change at least your $DOMAIN and the %DBINFO structure.

cd $LJHOME
cp doc/config-private.pl.txt etc/config-private.pl
chmod go-rwx etc/config-private.pl
vim etc/config-private.pl

In this file, uncomment the lines in the %DBINFO blocks (if they are commented out), and place your database password in quotes on the "pass => ," line, before the comma. For example:

%DBINFO = (
       master => {
           pass => 'mypassword',
       },
   );

Note that there are two DBINFO blocks; get them both.

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 [1] first. Then you can edit it:

vim etc/config.pl

Make sure things are working with checkconfig.pl

Now, you need to see if everything is working.

If you've setup the files as indicated above, run this command:

cd $LJHOME
bin/checkconfig.pl --no=ljconfig

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.

Populate database with initial data

There are a few commands you can now run to install the database. Just run these and watch for errors.

Note: 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.

$LJHOME/bin/upgrading/update-db.pl -r --innodb
$LJHOME/bin/upgrading/update-db.pl -r --cluster=all --innodb
$LJHOME/bin/upgrading/update-db.pl -p

(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.)

$LJHOME/bin/upgrading/make_system.pl
$LJHOME/bin/upgrading/texttool.pl load

Configure Apache

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.conf" in vi /etc/httpd/conf.d :

User dw
Group dw
UseCanonicalName off

StartServers 1
MaxSpareServers 2
MinSpareServers 1

DocumentRoot /home/dw/htdocs

PerlSetEnv LJHOME /home/dw
PerlPassEnv LJHOME

PerlRequire /home/dw/cgi-bin/modperl.pl

Restart the server:

service httpd restart

Now what?

Have a look at your new DW instance

Congratulations! You now have a working (though minimal) Dreamwidth install. If you point your web browser at your server, you should see a bare-looking welcome page.

Further setup

There are lots of other articles on setting up and customizing your DW install in the DW Installation category, including:

TheSchwartz Setup - TheSchwartz is needed for a handful of features - notably comment posting
Subdomain setup
Statistics setup
Generating documentation
Allow users to register

Dreamwidth Install on fedora

Dreamwidth Scratch Installation

Now what?

Have a look at your new DW instance

Further setup

no subject