-
Notifications
You must be signed in to change notification settings - Fork 110
Admin Manual
In this section, we cover all aspects of administration within a running PEPS server. All details about how to operate the server itself are detailed in the next section.
To create users, hit on the Settings icon in the Topbar menu, then hit on Bulk upload in the sidebar menu. you can quickly add users using the field.
To create a single user, hit on the People icon in the Topbar menu, then hit on the Users in the sidebar menu. Click the New user button to view the form. Enter user name, email and password to create a new user account.
To create teams hit the People icon in the Topbar menu, then hit Teams in the Sidebar menu. Teams are automatically created if you create users with teams options via Bulk upload. To create a new team hit "New team" button in the Sidebar.
Classes are used to protect communications. By default open, internal, encrypted classes are created.
To create teams hit the Settings icon in the Topbar menu, then hit Classification in the Sidebar menu. Team classes are automatically created if you create users with teams options via Bulk upload. To create a new class hit "New class" button in the Sidebar.
Once created, you can change class propeties by clicking on the class in the classes list to view. In the edit form you can change class name, description, category and allow or disallow internet diffusion.
You can also create Filters and view users who are using this class in the messages.
To change users properties hit the People icon in the Topbar menu, then hit Users in the Sidebar menu. You can scroll throught the Users list, then select a user and view or edit his properties. You can update user level, add or remove team membership, and provide with extra admin or super admin powers via Edit form.
You can also block this user, change his/her password or delete user using top right buttons.
This manual details how to operate the PEPS server which is conveniently packages using 5 Docker containers that are meant to be run on a single host or virtual machine:
- The PEPS server itself, a Node.js application
- MongoDB which is the main database
- Solr for search
- Haraka for inboud and outbound SMTP servers (running on two containers)
In this initial public release, TLS is not activated by default for SMTP.
Test that your SMTP service is properly configured with tools such as MXToolBox.
There are several ways to backup your PEPS data, including using rsync directly at the host running the containers. However, to ensure data integrity, we can use first mongodump
to generate a fixed backup:
# Backup of raw data (content, files)
docker exec -it peps_mongod mongodump -h HOST -d rawdata --out /data/backup/BACKUPNAME
# Backup of metadata
docker exec -it peps_mongod mongodump -h HOST -d webmail --out /data/backup/BACKUPNAME
Run make update
to update the PEPS containers to the latest version. Your data is naturally untouched.
You can open a mongo session to directly connect to the PEPS database backend by typing:
docker exec -it peps_mongod mongo