You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Tao Bojlén 9115d29a88 update backend 3 days ago
.github/workflows update backend 3 days ago
.reuse fix DEP5 file to follow spec 4 years ago
.vscode add debug config 3 years ago
LICENSES move to REUSE copyright spec 4 years ago
backend update backend 3 days ago
frontend Cherry-picking fork fixes 2 years ago
gephi only put instances with a type on the graph 4 years ago
.dokku-monorepo fix backend app name in .dokku-monorepo 4 years ago
.gitignore frontend/cytoscape feature parity 4 years ago
.gitlab-ci.yml update backend 3 days ago prepare for 2.0.0 release 4 years ago fix #104 3 years ago
LICENSE Add LICENSE 4 years ago update backend 3 days ago
docker-compose.yaml update backend 3 days ago
example.env refactor/elixir backend 4 years ago
netlify.toml allow data: images in CSP 3 years ago
nlnet-logo.png add nlnet logo to about page 4 years ago
screenshot.png add deployment instructions to README 4 years ago 🌐

The map of the fediverse that you always wanted.

Read the latest updates on Mastodon: @fediversespace

A screenshot of


Though containerized, backend development is easiest if you have the following installed.

  • For the crawler + API:
    • Elixir
    • Postgres
  • For laying out the graph:
    • Java
  • For the frontend:
    • Node.js
    • Yarn

Running it


  • cp example.env .env and modify environment variables as required
  • docker-compose up
  • Create the elasticsearch index:
    • iex -S mix app.start
    • Elasticsearch.Index.hot_swap(Backend.Elasticsearch.Cluster, :instances)


  • cd frontend && yarn install
  • yarn start



./gradlew shadowJar compiles the graph layout program. java -Xmx1g -jar build/libs/graphBuilder.jar runs it.


  • yarn build creates an optimized build for deployment


This project doesn't crawl personal instances: the goal is to understand communities, not individuals. The threshold for what makes an instance "personal" is defined in the backend config and the graph builder SQL.


You don't have to follow these instructions, but it's one way to set up a continuous deployment pipeline. The following are for the backend; the frontend is just a static HTML/JS site that can be deployed anywhere.

  1. Install Dokku on your web server.
  2. Install dokku-postgres, dokku-monorepo, dokku-elasticsearch, and dokku-letsencrypt.
  3. Create the apps
  • dokku apps:create phoenix
  • dokku apps:create gephi
  1. Create the backing database
  • dokku postgres:create fediversedb
  • dokku postgres:link fediversedb phoenix
  • dokku postgres:link fediversedb gephi
  1. Set up ElasticSearch
  • dokku elasticsearch:create fediverse
  • dokku elasticsearch:link fediverse phoenix
  1. Update the backend configuration. In particular, change the user_agent in config.exs to something descriptive.
  2. Push the apps, e.g. git push dokku@<DOMAIN>:phoenix (note that the first push cannot be from the CD pipeline).
  3. Set up SSL for the Phoenix app
  • dokku letsencrypt phoenix
  • dokku letsencrypt:cron-job --add
  1. Set up a cron job for the graph layout (use the dokku user). E.g.
0 2 * * * /usr/bin/dokku run gephi java -Xmx1g -jar build/libs/graphBuilder.jar

Before the app starts running, make sure that the Elasticsearch index exists -- otherwise it'll create one called instances, which should be the name of the alias. Then it won't be able to hot swap if you reindex in the future.


NLnet logo

Many thanks to NLnet for their support and guidance of this project.