The current docs show nicely how to set up a dev environment, however it is not clear how to set up the thing in a non-dev way (I guess that is the "deployment" docs, right?)

Here are some things to consider when writing this. I got it up and running in Ubuntu Maverick in a non-dev way. I had to install some things with "pip" and used the distribution packages whenever possible.

So stuff that needs documentation:

paster running on port 80 is not possible without having the whole thing running as root. Which will then require to also have celeryd running as root, as it needs to delete files that paster put there. I solved this in a very hackish way with "Capabilities" on Linux. Downside is, I had to grant /usr/bin/python the permission to access ports <1024. I achieved this with

sudo setcap 'cap_net_bind_service=+ep' /usr/bin/python2.6

(not saying we should recommend that to anyone. I guess we will propose to run this as a local user on a nonpriviledged port and proxy it through nginx or so.

Anyway, it runs beautiful as www-data on my server now.

We have three separate audiences that we need to write documentation for:

• contributors (developers, hackers, themers, translators, ...)
• site admin (someone who installs MediaGoblin on his/her server to use)
• users (someone who sets up a MediaGoblin account, uploads photos, ...)

Currently, we have documentation in a few different places. We want to migrate to the following:

1. contributor and project infrastructure documentation goes in the wiki.
2. site admin documentation goes in docs/ where it's built in HTML and Texinfo formats for release tarballs; site admin documentation is also available on http://docs.mediagoblin.org/
3. user documentation will be part of the MediaGoblin code probably as Jinja2 templates available through /help/ url or something like that

We want to do this for 0.0.5, but the most important stuff initially is straightening out the contributor docs, then straightening out the site admin docs, then writing user docs.