For which reason I think that it is a big shame that there is no setup script, as I'd like to install it "properly" (system-wide).
Since writing a simple setup.py isn't all that much work, I decided to get started doing that in the hope that it will get accepted
My other proposal is to seperate the project and app parts of djangobb:
I see two major use cases for DjangoBB: As a standalone forum and as a pluggable app that can be embedded in django websites. It would be great if installing djangobb as either were as easy as possible. I propose working toward the following workflows:
User A wants to install DjangoBB standalone and installs the package djangobb-standalone (which depends on the package djangobb-app). The installer prompts for some config values, like the media directory or the database connection string. It then creates a rudimentary http server config. In short, it tries to minimize the time user A will have to spend editing config files and the like.
I actually think that this could benefit DjangoBB _a lot_ since it would make installing so much easier that an entire new group of people could use it. It would be awesome if DjangoBB were as easy to install as, say, phpmyadmin, because it would be no problem for sysadmins that don't have a clue about python to install it. OTOH, "copy the files over" as installation instructions isn't very satisfying, and for those who don't know python, let alone django, daunting if something doesn't work.
User B is writing a web application in django, wants to plug a forum into the website, and installs djangobb-app. The installer could prompt for a directory to put static content into, otherwise user B will have to put static content in place manually. Then user B edits/adds a couple of settings, points "^forum/" to djangobb.urls in the root urlconf, and is done.
While use case A could turn out to be a lot of work, use case B actually seems pretty simple to me; the app would need to be more decoupled from the project (for instance, forms.py would belong inside the app, it would probably make sense to give the project its own directory), in any case, the project would literally be yet another django project that makes use of the djangobb app.
Well, I'm looking forward to feedback on this
