GNOME Desktop¶

Description¶

This role aggregates various GNOME desktop components to ensure a cohesive and fully functional GNOME environment on Arch Linux. It includes the installation and configuration of several sub-roles:

dsk-gnome-caffeine: Prevents the system from sleeping or locking automatically.
dsk-gnome-extensions: Manages GNOME Shell extensions and installs the CLI GNOME Extension Manager.
dsk-gnome-terminal: Installs GNOME Terminal, the official terminal emulator for GNOME.

Overview¶

This role aggregates essential GNOME desktop roles (including caffeine, extensions, and terminal) for a complete GNOME environment on Linux.

Architecture¶

ARCHITECTURE.md draws GNOME Desktop 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 provide a complete GNOME desktop experience by orchestrating multiple sub-roles. This simplifies deployment and management by ensuring that all key components are installed and configured in a consistent, system-wide manner.

Features¶

Aggregates multiple GNOME-related roles into one cohesive setup.
Installs and configures caffeine-ng to keep the desktop active.
Manages GNOME Shell extensions and integrates the CLI GNOME Extension Manager.
Installs GNOME Terminal for a robust command-line interface.
Ensures a seamless and uniform GNOME environment on Arch Linux.

Quick Setup¶

Development¶

Clone, set up the workstation, and deploy GNOME Desktop 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 full_cycle=false

Production¶

Install GNOME Desktop 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
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: GPL-2.0-or-later, under which commercial use is allowed. You owe its authors this much: publish the source of changes you distribute. Permission for one of the two is not permission for the other.

Addons¶

Role-level GNOME Shell extensions are declared in meta/addons/ (unified addon contract, requirement 026). They are installed through cli-gnome-extension-manager, which receives the action, uuid, and url from each addon’s config payload:

Addon	Mechanism	Default state	Bridges
`nasa-apod`	`extension`	required (always enabled)	none
`dash-to-dock`	`extension`	optional, disabled by default	none
`dash-to-panel`	`extension`	required (always enabled)	none

These are desktop GNOME Shell extensions with no in-app web surface to drive, so they are exempt from the Playwright requirement (requirement 026, Decision 11).