qusal/salt/fedora/README.md

# fedora

Fedora Template in Qubes OS.

## Table of Contents

*   [Description](#description)
*   [Installation](#installation)
*   [Usage](#usage)

## Description

Creates the Fedora template as well as a Disposable Template based on it.

## Installation

*   Top:

```sh
sudo qubesctl top.enable fedora
sudo qubesctl --targets=fedora-40 state.apply
sudo qubesctl top.disable fedora
```

*   State:

<!-- pkg:begin:post-install -->

```sh
sudo qubesctl state.apply fedora.create
sudo qubesctl --skip-dom0 --targets=fedora-40 state.apply fedora.install
```

<!-- pkg:end:post-install -->

## Usage

AppVMs and StandaloneVMs can be based on this template.
refactor: initial commit 2023-11-13 09:33:28 -05:00			`# fedora`

			`Fedora Template in Qubes OS.`

			`## Table of Contents`

doc: lint markdown files Only way to have a unified markdown syntax is to enforce the wanted syntax by linting the files. Don't rely on the many markdown syntaxes, be consistent. 2024-07-04 11:10:11 -04:00			`* [Description](#description)`
			`* [Installation](#installation)`
			`* [Usage](#usage)`
refactor: initial commit 2023-11-13 09:33:28 -05:00
			`## Description`

			`Creates the Fedora template as well as a Disposable Template based on it.`

			`## Installation`

doc: lint markdown files Only way to have a unified markdown syntax is to enforce the wanted syntax by linting the files. Don't rely on the many markdown syntaxes, be consistent. 2024-07-04 11:10:11 -04:00			`* Top:`

refactor: initial commit 2023-11-13 09:33:28 -05:00			```sh
doc: prefix qubesctl with sudo Fixes: https://github.com/ben-grande/qusal/issues/20 2024-02-23 10:54:35 -05:00			`sudo qubesctl top.enable fedora`
feat: bump Fedora version 2024-06-12 09:00:59 -04:00			`sudo qubesctl --targets=fedora-40 state.apply`
doc: prefix qubesctl with sudo Fixes: https://github.com/ben-grande/qusal/issues/20 2024-02-23 10:54:35 -05:00			`sudo qubesctl top.disable fedora`
refactor: initial commit 2023-11-13 09:33:28 -05:00			```

doc: lint markdown files Only way to have a unified markdown syntax is to enforce the wanted syntax by linting the files. Don't rely on the many markdown syntaxes, be consistent. 2024-07-04 11:10:11 -04:00			`* State:`

refactor: initial commit 2023-11-13 09:33:28 -05:00			`<!-- pkg:begin:post-install -->`
doc: lint markdown files Only way to have a unified markdown syntax is to enforce the wanted syntax by linting the files. Don't rely on the many markdown syntaxes, be consistent. 2024-07-04 11:10:11 -04:00
refactor: initial commit 2023-11-13 09:33:28 -05:00			```sh
doc: prefix qubesctl with sudo Fixes: https://github.com/ben-grande/qusal/issues/20 2024-02-23 10:54:35 -05:00			`sudo qubesctl state.apply fedora.create`
feat: bump Fedora version 2024-06-12 09:00:59 -04:00			`sudo qubesctl --skip-dom0 --targets=fedora-40 state.apply fedora.install`
refactor: initial commit 2023-11-13 09:33:28 -05:00			```
doc: lint markdown files Only way to have a unified markdown syntax is to enforce the wanted syntax by linting the files. Don't rely on the many markdown syntaxes, be consistent. 2024-07-04 11:10:11 -04:00
refactor: initial commit 2023-11-13 09:33:28 -05:00			`<!-- pkg:end:post-install -->`

			`## Usage`

			`AppVMs and StandaloneVMs can be based on this template.`