Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Upcoming version of VictoryChat

branch: master

Fetching latest commit…


Cannot retrieve the latest commit at this time

Octocat-spinner-32 public
Octocat-spinner-32 templates
Octocat-spinner-32 .gitignore
Octocat-spinner-32 COPYING
Octocat-spinner-32 README.markdown
Octocat-spinner-32 chat.js
Octocat-spinner-32 config.json.default
Octocat-spinner-32 database.js
Octocat-spinner-32 login.js
Octocat-spinner-32 main.js
Octocat-spinner-32 package.json

VictoryChat 300

This is a fork of VictoryChat (even though they don't actually share any code), written in JavaScript:

  • CouchDB
  • Node.js (and express)
  • jQuery (and less-css)

The design goals, currently, are as follows:

  • Being able to run multiple web-servers on the same database
  • Being able to handle replicated databases without interruption
  • Handling around 3000 concurrent connections on one server / db
  • Making the UI fluent, responsive, and as solid as possible

The source code is littered with "// TODO"s. If you decide to contribute to this code, don't hesitate to add some yourself.

If you are interested in contributing, a lot of those TODOs are quite trivial, and - again - it is 100% JavaScript.



To run the sever, first install the required modules from npm:

cd victorychat-ng
npm install

Then install CouchDB

sudo apt-get install couchdb
sudoedit /etc/couchdb/local.ini

At the bottom of local.ini, in the [admins] section, add a new user with a random password.

Move config.json.default to config.json, and insert the couchdb username, password. If you decide to change the http port for the app, make sure to also change that number in the openid host parameter.

After all of this, run node main.js and go to http://localhost:5000.


Copyright (C) 2012-2013 Stefano Palazzo

VictoryChat 300 is licensed to you under the terms of the GNU General Public License, Version 3 or (at your option) any later version.

For more information, see COPYING.

Something went wrong with that request. Please try again.