Git-Mirrors/qusal
1
0
Fork 0
mirror of https://github.com/ben-grande/qusal.git synced 2024-12-12 17:34:34 -05:00
Code Issues Packages Projects Releases Wiki Activity
49fb82a177
qusal/docs/BOOTSTRAP.md

98 lines
3.0 KiB
Markdown
Raw Normal View History

doc: separate documents per use case The main README is very large, by placing the documents in a separate directory, we allow the user to choose explicitly what they read, giving a better reading experience and allows a deeper understanding of the project.
2024-01-22 12:38:04 -05:00
# Bootstrap
Qusal bootstrap strategy.
## 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)
* [Essential](#essential)
* [Optional](#optional)
* [Internet communication](#internet-communication)
* [Files](#files)
* [Admin](#admin)
doc: separate documents per use case The main README is very large, by placing the documents in a separate directory, we allow the user to choose explicitly what they read, giving a better reading experience and allows a deeper understanding of the project.
2024-01-22 12:38:04 -05:00
## Description
doc: formula order matters
2024-02-28 06:47:51 -05:00
With so many packages, you may be wondering, how to bootstrap a new system?
Well, the answer depends on your goal.
doc: separate documents per use case The main README is very large, by placing the documents in a separate directory, we allow the user to choose explicitly what they read, giving a better reading experience and allows a deeper understanding of the project.
2024-01-22 12:38:04 -05:00
doc: spell check
2024-07-08 05:41:45 -04:00
Below you will find a list sorted by task, which have projects that can help
doc: formula order matters
2024-02-28 06:47:51 -05:00
you accomplish your mission. The order of which the formulas are applied can
matter in some circumstances, in those cases, it is noted in this page.
doc: separate documents per use case The main README is very large, by placing the documents in a separate directory, we allow the user to choose explicitly what they read, giving a better reading experience and allows a deeper understanding of the project.
2024-01-22 12:38:04 -05:00
## Essential
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
* Base (order matters):
* [dom0](../salt/dom0/README.md)
* [debian-minimal](../salt/debian-minimal/README.md)
* [fedora-minimal](../salt/fedora-minimal/README.md)
* [mgmt](../salt/mgmt/README.md)
* [sys-cacher](../salt/sys-cacher/README.md)
doc: separate documents per use case The main README is very large, by placing the documents in a separate directory, we allow the user to choose explicitly what they read, giving a better reading experience and allows a deeper understanding of the project.
2024-01-22 12:38:04 -05:00
## Optional
### Internet communication
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
* PCI devices holders:
* [sys-net](../salt/sys-net/README.md)
* [sys-audio](../salt/sys-audio/README.md)
* [sys-usb](../salt/sys-usb/README.md)
doc: reorganize bootstrap guide - The sys-gui was not implemented; - Light sys-net, sys-firewall, sys-audio and vault are not essential to bootstrap other formulas; and - Joining PCI formulas into one section is easier to find.
2024-06-04 08:21:44 -04: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
* Firewall, DNS Sinkhole and VPN Tunnel:
* [sys-firewall](../salt/sys-firewall/README.md)
* [sys-mirage-firewall](../salt/sys-mirage-firewall/README.md)
* [sys-pihole](../salt/sys-pihole/README.md)
* [sys-wireguard](../salt/sys-wireguard/README.md)
doc: add Tailscale too bootstrap guide
2024-07-05 11:15:57 -04:00
* [sys-tailscale](../salt/sys-tailscale/README.md)
doc: separate documents per use case The main README is very large, by placing the documents in a separate directory, we allow the user to choose explicitly what they read, giving a better reading experience and allows a deeper understanding of the project.
2024-01-22 12:38:04 -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
* Web browser and file retriever:
* [browser](../salt/browser/README.md)
* [fetcher](../salt/fetcher/README.md)
doc: separate documents per use case The main README is very large, by placing the documents in a separate directory, we allow the user to choose explicitly what they read, giving a better reading experience and allows a deeper understanding of the project.
2024-01-22 12:38:04 -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
* Instant messaging and E-Mail:
* [mail](../salt/mail/README.md)
* [signal](../salt/signal/README.md)
* [element](../salt/element/README.md)
doc: separate documents per use case The main README is very large, by placing the documents in a separate directory, we allow the user to choose explicitly what they read, giving a better reading experience and allows a deeper understanding of the project.
2024-01-22 12:38:04 -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
* Electronic cash:
* [sys-bitcoin](../salt/sys-bitcoin/README.md)
* [sys-electrumx](../salt/sys-electrumx/README.md)
* [sys-electrs](../salt/sys-electrs/README.md)
* [electrum](../salt/electrum/README.md)
feat: electrum bitcoin wallet
2024-01-31 10:53:04 -05:00
doc: separate documents per use case The main README is very large, by placing the documents in a separate directory, we allow the user to choose explicitly what they read, giving a better reading experience and allows a deeper understanding of the project.
2024-01-22 12:38:04 -05:00
### Files
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
* Passwords and TOTP:
* [vault](../salt/vault/README.md)
doc: separate documents per use case The main README is very large, by placing the documents in a separate directory, we allow the user to choose explicitly what they read, giving a better reading experience and allows a deeper understanding of the project.
2024-01-22 12:38:04 -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
* Multimedia:
* [reader](../salt/reader/README.md)
* [media](../salt/media/README.md)
* [sys-print](../salt/sys-print/README.md)
* [video-companion](../salt/video-companion/README.md)
doc: separate documents per use case The main README is very large, by placing the documents in a separate directory, we allow the user to choose explicitly what they read, giving a better reading experience and allows a deeper understanding of the project.
2024-01-22 12:38:04 -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
* File sharing:
* [usb](../salt/usb/README.md)
* [sys-ssh](../salt/sys-ssh/README.md)
* [sys-syncthing](../salt/sys-syncthing/README.md)
* [sys-rsync](../salt/sys-rsync/README.md)
doc: separate documents per use case The main README is very large, by placing the documents in a separate directory, we allow the user to choose explicitly what they read, giving a better reading experience and allows a deeper understanding of the project.
2024-01-22 12:38:04 -05:00
### Admin
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
* Remote administration:
* [remmina](../salt/remmina/README.md)
* [ssh](../salt/ssh/README.md)
* [sys-ssh-agent](../salt/sys-ssh-agent/README.md)
* Remote task execution and configuration management:
* [ansible](../salt/ansible/README.md)
* [docker](../salt/docker/README.md)
* [opentofu](../salt/opentofu/README.md)
* [terraform](../salt/terraform/README.md)
* Coding:
* [dev](../salt/dev/README.md)
* [sys-pgp](../salt/sys-pgp/README.md)
* [sys-git](../salt/sys-git/README.md)
* [sys-ssh-agent](../salt/sys-ssh-agent/README.md)
Reference in New Issue Copy Permalink