Installing modules

The core brings neither files, nor calendar, nor mail: those are modules, and you install only the ones you need. Each is independent — its own repository, its own packages, its own release rhythm.

Docker

With Docker there is nothing to do: the image already bundles twenty-one modules. This page concerns native package installations.

From the administration console (the simplest way) #

Open Administration → Marketplace, pick a module, install it. The server downloads the published package, checks its SHA-256 fingerprint, installs its dependencies first if it has any, then starts the module without restarting the instance. It appears in the application launcher straight away.

Note

This one-click installation works on a Linux instance. On Windows and macOS, go through the packages below.

From a package #

Each module publishes its own packages on the Releases page of its repository — one repository per module:

https://github.com/kubuno/drive/releases/latest      # same for office, mail, calendar, photos…

sudo apt install ./kubuno-drive_*_amd64.deb

sudo dnf install ./kubuno-drive-0.1.6-1.x86_64.rpm

kubuno-drive-setup-0.1.6-x64.exe        # à lancer en administrateur

sudo installer -pkg kubuno-drive-0.1.6-arm64.pkg -target /

The package drops the module into the core's installation and restarts the service for you. There is no central configuration to edit: the module announces itself to the core, which discovers it and publishes its routes.

Versions

A module requires a core whose version is at least its own — otherwise the package manager will refuse the installation. Update the core first.

Enabling, disabling, removing #

Everything is done from Administration → Applications → Installed modules: a disabled module stays in place but no longer answers. Complete removal goes through the same page, or through your system's package manager.

From source #

For a module you are developing, or whose package you want to build yourself:

git clone https://github.com/kubuno/drive && cd drive
bash build_deb.sh --install

Note

Writing your own module? The technical documentation explains the manifest, registration with the core and distribution.