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 release rhythm — and ships as a single file: a Kubuno .kbpkg package, the same one on Linux, Windows and macOS.

Docker

With Docker there is nothing to do: the image already bundles twenty-one modules. This page is for instances installed some other way.

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

One-click installation works on all three systems: the .kbpkg is an archive the server opens by itself, with no host tooling. The catalogue it queries is https://api.kubuno.com/v1/modules, and the server only accepts official modules from the github.com/kubuno/ organisation.

En ligne de commande, hors ligne #

À réserver aux machines sans accès au catalogue — sinon, préférez l'installation en un clic ci-dessus. Chaque module publie un paquet par plateforme sur la page Releases de son dépôt — un dépôt par module. Le nom du fichier porte sa cible : <module>-<version>-<système>-<architecture>.kbpkg.

https://github.com/kubuno/drive/releases/latest      # same for office, mail, calendar, photos…
sudo kubuno modules:install drive-0.1.10-linux-x86_64.kbpkg
sudo systemctl restart kubuno
Effet de bord à connaître

Lancée avec sudo avant toute installation depuis la console, cette commande crée le magasin des modules (/var/lib/kubuno/modules-store) au nom de root. Or le service tourne sous l'utilisateur kubuno : il ne peut plus y écrire, et l'installation en un clic échoue ensuite sur « Erreur interne », pour tous les modules. Si cela vous arrive, une seule commande rétablit la console, sans redémarrage :
sudo chown -R kubuno:kubuno /var/lib/kubuno/modules-store

The command refuses every other format, checks the SHA-256 digests the archive carries — which protects a copy brought in on a USB stick, far from any catalogue — then drops the module into the core's store. Unlike one-click installation, it does not start it: the service restart is what brings it online.

One format only

A Kubuno package is not a system package: neither apt, nor dnf, nor a Windows or macOS installer is involved. Modules no longer publish .deb, .rpm, .exe or .pkg files — and the server would refuse them.

Seeing what is installed #

kubuno modules:list        # modules in the store, with their version
kubuno modules:commands    # the commands those modules add to kubuno

Enabling, disabling, removing #

Everything is done from Administration → Applications → Installed modules: a disabled module stays in place but no longer answers. Removing it stops its process, erases its files from the store and purges its registrations from the database.

Note

Removal only covers modules in the store. Those shipped with the server — the Docker image, for instance — are left untouched.

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_kbpkg.sh --install
Note

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