Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-11-15 01:30:44 -05:00
Code Issues Projects Releases Packages Wiki Activity
All Qubes OS Project documentation pages are stored as plain text files in this dedicated repository. By cloning and regularly pulling from this repo, users can maintain their own up-to-date offline copy of all Qubes documentation rather than relying solely on the Web.
5942 commits 11 branches 2681 tags 134 MiB
Find a file
Robin Schneider ec70076361
Use HTTPS everywhere (mechanical edit using util from https-everywhere) 
Ref: https://github.com/EFForg/https-everywhere/tree/master/utils/rewriter

```Shell
~/src/EFForg/https-everywhere/utils/rewriter/rewriter.js .
```
2020-12-19 19:57:07 +01:00
_dev Use HTTPS everywhere (mechanical edit using util from https-everywhere) 2020-12-19 19:57:07 +01:00
developer Use HTTPS everywhere (mechanical edit using util from https-everywhere) 2020-12-19 19:57:07 +01:00
external Fix redirects (fixes QubesOS/qubes-issues#6273) 2020-12-12 06:03:52 -08:00
introduction Use HTTPS everywhere (mechanical edit using util from https-everywhere) 2020-12-19 19:57:07 +01:00
project-security Clarify verification steps 2020-11-21 06:30:42 -08:00
user Use HTTPS everywhere (mechanical edit using util from https-everywhere) 2020-12-19 19:57:07 +01:00
.gitlab-ci.yml gitlab-ci: use local project reference 2020-11-27 03:55:05 +01:00
.travis.yml Update travis to bionic 2020-09-29 15:12:04 +02:00
CONTRIBUTING.md Fix link 2017-04-04 21:52:06 -07:00
doc.md Update links to Qubes-Community version 2020-12-07 22:31:41 -08:00
README.md Fix typo 2016-03-22 22:52:54 +00:00

README.md

Qubes OS Documentation

Canonical URL: https://www.qubes-os.org/doc/

All Qubes OS Project documentation pages are stored as plain text files in this dedicated repository. By cloning and regularly pulling from this repo, users can maintain their own up-to-date offline copy of all Qubes documentation rather than relying solely on the Web.

For more information about the documentation, including how to contribute, please see the Documentation Guidelines.