Chapters

Documentation

The current goal is a useful overview of Copland, with practical examples and visible gaps. The documents below have a starting point, but some topics still need work.

DocumentNext work
ServicesExplain tasks, logging, environment variables, resource limits and service hooks. Review the existing provider examples.
SecretsExplain native age keys alongside SSH keys, persistent destinations and key rotation.
Copland HomeDocument user services, session variables, managed directories and file conflicts during activation.
StorageAdd practical guidance for changing an existing dataset's mountpoint or quota.
SwitchingExplain how changed services are identified and how to inspect a failed switch.
ContainersReview the existing text and examples against the current module.
DevelopmentExpand the existing runner notes into an overview of module development, local packages and validation.

These are documentation tasks, not a list of missing system features. Getting started now contains Personal system and VPS examples that have been built but still need installation and boot testing. options.org and recipes.org remain intentionally empty for now.

Known implementation gaps

SSH authorized-key activation currently depends on the zfs-datasets activation step even when no additional datasets are declared. Such a configuration fails to evaluate. The VPS example includes a state dataset and therefore avoids this issue.

Integrated WLAN configuration and automatic clock synchronization are not yet provided by the module catalog.

Planned features

Configurable switch failures

We plan to make it possible to complete a switch even when selected services fail to start. This would allow those services to be started manually later without rolling back the whole system configuration.

Installation images

Future Copland installation ISOs are planned to include ZFS support out of the box. The existing install.sh workflow is separate from this planned installation image.