mailinabox/setup/management.sh

#!/bin/bash

source setup/functions.sh

apt_install python3-flask links duplicity

# Create a backup directory and a random key for encrypting backups.
mkdir -p $STORAGE_ROOT/backup
if [ ! -f $STORAGE_ROOT/backup/secret_key.txt ]; then
	openssl rand -base64 2048 > $STORAGE_ROOT/backup/secret_key.txt
fi

# Link the management server daemon into a well known location.
rm -f /usr/bin/mailinabox-daemon
ln -s `pwd`/management/daemon.py /usr/bin/mailinabox-daemon

# Create an init script to start the management daemon and keep it
# running after a reboot.
rm -f /etc/init.d/mailinabox
ln -s $(pwd)/conf/management-initscript /etc/init.d/mailinabox
update-rc.d mailinabox defaults

# Start it.
service mailinabox restart
move management into a daemon service running as root * Created a new Python/flask-based management daemon. * Moved the mail user management core code from tools/mail.py to the new daemon. * tools/mail.py is a wrapper around the daemon and can be run as a non-root user. * Adding a new initscript for the management daemon. * Moving dns_update.sh to the management daemon, called via curl'ing the daemon's API. This also now runs the DNS update after mail users and aliases are added/removed, which sets up new domains' DNS as needed. 2014-06-03 13:24:48 +00:00			`#!/bin/bash`

			`source setup/functions.sh`

re-do the backup script to use the duplicity program Duplicity will manage the process of creating incremental backups for us. Although duplicity can both encrypt & copy files to a remote host, I really don't like PGP and so I don't want to use that. Instead, we'll back up to a local directory unencrypted, then manually encrypt the full & incremental backup files. Synchronizing the encrypted backup directory to a remote host is a TODO. 2014-06-09 13:34:52 +00:00			`apt_install python3-flask links duplicity`
new backup script, see #11 2014-06-03 20:21:17 +00:00
			`# Create a backup directory and a random key for encrypting backups.`
			`mkdir -p $STORAGE_ROOT/backup`
			`if [ ! -f $STORAGE_ROOT/backup/secret_key.txt ]; then`
			`openssl rand -base64 2048 > $STORAGE_ROOT/backup/secret_key.txt`
			`fi`
move management into a daemon service running as root * Created a new Python/flask-based management daemon. * Moved the mail user management core code from tools/mail.py to the new daemon. * tools/mail.py is a wrapper around the daemon and can be run as a non-root user. * Adding a new initscript for the management daemon. * Moving dns_update.sh to the management daemon, called via curl'ing the daemon's API. This also now runs the DNS update after mail users and aliases are added/removed, which sets up new domains' DNS as needed. 2014-06-03 13:24:48 +00:00
			`# Link the management server daemon into a well known location.`
			`rm -f /usr/bin/mailinabox-daemon`
			ln -s `pwd`/management/daemon.py /usr/bin/mailinabox-daemon

			`# Create an init script to start the management daemon and keep it`
			`# running after a reboot.`
			`rm -f /etc/init.d/mailinabox`
			`ln -s $(pwd)/conf/management-initscript /etc/init.d/mailinabox`
			`update-rc.d mailinabox defaults`

			`# Start it.`
			`service mailinabox restart`