Board engine behind Fanboi Channel written in Python.
Fanboi2 has the following runtime requirements:
Additionally, the following packages are build-time requirements for compiling assets:
After all packages are installed, you may now setup the application:
$ git clone https://git.sr.ht/~sirn/fanboi2 fanboi2 $ cd fanboi2/ $ make all -j2
.env according to the configuring section below, then run:
$ make migrate $ make serve
You also need to run the worker (in another terminal) with:
$ make worker
And you're done! Please visit http://localhost:6543/admin/ to perform initial configuration.
Fanboi2 uses environment variable to configure the application. In case
make is used, you can create a file named
.env in the root directory of the project and our make configuration will happily use it up on
make serve or
make devserve. Otherwise you may want to use something like Direnv.
AUTH_SECRET-- Required. Secret for authentication/authorization cookie.
CELERY_BROKER_URL-- Required. Redis URL for Celery broker, e.g. redis://127.0.0.1/1
DATABASE_URL-- Required. Database URL, e.g. postgres://127.0.0.1/fanboi2
REDIS_URL-- Required. Redis URL, e.g. redis://127.0.0.1/0
SESSION_SECRET-- Required. Secret for session cookie. Must not reuse
GEOIP_PATH-- Path to GeoIP database, e.g. /usr/share/geoip/GeoLite2-Country.mmdb
SERVER_DEV-- Boolean flag whether to enable dev console, default False
SERVER_SECURE-- Boolean flag whether to only authenticate via HTTPS, default False.
Fanboi2 is open to any contributors, whether you are learning Python or an expert. To contribute to Fanboi2, it is highly recommended to use Vagrant as it is currently replicating the production environment of Fanboi Channel and perform all the necessary setup steps for you. Alternatively, if containers are your thing, you can find experimental, unsupported Docker Compose scripts in
In case you do not want to use Vagrant, you can install the dependencies from the installation section and run:
$ make dev $ make devhook
You can then configure the application (see configuration section) and run the server:
$ make migrate $ make devrun
cp vendor/docker/docker-compose.* ../)
openssl rand -hex 32
fanboi2; update the build and mount paths if untrue
docker-compose upfrom the same directory as the config files.
Images are published to sirn/fanboi2 on Docker Hub for every commit in master. By default, using Fanboi2 with the default
docker-compose.yml will start server in development mode which aids debugging. To disable development server capabilities, remove or rename the file
To submit patches to mailing list:
git clone https://git.sr.ht/~sirn/fanboi2
git config sendemail.to ~firstname.lastname@example.org
git format-patch -1 HEAD(refer to
git-format-patch(1)for more info)
git send-email -1(refer to
git-send-email(1)for more info)
To submit patches via GitHub Pull Request:
Submitting patches via mailing list is recommended in case you wish to remain anonymous (e.g. using thrown-away email address). GitHub, on the other hand, require you to create account with them and GitHub terms of service explicitly forbids having more than one account. Whether method you choose, our reviewer will review and merge the patch as soon as possible. It would be much appreciated if you could follow the following guidelines:
Fanboi2 uses a
Makefile-based workflow in its development and production cycle. You are encourage to use
make rather than directly invoking underlying commands. The provided
Makefile can be customized to certain extent using environment variable, such as:
VERBOSE=1-- Prints the underlying command when running
VIRTUALENV=virtualenv-- Specifies the
YARN=yarn-- Specifies the
VENVDIR=.venv-- Specifies the virtualenv directory.
ENVFILE=.env-- Specifies the file containing environment variable to load from.
The following make targets are available for use in production:
make allbuild the application and assets using production configurations.
make prodbuild the application using production configuration.
make serverun the application server.
make workerrun the application worker.
make assetsbuild assets.
make migratemigrate daabase.
make cleanremove everything.
The following make targets are available for use in development:
make devbuilds the application using development configuration.
make devrunrun the development application server, application worker and assets watcher.
make devhookinstall development pre-commit hook to the repository.
make devserverun the development application server.
make devassetsrun the development assets watcher.
The following make targets are available for use in test environment:
make testrun tests.
Most of these commands make use of VENVDIR and ENVFILE.
make is not your thing, you can set everything up manually, for example on macOS:
$ brew install python@3 node@8 yarn
Create the deploy environment:
$ mkdir -p $HOME/dev/fanboi2/venv $ virtualenv new -p python3 $HOME/dev/fanboi2/venv $ git clone https://git.sr.ht/~sirn/fanboi2 $HOME/dev/fanboi2/src
Setup the application:
$ cd $HOME/dev/fanboi2/src $ $HOME/dev/fanboi2/venv/bin/pip3 install -e .[dev,test] $ yarn install $ yarn run gulp $ vi $HOME/dev/fanboi2/envfile
$ $HOME/dev/fanboi2/venv/bin/alembic upgrade head $ $HOME/dev/fanboi2/venv/bin/fbctl serve --reload
In another terminal, run the worker:
$ $HOME/dev/fanboi2/venv/bin/fbcelery worker
pre-commit-hook if you want to contribute to the project:
$ $HOME/dev/fanboi2/venv/bin/pre-commit install
Copyright © 2013-2018, Kridsada Thanabulpong. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.