Skip to content

document QubesDB+systemd provisioning pattern #166

@cfm

Description

@cfm

Describe the change

Now that we have a pattern we like for configuring VM-specific services (freedomofpress/securedrop-workstation#1004), we should document it and/or provide a minimal example so that it's easily replicable.

How will this impact users?

As a Workstation developer, I don't want to reinvent the wheel.

As a new Workstation developer, I want an abstract example of what a wheel is, since that's a pattern I haven't seen in any other system I've worked on.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions