Skip to content
Forum software straight outta 2008
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
Service Fixed logo not appearing on service page. Sep 25, 2018


Jaxboards is a PHP/MySQL forum software built sometime between 2007 and Oct 6th, 2010. It's pretty full featured and offers a unique experience over other forum software even today. That being said, it's showing its age, and relies on some flash and older technologies to get by. It is not recommended to run this in production these days.

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development purposes.


Tested on Apache and Linux only.

It is not recommended to run Jaxboards in production.


  • PHP 5.3.7
  • MySQL>=5.5.3
  • TLS certificate (due to hardcoded URLs in codebase)

You'll want a dedicated database just for Jaxboards just to avoid any kind of conflicts with anything else.

For the service setup you'll want your webserver configured like this:

  • The apex domain and www subdomain should point to the Service/ directory.
  • Wildcard subdomain of that apex domain should point to the root directory.

Jaxboards must be installed in the root directory of a domain or subdomain. You're not going to have a good time trying to get this working in a subdirectory.


Once you've met all the requirements, head to: https://$DOMAIN/Service/install.php, replacing $DOMAIN with your domain. This page gives you the option of installing the service or a standalone Jaxboards - pick whatever suits your needs.

The install script at Service/install.php handles configuration and setting up a new install. It does the following:

  • Saves configuration settings from the installer. Mainly this is database information, but it also saves the domain you're running the board on. Basically copies config.default.php to config.php and updates the values. Here's the direct PHP code what values are being set specifically:
        // Update with our settings.
        $CFG['boardname'] = 'Jaxboards';
        $CFG['domain'] = $JAX->p['domain'];
        $CFG['mail_from'] = $JAX->p['admin_username'] . ' <' .
            $JAX->p['admin_email'] . '>';
        $CFG['sql_db'] = $JAX->p['sql_db'];
        $CFG['sql_host'] = $JAX->p['sql_host'];
        $CFG['sql_username'] = $JAX->p['sql_username'];
        $CFG['sql_password'] = $JAX->p['sql_password'];
        $CFG['installed'] = true;
        $CFG['service'] = $service; // boolean if it's a service or not
        $CFG['prefix'] = $service ? '' : 'jaxboards';
        $CFG['sql_prefix'] = $CFG['prefix'] ? $CFG['prefix'] . '_' : '';
  • Figures out if you're installing a service (multiple boards like or a single-board install.
  • If it's a service install, install those special service tables.
  • Copy over the MySQL tables here. Service installs have an additional step of adding each board installed to the directory table. Once the database is imported, the admin user is created as well.

After install the MySQL credentials are saved in config.php. This is copied over from config.default.php so you can see what the format looks like there.

Service/blueprint.sql contains the base tables and base data for the database for a single-board install. Every table is prefixed with blueprint_ (and should be updated to match what the sql_prefix setting is in the config.php file before importing). In addition, a service install (multiple boards) has two additional tables, directory (containing a list of all the registered boards) and banlist (containing a list of IP addresses to ban). These are both described in the Service/install.php file.


If you're running an old Jaxboards database, you can update it to the latest with the update script. It's only meant to run via the CLI, so run it with this:

php ./Service/update.php

If you're just starting to use this repo, it's not needed.


If you want to contribute, great! We make use of some command line utilities, though there may be was to integrate these tools in your development environment in other ways. It is recommened you fix any errors given off by these tools before you commit anything, so we can keep our code clean and easy to manage. Here's how to get the developer tools working and running:

node.js Tools

We use a few tools made with node.js. I've been using pnpm to manage node.js dependencies, but feel free to use npm or yarn if you're more comfortable with that, just keep in mind the shrinkwrap.yaml file is incompatable with those.

Install the node.js tools with this command in the Jaxboards directory:

pnpm install

The tools have npm scripts for them, so you can easily get the tools working.

JS Compilation

EXPERIMENTAL / IN PROGRESS: All Javascript sourcecode is modularized into ES6 classes, and is bundled together using rollup. To build a bundled source ("jsnew.js") from the modules, run:

pnpm run build


Prettier automatically formats code to its standards. This keeps code easier to manage and makes sure anyone contributing keeps to a consistent style. The only limitation is that it's limited to the file types it supports, so we aren't using this for PHP or HTML. However, it does support CSS, JavaScript, YAML, and JSON, which we make use of.

Run with this command in the Jaxboards directory to run it on all the files:

pnpm run prettier



Stylelint adds some additional rules to keep CSS files clean and help us avoid trouble in the future with over-complicated CSS rules.

Run with this command in the Jaxboards directory to run it on all the files:

pnpm run stylelint

In additon, Stylelint supports automatic code fixing for some rules. This won't avoid every pitfall, but it should take care of some of the things Prettier does not. Run this fixer on all the files with this command in the Jaxboards directory:

pnpm run stylelint-fix


ESLint keeps the javascript clean. Run with:

pnpm run eslint

Composer tools

Composer is a package manager for PHP and tools made in PHP. As Jaxboards is a PHP project, it shouldn't be too surprising we make use of some PHP tools. We're using node-composer-runner to run composer commands with pnpm, so composer packages should be installed after you run pnpm install.


PHP_CodeSniffer is basically the equivalent of Stylelint for PHP. It also includes a tool to automatically fix fixable issues, which helps keep code looking great.

Run on all files with the following command in the Jaxboards directory:

pnpm run phpcs

And run this in the Jaxboards directory to run the fixer tool on all files:

pnpm run phpcbf


  • seanjohnson08 - Original developer
  • dgatwood - Updated the codebase to support PHP's MySQLi interface and work with PHP7
  • wtl420 - Maintainer of this fork.

See also the list of contributors who participated in this project.


This project is licensed under the MIT License - see the file for details

Third-Party Libraries

  • password_compat library so we can make use of PHP's built-in password hashing functions


  • Contributors to the original Jaxboards Service; Jaxboards wouldn't exist without feedback from everyone who's supported it over the years.
You can’t perform that action at this time.