iproute2-cheatsheet
iproute2-cheatsheet copied to clipboard
dmbaturin
Suggestion to add content
Some time ago I created a presentation that details some of the commands offered by iproute2.
https://gbraad.gitlab.io/tools-training/slides.html#/iproute2
Have a look and tell me what you think is valuable for me to propose as pull requests.
Could this also be possibly transitioned into a GitBook? I think it would do really well at that.
Gitbook? No. Just no. For starters, the "free for open source" plan allows no more than five collaborators. Second. I would rather not trust a closed cloud service if I want something to stay around even if I get eaten by a grue, with the current setup and workflow making mirrors of either the page or the git repo is trivial.
@dmbaturin It can be seen as a way to structure the archive. Adding a file called SUMMARY.md is all that is needed. My own knowledge-base project gets pushed to github pages, from https://gitlab.com/gbraad/knowledge-base/ as a CI runner.
Example SUMMARY.md: https://gitlab.com/gbraad/knowledge-base/blob/master/SUMMARY.md... and when run with something like https://github.com/gbraad/dockerfile-gitbook-server or https://github.com/getwarped/s2i-gitbook-server turns into http://gbraad.nl/knowledge-base/
Note: I think this issue can be closed... WDYT?
@predatorian3 I think the suggestion should first be; convert to markdown and let GitHub pages handle with publication. The current delivery of a HTML-file is not easy to deal with from a contribution standpoint, especially since HTML can be generated. Add a template file, let Jekyll handle the generation. This would also allow easier migration to a possible GitBook-structure... at the moment, the benefit is too little to consider this....