This Might Be Offensive
Getting Started with a Virtual Machine
The easiest way to get started is to download the development VM, which can be found at http://thismight.be/~thismightbe/vm.tgz. It was made in Fusion 4, but will work on a recent Workstation or ESX.
All user-level passwords are set to
[tmbo]. This includes the web site's unprivileged account (asdf) and the machine user thismightbe.
All root-level passwords are set to
[nsfw]. This includes the web site's admin account (admin) and the SSL certificate.
The codebase can be found in ~thismightbe/this-might-be-offensive as a read-only clone of this repo.
Rolling Your Own
If you want to build your own server, it won't take more than an hour or few, and you'll need the following packages:
You'll want to enable mod_rewrite and mod_ssl and configure them as appropriate. You'll also want to install the following perl modules from CPAN:
Point your webroot at the repository and create a new file in the
admin directory named
.config - this is where you will store your
The file follows .ini syntax, and should look something like this:
[tmbo] database_host = "localhost" database_user = "bob" database_pass = "my_password_is_hard" database_name = "name_of_database"
You'll also want to put the following lines in your crontab:
THEMAXX=/home/thismightbe/sites/tmbo MAILTOemail@example.com # m h dom mon dow cmd 5 0 * * * $THEMAXX/offensive/deleteOldFiles.pl 7 zips > /dev/null 2 0 * * * $THEMAXX/offensive/zipYesterday.pl zips 3 1 * * * $THEMAXX/offensive/deleteOldFiles.pl 2 quarantine > /dev/null 0 * * * * /usr/bin/nice /usr/bin/php5 $THEMAXX/admin/commentIndexer.php
tmbo's content protection is the same in development as it is in production, which means if you browse to your instance by IP, you're not going to see any images. Putting a thismight.be subdomain in your hosts file will work around this problem. For example:
Developing using GitHub
If you want to fork the project to contribute changes via github:
cd ~thismightbe rm this-might-be-offensive git clone git://github.com/USERNAME/this-might-be-offensive.git su -c "chgrp -R www-data ~thismightbe/this-might-be-offensive" - chmod -R g+w this-might-be-offensive
You'll need to build a replacement
admin/.config file as detailed above.
Problems with the web site are frequently well-documented by error messages emitted by trigger-error. Administrators see this output as part of the rendered page, but it is also recorded to the httpd's logs. On the VM they are located in
If you need anything to get running, help can usually be had in #tmbotech on EFnet.