tommy/mobilizon
1
0
Fork 0
forked from potsda.mn/mobilizon
Code Pull requests Activity

Add FAQ for server requirements

Browse source 
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
This commit is contained in:
Thomas Citharel 2020-10-08 10:20:46 +02:00
parent d5c90af809
commit ca79f4dba0
No known key found for this signature in database
GPG key ID: A061B9DDE0CA0773
1 changed files with 34 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

34
docs/administration/faq.md Normal file
View file

@ -0,0 +1,34 @@
---
title: FAQ
---
# 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](./configure/geocoders.md).
<dl>
<dt>CPU</dt>
<dd><b>One should be enough</b>
<p>Depending on your number of users and instances you federate with, extra CPUs will be helpful.</p>
</dd>
<dt>RAM</dt>
<dd>
<b>512MB should be enough for Mobilizon, Nginx and PostgreSQL</b>
<p>Mobilizon will use at least around ~256MB and PostgreSQL and nginx can use ~20MB. Extra memory can improve tasks like compiling and building dependencies.</p>
</dd>
<dt>Storage</dt>
<dd><b>Depends how many users and events you have</b>
<p>A little space will be needed for Mobilizon and it's dependencies (damn you <code>node_modules</code>) 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.</p>
</dd>
<dt>Bandwidth</dt>
<dd>Any bandwidth will do, but higher numbers will improve the experience for users and will help federation.</dd>
</dl>