Problem installing Dreamwidth.....

[notdefined]

I'm following the dialogue to install dreamwidth under Ubuntu 9.04. All is going well until I execute the bin/checkconfig.pl. I get this error:

dw@web01:~$ bin/checkconfig.pl --no=ljconfig
[Checking for Perl Modules....]
[Checking LJ Environment...]

Problem:

* Failed to load ljlib.pl: Can't locate DW/Hooks.pm in @INC (@INC contains: /home/dw/cgi-bin /etc/perl /usr/local/lib/perl/5.10.0 /usr/local/share/perl/5.10.0 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at /home/dw/cgi-bin/ljlib-local.pl line 6.

BEGIN failed--compilation aborted at /home/dw/cgi-bin/ljlib-local.pl line 6. Compilation failed in require at /home/dw/cgi-bin/ljlib.pl line 119. Compilation failed in require at bin/checkconfig.pl line 233.

Any clue what I'm doing wrong??

Comments

[denise]

There aren't really any restrictions -- we've tried to make it totally possible to run a complete production site on the code, up to and including a lot of functions/features that LJ doesn't put in their equivalent of 'dw-free' -- but one caveat you should be aware of is that we're, uh, still very much in beta!

Obviously, the code works well enough to run a production system on -- we're doing it, after all -- but we're doing very rapid development and iteration as we identify glitches and flaws, and our documentation is lagging behind our actual code (a perpetual problem, she says, wearily, and in fact as you notice things that need documenting better, we'd love it if you note them down on the wiki). During beta, we're also working without a lot of the QA/staged deployment systems we want to have in place by full site 'launch', so there's a pretty good risk you're going to get something mildly buggy if you update from tip. (she says, having been the person who broke the site four times in the past month...)

None of this is an argument against running a production site on DW code, and indeed we'd love to see you doing it -- the more people running the code, with as many use cases as possible, the more bugs we can shake out and fix and the more suggestions for improvements we can find -- but it's a good idea to know what you're getting into! It's probably a good idea to create a local repository of the code and work from that, rather than just updating directly from tip, so you can roll back to a "known good" version in case something breaks. It's also a good idea to be watching changelog -- it can be high-traffic (which excites me, let me tell you) but it gives a good sense of what we're up to, development-wise.

And if your coding fingers creep out of your pockets, we'd love to see you contribute some code :)

Welcome to the DW community! I'm really excited to see you here and using our code to build something -- let us all know when you get the site running so we can drop by and say hi :)

[foxfirefey]

If changelog is too spammy, there is always changelog_digest! That's what I watch instead of the main comm itself.