00f81fa95c
The way we're handling them is to have a global timer that is reset at any point a task is ran. This gives a maximum amount of chances to any task to have its dependencies resolve. A minimum of 60s is given, but in reality the chances are the conditions for trying to resolve were already present before the timeout started counting towards that particular dependency. Note that a long running task, when successfully ran, does not cause the timeout to be reached. E.g. at 10s of timeout a task is started, the loop is not executed until the task exits. When it exits the branch followed is for a task that ran, which means that even if the task took 70s total (which gives us 80 seconds) a timeout of 60s wouldn't apply here. Though, please, don't make your tasks take that much time to run! |
||
---|---|---|
.. | ||
_support | ||
in-depth | ||
.gitignore | ||
about.adoc | ||
boot_process.adoc | ||
default.nix | ||
getting-started.adoc | ||
pkgs.nix | ||
porting-guide.adoc | ||
README.md | ||
resources.adoc |
Documentation internal notes
This document is not to be generated into the website/documentation.
Implementation notes
This documentation folder generates the Mobile NixOS website and documentation as a whole.
The documentation is to be written in asciidoc, and converted through a custom pipeline through the Asciidoctor API. Markdown files are accepted in the pipeline, but frowned upon except for the simplest documentation articles.
The build pipeline can be improved upon, and contributions doing so are welcome!
Main Page and News
To reduce the amount of irrelevant contents in the documentation folders, the main page, and news entries from the Mobile NixOS website have been split into the Mobile NixOS website repository.
This also allows more leeway to add additional non-documentation relevant pages to the website. The documentation folder of the main repository is used solely for documentation.
Devices list
The devices
folder is special and assumes it will be replaced in-place with
asciidoc source files generated from a build outside of the main documentation
build. This is because it is generated from the actual device descriptions from
the repository.
Sitemap
The sitemap is simply a dump of all document files and "catalogs" from as parsed by Asciidoctor.