![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png){kind=small}
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
Entry tags:
Running DW code
At OSCON, Mark and I were discussing adoption of the DW code by other sites, and a little bit of how we could work to that point. Mark's interested in cross-site federation and open social-media protocols, but I'm thinking a bit more about making it easier for people to install and run the DW code.
Right now, the code we 'ship', in dw-free, is pretty fully functional. Somebody could grab that code, install it, and have a working and running site without a ton of custom work. It's not easy, though, and there are a lot of "gotcha"s in place during the install process.
Better install documentation is a must, and that's something we can work on, but I'm throwing the option open to the field: what else can we do to improve the DW install process, with the end goal of having someone be able to get the code and get it running with as little hassle as possible? We have a bunch of bugs open to do that, but what (besides documentation and an installer) do you think people would be looking for?
Right now, the code we 'ship', in dw-free, is pretty fully functional. Somebody could grab that code, install it, and have a working and running site without a ton of custom work. It's not easy, though, and there are a lot of "gotcha"s in place during the install process.
Better install documentation is a must, and that's something we can work on, but I'm throwing the option open to the field: what else can we do to improve the DW install process, with the end goal of having someone be able to get the code and get it running with as little hassle as possible? We have a bunch of bugs open to do that, but what (besides documentation and an installer) do you think people would be looking for?
no subject
They would handle the installing of the pre-requisites based on what the user wanted to install (the pre-requisites would be mostly Perl modules installed using apt-get), setting up a new user, installing various servers, etc.
The reason I say "scripts" instead of "script" is because if you're going to want to do anything production-wise, you're probably going to at least want the web server on a different machine from the database server, so it's probably best to have separate scripts for each of the different parts that can be potentially on different machines.
Of course, the Dreamhack machine already has a fully automated script, but it's not quite what we'd need here because it relies on the pre-reqs already being installed, and assumes a few things about the environment. We might be able to use it as a base, though.
On the other hand, we may want to opt for something based on Puppet, which is what DW.org itself uses to configure machines. I don't know much about that, so someone else would need to speak about that.