Skip to content

FAQ

Should I have a big server to run Mobilizon?

Not really. Being written in Elixir, Mobilizon doesn't need much resources once it's running. If you plan to open your instance to the public, plan in advance higher values for the following given requirements.

Note

If you plan to self-host a address/geocoding server as well, the requirements are quite on another level.

CPU
One should be enough

Depending on your number of users and instances you federate with, extra CPUs will be helpful.

RAM
512MB should be enough for Mobilizon, Nginx and PostgreSQL

Mobilizon will use at least around ~256MB and PostgreSQL and nginx can use ~20MB. Extra memory can improve tasks like compiling and building dependencies.

Storage
Depends how many users and events you have

A little space will be needed for Mobilizon and it's dependencies (damn you node_modules) themselves. Otherwise, storage usage will grow mostly with user's profile pics and pictures associated to events. Also the PostgreSQL database can start to weigh a bit after a while, depending on how many events you create and how many other instances you follow.

Bandwidth
Any bandwidth will do, but higher numbers will improve the experience for users and will help federation.

A Mobilizon dependency fails to compile (source install)

Some Mobilizon dependencies require system tools or libraries to compile (such as cmake or gcc). You might be missing a system dependency.

Check the source install guide (especially the "Basic tools" section), make sure everything is installed and clean and recompile Mobilizon's dependencies with:

MIX_ENV=prod mix deps.clean --all
MIX_ENV=prod mix clean
MIX_ENV=prod mix compile

I am unable to send any emails

The default Mobilizon configuration assumes a local SMTP server is available on the same server. To tweak this for your own setup, see this page.

What should I backup?

You'll need to backup the PostgreSQL database (we recommend Barman), your config file (such as /etc/mobilizon/config.exs or config/runtime.exs, depending on how you installed Mobilizon) and the user's picture directory in uploads/.

For now this isn't supported (unless you edit the front-end files directly).

How can I give a user moderator/administrator permissions?

For now this is only possible through CLI.

I can't install dependencies with Yarn

If you have the following error:

ERROR: [Errno 2] No such file or directory: 'install'
It means that you installed the yarn from Debian/Ubuntu directly, which provides the cmdtest package, which is completely unrelated. Follow the instructions on the Source install guide to install the proper tool.

How to upgrade PostgreSQL ?

Info

If you're using an install based on Docker, it is required to dump and restore when upgrading the postgis image to new major versions of PostgreSQL or PostGIS. A version of postgresql-client is included in the mobilizon image if needed.

We use the PostGIS extension to hold the geospatial data. Migrating to a new major PostgreSQL version (with pg_upgradecluster) is not supported when there's also a PostGIS upgrade.

For instance migrating from Debian Buster (10) to Bullseye (11) upgrades PostgreSQL from 11 to 13, but also Postgis from 2.5 to 3.1, so you won't be able to perform a simple upgrade.

In this case, it's better to:

  • Dump the database (with pg_dump) from the old PostgreSQL cluster.
  • Stop the old cluster.
  • Create and start the new one (if not already done when upgrading the system).
  • Create the database, database user back (according to the credentials in your mobilizon configuration).
  • Add the extensions back to the database CREATE EXTENSION extension (where extension is postgis, pg_trgm and unaccent).
  • Import the dump to your new cluster (with pg_restore).

Warning

If you have other databases that don't use Postgis on the same server, you need to DROP the mobilizon database (or any other database that uses Postgis and that you have already dumped), then perform the pg_upgradecluster command to migrate these simple databases to the new cluster.

If everything works fine after the upgrade and after making sure you are running on the new cluster, you may drop the old cluster and remove the postgresql-11 dependencies.

A few links related to this:

In french 🇫🇷:


Last update: August 19, 2021