This documents the development folder checked out by
Directories you will use a lot
This directory contains backend utilities for maintaining and upgrading the site.
This directory contains the code that runs the site. This is the base of the library path--that is
use Net::OpenID::Consumer; refers to the code in
cgi-bin/Net/OpenID/Consumer.pm. It contains all the custom Perl libraries functions that the code references, including the
This directory contains most of the user-facing pages, with the directory structure used on the main website. That is to say, anything that appears at
http://www.dreamwidth.org/filename.bml will be here, as
htdocs/filename.bml; anything at
http://www.dreamwidth.org/directory/filename.bml will be here as
htdocs/directory/filename.bml, etc. To see your changes on your development site, you need to make the changes to the appropriate file in this directory.
This contains pages that are transmitted over SSL instead of being unencrypted. Regular files live in
This contains Template Toolkit files, as part of our conversion from BML to Template Toolkit. The controllers for the templates are in cgi-bin/DW/Controller/.
The cvs folder contains a local checkout of the Mercurial repositories. To generate a patch for your changes that can be applied, you need to make the changes to the appropriate changes in this directory, after you have verified that the changes work, testing them by putting them in
ssldocs and viewing them (and testing them) on your development site. Once you've done that, you can use the automatic tools to sync your "live" directories and your cvs directory. More information can be found at [].
The two Mercurial source branches you'll be using most often are
dw-free dw-free and
dw-nonfree dw-nonfree. (When viewing the Mercurial page for each repo, the 'Manifest' link in the top menu bar will allow you to browse the source tree.)
Directories you will not need to change often
These are directories you won't need to change often, unless you're working on some specific task related to them.
Most notable thing in here is the docbook code for the server and LJ programming guides.
Empty in a clean checkup. Your site's
ljconfig.pl will go here, to make sure the original
ljconfig.pl can be updated without ill effects on a running installation.
Looks to be an empty folder to store logs during running the code.
Confusingly enough, contains source for some of the packages the code uses. Perhaps this is the folder that comes with the distribution and
cvs is checked out from the other repositories? Does not contain all of the ones in
Looks like this contains the tests that use the testing framework in main/test. See Dev Testing for how to use them.
Empty in a clean install. Probably used for temporary file storage.
Very sparse directory; really not much here.
A clean install of this only includes devdata/evillaugh.wav. Nobody remembers what this is for.