This project is just a collection of personal cheat sheets, about various GNU/Linux related topics.
Most of them are still very much TODO or in a Work In Progress state.
All of them should be treated with caution!
Check it online¶
Those cheat sheets are meant to be read online (alternatively, a backup is also available here on https://readthedocs.io), they are not meant to be read directly from their GitLab repository) because of the way this project will enhance their rendering.
How to use¶
You can browse the cheat sheets online (alternatively, a backup is also available here on https://readthedocs.io).
You can also clone this project and look at the cheat sheets from your terminal:
How to contribute¶
The cheat sheets of this project are simply written with the Markdown markup
language (they are located in
./cheatsheets/docs, see all
*.md files). Thus, they are very easy to read/write with any text editor.
Those cheat sheets are "build" into a simple static website, thanks to MkDocs. This is nice way of generating readable technical documentation, and I find it very appropriated for this project.
Both the Markdown markup language and MkDocs are greatly enhanced by Material for MkDocs (a theme/plugin for MkDocs). This makes it possible to add a lot of features that I find very interesting, especially for the cheat sheets format.
Also, I got access to Material for MkDocs insiders, i.e. "premium" features of Material for MkDocs (because I sponsor the project from time to time, in order to support their work a bit). So, I made a private fork of their repository (as allowed by their terms), this allows me to use their advanced functionalities.
Note that, in order to build this project, you don't need to also be part of Material for MkDocs insiders. If you are not part of it, then after building, your locally generated static website - hosting the cheat sheets for you to see how they render - will just miss a few features (which is not a big deal, really).
⚠️ Prerequisites ⚠️:
Clone this project:
Clone the mkdocs-material repository next to this README file (or where you want, but with a
mkdocs-materialsymlink next to this file):
- If you are not part of mkdocs-material insiders:
- If you are currently part of mkdocs-material insiders:
- If you were part of mkdocs-material insiders and you made a private fork: side note section at the end of this README for more details about why this extra step is needed and not handled by poetry)
Install the project dependencies (in a virtual environment) with
Make sure the installation went well by following the below Run section.
After editing some of the cheat sheets of this project, you might want to see how your contribution
will look like. In order to do so, just build and serve the cheat sheets to a local address (e.g.
If you have not cloned a mkdocs-material insiders repository (nor a forked one) in the previous installation section:
If you have cloned a mkdocs-material insiders repository (or a forked one) in the previous installation section:
Now just open http://127.0.0.1:1234 in a web browser and make sure the rendering of your modifications is OK.
Note that I use a private fork of mkdocs-material
insiders at version
If you are not part of mkdocs-material
insiders, or if you a part of it and using
a much older/newer version, then you might not get the same rendering (and it's OK).
Before submitting a merge/pull request, you can additionally execute the
run-cheat-sheets-tests.bash script, in order to check some formatting rules, spelling mistakes,
broken links etc.
If you have not cloned a mkdocs-material insiders repository (nor a forked one) in the previous installation section, then execute the following:
If you have cloned a mkdocs-material insiders repository (or a forked one) in the previous installation section, then execute the following:
Once you are satisfied with your modifications, you can simply share them with a merge/pull request (see how to create a merge request on GitLab here).
$ tree . -a -I ".git|.cache|.venv|site" . ├── .abbreviations # list of all the abbreviations used in the cheat sheets ├── .aspell-personal-dict # aspell dictionary extension, adding specific words present in some cheat sheets ├── docs # folder containing all the cheat sheets │ └── ... ├── .gitignore # file specifying untracked files / files to be ignored by git ├── mkdocs-material # Material-for-MkDocs git repository │ └── ... ├── .mkdocs-material-insiders.yml # configuration file of MkDocs (for people part of Material-for-MkDocs-insiders) ├── .mkdocs.yml # configuration file of MkDocs ├── poetry.lock # lock file of poetry ├── pyproject.toml # configuration file of poetry (dependencies specification, project information, build system, etc) ├── README.md # current file ├── .readthedocs.yml # configuration file for readthedocs.org ├── tests # folder containing all tests scripts │ ├── run-cheat-sheets-tests.bash # main bash script, running all the others, checking for formatting rules, spelling mistakes, broken links, etc. │ └── ... └── TODO.md # TODO list
You might have noticed that the
poetry.lock file is ignored by Git. Even if, according to the
it is recommended to include the
poetry.lock file in version control, in order to ensure
I made this choice because a dependency to the
mkdocs-material-insiders repository might prevent
you from successfully building the project if you are not part of the "Material for MkDocs
insiders" (see https://squidfunk.github.io/mkdocs-material/insiders/). I didn't find a way to
support multiple sources for the
mkdocs-material dependency, e.g. one source for the
mkdocs-material "general" repository, and one for the
mkdocs-material "insiders" repository
(keeping the insiders one private, as kindly asked here). So, unless someone has a better
solution to propose: the
poetry.lock file won't be tracked.
Note that this also explains why you have to clone the
mkdocs-material dependency (insiders or
not) "by hand" and not let poetry automatically handle it.