Kopano mail & collaboration SW integration for the Synology NAS using Docker wrapped in a SPK for the Package Manager.
Kopano is an open e-mail and groupware platform that can be used as an alternative for MS Exchange. It comes via Docker using pre-packaged binaries (e.g. Debian/Ubuntu DPKG) to ease installation. With Webmeetings and Mattermost Kopano enters into Unified Communications.
Kopano4S is available as free community beta edition based on nightly builds or two types of tested versions which are easier to use with less surprises than the beta: an also free default edition which is 3-9 months old or the up to date supported edition. The latter requires a subscription serial-number (SNR). The signed package is available via Community Package Hub which can be linked into Synology Package Center for automatic updates etc. There is no need to git-clone and build the package unless contributing and testing is planned. A project overview incl. FAQ's, package center integration, installation, Zarafa migration advise, screenshots etc are found on Z-Hub.io.
For testing you clone this GitHub repository and via build_spk.sh script build the Synology package file or maintain downloaded SPK via 7zip. For detailed instructions including structure and purpose of each files see CONTRIBUTING.md.
When the SPK is rolled out during install Synology copies over the script directory and extracts package.tgz to the target area in this case /var/packages/Kopano4s/target as base directory. Therefore the scripts are found in /var/packages/Kopano4s/scripts/ and the GUI in /var/packages/Kopano4s/target/ui/ and its sub-directories. Running and testing the scripts is by calling them from the cmd-line however note that the main kopano(4s) commands have been set as softlink in /usr/local/bin to make usage more conveniant. Pragmatic and fastrack testing can be done by copying over a script It is also possible to run the main install script from cmd-line via > sudo /var/packages/Kopano4s/scripts/postinst providing the MySql root password. This is because all settings usually coming from package.wizard are set to default. The same applies for testing the perl ui vi sudo perl index.cgi which has to be run from /var/packages/Kopano4s/target/ui/.