Classic Forum, a modern, fast and flexible threaded forum software
Ruby HTML JavaScript PLpgSQL CSS
Latest commit 0247a0d Jan 3, 2017 Christian Kruse fix: fuck you, get it right!
Permalink
Failed to load latest commit information.
app fix: fuck you, get it right! Jan 3, 2017
bin
config feat: we now create redirections to the new thread Dec 27, 2016
db feat: we now have redirections on application basis Dec 27, 2016
doc added message tree sorting Jun 29, 2012
lib feat: we now can split threads Dec 23, 2016
log initial commit Jun 19, 2012
public typo Nov 8, 2016
script ref: renamed all models and controllers to miss cf prefix Apr 8, 2016
spec ref: bundle update; upgrades pygments as well Dec 18, 2016
vendor initial commit Jun 19, 2012
.gitignore feat: we now provide a vagrant file Jul 28, 2016
.rspec
.rubocop.yml ref: confirm to style guide Nov 8, 2016
.travis.yml bundle update, fixes travis May 11, 2016
Cheffile feat: we now provide a vagrant file Jul 28, 2016
Cheffile.lock feat: we now provide a vagrant file Jul 28, 2016
Gemfile fix: ordering gems alphabetically in a group Dec 27, 2016
Gemfile.lock bundle update Dec 27, 2016
Guardfile feat: added system notifications for guard Jan 3, 2016
LICENSE relicensing to AGPL3 Aug 7, 2015
README.md build icon in readme Jan 7, 2016
Rakefile made the default cforum schema (PG naming) non-default Mar 16, 2015
Vagrantfile feat: we now provide a vagrant file Jul 28, 2016
config.ru initial commit Jun 19, 2012
package.json ref: now using socket.io for websockets Sep 25, 2015

README.md

Classic Forum

Build Status

The Classic Forum is a modern and flexible threaded forum software written in Ruby on Rails. It uses PostgreSQL as its backend.

It tries to give the user an alternative to all questionable design- or function decisions and thus aims to be highly configurable without losing performance.

Requirements

  • PostgreSQL 9.3 or newer
  • Ruby 2 or newer
  • Rails 4.2

Installations