We probably should document the things needed to do to run a full production site a lot better. It's not that bad to get a dev environment going, but once you step past that to configuring all of the other pieces you need (perlbal, mogilefs, memcache, theschwartz workers, gearman, whatever else) the documentation suddenly becomes a lot more sparse.
Some different production targets would also be good. Want to run a local dreamhack? Do these things. Want to use DW as a personal blogging platform? It's overkill, but here's how you'd do it. Private site for running an RPG? Blogging platform just for you and your personal friends? Open site for a small community? Want to replace Facebook? Each of these might require slightly different configuration options. And even if you assume that each site would be unique, it would still be good to have a few different sets of starting points before enabling/disabling features a la carte.
We could do a better job of separating out the user-facing custom configurations. It would be helpful if there were a single place where you could customize the site name, welcome text, etc., instead of having some of it in etc/config.local, some in htdocs/index.bml, etc.
...Hmm, you know, if we separated out the local customizaitons, then there'd really be no reason that we couldn't distribute DW as a pre-configured package rather than getting it from the source repository and configuring it by hand. It'd be a lot of work for somebody, but if DW were packaged as a PPA it would make doing production (as opposed to development) installs a whole lot easier.
no subject
Some different production targets would also be good. Want to run a local dreamhack? Do these things. Want to use DW as a personal blogging platform? It's overkill, but here's how you'd do it. Private site for running an RPG? Blogging platform just for you and your personal friends? Open site for a small community? Want to replace Facebook? Each of these might require slightly different configuration options. And even if you assume that each site would be unique, it would still be good to have a few different sets of starting points before enabling/disabling features a la carte.
We could do a better job of separating out the user-facing custom configurations. It would be helpful if there were a single place where you could customize the site name, welcome text, etc., instead of having some of it in etc/config.local, some in htdocs/index.bml, etc.
...Hmm, you know, if we separated out the local customizaitons, then there'd really be no reason that we couldn't distribute DW as a pre-configured package rather than getting it from the source repository and configuring it by hand. It'd be a lot of work for somebody, but if DW were packaged as a PPA it would make doing production (as opposed to development) installs a whole lot easier.