Mobilizon
This automated deployment is based on the guide at https://tcit.frama.io/documentation/administration/install/docker/.
Deploying Mobilizon
Prerequisites
You will need to create a DNS record for a new subdomain on your domain. These steps will be uniquie to your domain registrar, but it should be simple to create an A record with the desired subdomain pointed to your server's IP address.
In this example the we'll choose mobi as the subdomain, so the URL for the server will be mobi.example.org
Single sign-on (SSO)
If you would like to use single sign-on (SSO), you will need to have an IdP solution in place. Otherwise, your users will log in with username and password. Instructions for setting up Mobilizon with Authentik are provided below.
1. Edit Inventory file
The host group for Mobilizon is [mobilizon]. Place the following information under that group.
The standard vaules:
- The server's IP address.
server_tag=- This could be "mobilizon"ansible_user=- The non-root useransible_become_pass="{{ nb_become_pass }}"- or change variable to the appropriate value in the Vault.ansible_ssh_private_key_file="~/.ssh/id_ed25519_<server_tag>_<nonroot_user>"- The SSH key used to authenticate onto the server.
Extra values:
- None.
Example:
[mobilizon]
203.0.113.73 server_tag=mobilizon ansible_user=serveradmin ansible_become_pass="{{ mobilizon_become_pass }}" ansible_ssh_private_key_file="~/.ssh/id_ed25519_mobilizon_serveradmin"
2. Edit Ansible Vault variables
Edit the Ansible Vault file:
ansible-vault edit group_vars/all/vaulted_vars.yml
Include the following settings:
# Mobilizon
# If you have a unique credentials for this server.
mobilizon_become_pass: <sudo password for non-root user>
3. Edit env.template
The environmental variable for the Mobilizon deployment must be edited before running the playbook. It is located at lt-server-setup/roles/app_loomio/templates/env.template. Copy the file and name is env.edited make these edits.
Run this command to
4. Add random passwords to .env file
The .env file contains the passwords that the various Docker containers use for inter-container communications. Running the gen-passwords.sh script from the app_jitsi/templates directory will automatically generate and add strong passwords to the .env file. This also helps prevent intruders from impersonating a service account.
5. Run Ansible playbook command
Post-deployment setup
6. Register new user
7. Connect to proxy
Advanced options
The provides a path to configuring many other options upfront. These include:
- Custom identity providers (IdPs) like Keycloak, Authentik, and Zitadel.
ADD LINKS TO DOCS HERE