Development guide #
These instructions are for hacking on Bonfire. If you wish to deploy in production, please refer to our deployment guide instead.
Hello, potential contributor! :-)
This is a work in progress guide to getting up and running as a developer. Please ask questions in the issue tracker if something is not clear and we'll try to improve it.
Status: beta - have fun and provide feedback 🙏 #
Bonfire is currently beta software. While it's fun to play with it, we would not recommend running any production instances (meaning not using it for your primary fediverse identity) yet because it's not quite ready for that today.
Either way, you need to first clone this repository and change into the directory and then do some configuration:
$ git clone https://github.com/bonfire-networks/bonfire-app bonfire
$ cd bonfire
Pick a flavour #
Bonfire is a flexible platform that powers a variety of social networks. The first thing you have to choose is which app (or "flavour") you want to hack on:
classic ("Bonfire Social", a toot-based social network that interoperates with the fediverse)
cooperation (for building cooperative communities)
reflow (for community economic activities)
haha (for learning new things)
Note that at the current time, the core team are focusing most of their efforts on the classic flavour and this is where we recommend you start.
You first need to install just which is a handy tool (a
make alternative) to run commands defined in
So for example if you want to run the
classic flavour, run:
export FLAVOUR=classic (you may also want to put this in the appropriate place in your system so your choice of flavour is remembered for next time)
- Then edit the config (especially the secrets) for the current flavour in
Option A - the entry way (fully managed via docker-compose, recommended when you're first exploring) #
- Recent versions of Elixir (1.13+) and OTP/erlang (24+)
- Recent versions of Rust and Cargo
- Postgres 12+ (or rather Postgis if using the bonfire_geolocate extension)
- Meili Search (optional)
You will need to set the relevant environment variables in the .env file (see above) to match your local install of Postgres.
If you want search capabilities, you'll also need to setup a Meili server and set the relevant env variables as well.
Set an environment variable to indicate your choice:
export WITH_DOCKER=no and proceed to Hello world!
Option E - the nix one (dev environment with Nix) #
The tool direnv is necessary for the nix setup as the nix shell environment will use variables defined on
.envrc to set itself up.
Note: when you run
direnv allow on the bonfire-app directory for the first time, nix will automatically fetch the dependencies for bonfire. The process will take a while as it's downloading everything needed to use the development environment. Afterwards you will be able to use just fine. Proceeding times you enter the directory, the shell with automatically set up for your use without downloading the packages again.
You will need to update the db directory which is automatically created by nix the first time you initialized the shell with
direnv allow. You can do so with the following steps:
props.nix to the settings you want.
just nix-db-init to create the database and user for postgres defined on
- Modify the
.env file to comment out all
POSTGRES_* variables. These are populated automatically by nix. So if the variables are set here, you may get issues with overriding your settings in
props.nix when using bonfire.
- You can now proceed to Hello World!
Note: if you ever want to shut off the postgres server in nix, simply run the nix-db targets in just:
# stop postgres server running locally
just nix-db stop
# start postgres server running locally
just nix-db start
Hello world! #
- From a fresh checkout of this repository, this command will fetch the app's dependencies and setup the database (the same commands apply for all three options above):
- You should then be able to run the app with:
- See the
just commands below for more things you may want to do.
By default, the back-end listens on port 4000 (TCP), so you can access it on http://localhost:4000/
Your first step will be to create an account to log in with. The
easiest way to do this is with our mix task:
$ just mix bonfire.account.new
Enter an email address: root@localhost
Enter a password:
Your password must be at least 10 characters long and the output could be more helpful if you don't do that. This task seems to work most reliably if you open a second terminal window with the devserver running. We're not sure why.
You should then be able to log in and create a user through the web interface.
If you would like to become an administrator, there is a mix task for that too:
just mix bonfire.user.admin.promote your_username
The Bonfire Environment #
We like to think of bonfire as a comfortable way of developing software - there are a lot of
conveniences built in once you know how they all work. The gotcha is that while you don't know them, it can be a bit overwhelming. Don't worry, we've got your back.
Note: these are still at the early draft stage, we expect to gradually improve documentation over time.
The code is somewhat documented inline. You can generate HTML docs (using
Exdoc) by running
Additional information #
messctl is a little utility for programmatically updating the .deps files from which the final elixir dependencies list is compiled by the mess script. The only use of it is in the dep-* tasks of the Makefile. It is used by some of the project developers and the build does not rely on it.
./extensions/ is used to hack on local copies of Bonfire extensions. You can clone an extension from its git repo and use the local version during development, eg:
just dep-clone-local bonfire_me https://github.com/bonfire-networks/bonfire_me
./forks/ is used to hack on local copies of any other dependencies.
You can migrate the DB when the app is running (also runs automatically on startup):
You can generate a dependency graph using
just xref-graph which will generate a DOT file at
docs/ (if Graphviz is installed it will also generate an SVG visualisation using
Usage under Windows (WSL, MSYS or CYGWIN) #
By default, the
justfile requires symlinks, which can be enabled with the help of this link.
See the pull request adding WSL support for details about usage without symlinks.
just commands #
just followed by any of these commands when appropriate rather than directly using the equivalent commands like
docker-compose, etc. For example,
just setup will get you started, and
just dev will run the app.
You can first set an env variable to control which mode these commands will assume you're using. Here are your options:
WITH_DOCKER=total : use docker for everything (default)
WITH_DOCKER=partial : use docker for services like the DB
WITH_DOCKER=easy : use docker for services like the DB & compiled utilities like messctl
WITH_DOCKER=no : please no
just help to see the list of possible commands and what they do.
EACCES Permissions Error #
If you get a permissions error when following any of the steps, run the following command and it should be fixed:
cd bonfire && sudo chown -R yourusername:yourusername .
Note that the command should be modified so your shell is pointing to wherever you have bonfire installed. If you are already in the bonfire directory then you only need to worry about running the
chown portion of the command.
Unable to access Postgres database #
If you are getting any
:nxdomain errors, check if you have any firewalls that may be blocking the port on your system.
For example, if you are running UFW (a lot of Linux distros do), run the following command to allow access to port 4000:
sudo ufw allow 4000
(Mix) Package fetch failed #
** (Mix) Package fetch failed and no cached copy available (https://repo.hex.pm/tarballs/distillery-2.0.12.tar)
In this case, distillery (as an example of a dependency) made a new release and retired the old release from hex. The new version (
2.0.14) is quite close to the version we were depending on (
2.0.12), so we chose to upgrade:
mix deps.update distillery
This respects the version bounds in
~> 2.0), so increment that if required.
(DBConnection.ConnectionError) tcp recv: closed #
** (DBConnection.ConnectionError) tcp recv: closed (the connection was closed by the pool, possibly due to a timeout or because the pool has been terminated)
In this case, the seeds were unable to complete because a query took too long to execute on your machine. You can configure the timeout to be larger in the
config/dev.exs in your editor.
- Find the database configuration (search for
timeout: 60_000 to the list of options:
config :bonfire, Bonfire.Repo,