GNOME Extensions Manager¶

Description¶

This role manages GNOME Shell extensions by ensuring user extensions are enabled and by installing the CLI GNOME Extension Manager. The CLI tool facilitates the configuration and control of GNOME extensions via the command line.

Learn more about the CLI tool on its GitHub page and about GNOME Extensions at GNOME Extensions.

Overview¶

This role configures GNOME Shell extensions and installs the CLI GNOME Extension Manager for managing extensions.

Architecture¶

ARCHITECTURE.md draws GNOME Extensions Manager from its own metadata: the containers it runs under compose, what changes under swarm, how each volume is backed, and every role it depends on or is depended upon by.

Section	Drawn from
Compose	`meta/services.yml`
Swarm	`meta/services.yml` replicas and placement
Volumes	`meta/volumes.yml` against the NFS decision chain
Dependencies	`meta/services.yml` and `meta/main.yml` of every role

Purpose¶

The purpose of this role is to enhance and customize the GNOME desktop environment by managing shell extensions. It simplifies the process of installing and configuring extensions, thereby improving productivity and desktop functionality.

Features¶

Activates GNOME Shell extensions via gsettings.
Installs the CLI GNOME Extension Manager using the package manager.
Executes extension configuration commands for streamlined management.
Provides an automated method for managing and updating GNOME extensions.

Quick Setup¶

Development¶

Clone, set up the workstation, and deploy GNOME Extensions Manager onto the local stack:

git clone https://github.com/infinito-nexus/core.git
cd core
make onboard
make compose-deploy mode=reinstall apps=dsk-gnome-extensions full_cycle=false

Production¶

Install GNOME Extensions Manager directly onto the target machine: clone the repository, install the OS prerequisites and the repository toolchain, then deploy against localhost over a local connection (no SSH, no container):

git clone https://github.com/infinito-nexus/core.git
cd core
bash scripts/install/package.sh
make install
source scripts/meta/env/load.sh

APP=dsk-gnome-extensions
DOMAIN="<your-domain>"
TLS_MODE=self_signed
SSH_PUBLIC_KEY="<your-ssh-public-key>"
INVENTORY=inventories/production
infinito administration inventory provision "$INVENTORY" \
  --inventory-file "$INVENTORY/devices.yml" \
  --host localhost \
  --include "$APP" \
  --vars "{\"TLS_MODE\": \"$TLS_MODE\", \"DOMAIN_PRIMARY\": \"$DOMAIN\", \"users\": {\"administrator\": {\"authorized_keys\": [\"$SSH_PUBLIC_KEY\"]}}}"
infinito administration deploy dedicated "$INVENTORY/devices.yml" \
  --password-file "$INVENTORY/.password" \
  --diff -vv

Credits¶

Kevin Veen-Birkenbach

Part of the Infinito.Nexus Project and maintained by Kevin Veen-Birkenbach. Licensed under the Infinito.Nexus Community License (Non-Commercial).

That licence covers this role. The software it deploys is a separate grant: AGPL-3.0-only, under which commercial use is allowed. You owe its authors this much: publish the source of changes once you offer it over a network, which a hosted deployment does. Permission for one of the two is not permission for the other.

Addons¶

This role is a generic GNOME-extension installer driven by services.gnome-extensions.plugins, a 3-tuple list (action, uuid, url) consumed by cli-gnome-extension-manager. It ships no concrete extensions of its own and reads no meta/addons/ files. Roles that ship concrete GNOME extensions, such as dsk-gnome, declare them through the unified addon contract under meta/addons/ (requirement 026), with one file per extension (mechanism: extension, source: upstream, config: { uuid, url }); see that role for the per-file example.

Playwright exemption: GNOME Shell extensions are desktop-only and have no in-app web surface to drive, so they carry no Playwright spec (Confirmed Decision 11).