docs
docs copied to clipboard
debops
DebOps documentation
Currently [Getting Started with DebOps](https://docs.debops.org/en/latest/debops-playbooks/docs/guides/getting-started.html) is in the section [Guides](https://docs.debops.org/en/latest/debops-playbooks/docs/guides/index.html) of the chapter [DebOps playbooks](https://docs.debops.org/en/latest/debops-playbooks/docs/index.html). Path: Docs » DebOps playbooks » Guides » Getting Started with DebOps. - Short: Somewhere...
A metadata section cloud be added to the [introduction page](https://docs.debops.org/en/latest/ansible/roles/ansible-apt_install/docs/introduction.html) automaticlly which consists of: - Galaxy tags - Link to the VCS repo - Version - And more goodness
Ref: https://github.com/debops/debops-playbooks/issues/319
E.g. the [Readme of debops-contrib/ansible-lam ](https://raw.githubusercontent.com/debops-contrib/ansible-lam/master/README.md) says, "http://docs.debops.org/en/latest/ansible/roles/ansible-lam/docs/", which does not exists. Where as foodsoft points to http://docs.debops.org/en/latest/ansible/roles/ansible-contrib-foodsoft/docs, which does not exist either. What about setting up a doc repo...
Currently the header of `default/main.yml` files looks something like this: ``` YAML --- # .. vim: foldmarker=[[[,]]]:foldmethod=marker # debops.cryptsetup default variables [[[ # ======================================= # .. contents:: Sections # :local:...
Some rough outline and reminder for open non-tech issues **DebOps identity at a glance** - [ ] Vision - [ ] Mission - [ ] Message to the crowd -...
I think `Default variable details` is the better name for [Default variables: configuration](http://docs.debops.org/en/latest/ansible/roles/ansible-apt_preferences/docs/defaults-configuration.html) because this section explains complex role variables in more detail. With this change I would also propose...
Currently, the `docs/getting-started.rst` contain something like this: ``` rst Example playbook ---------------- Here's an example playbook that can be used to manage cryptsetup:: --- - name: Configure encrypted filesystems hosts:...
After finding http://keepachangelog.com/ I propose to over time switch the Changelog format to something more readable. I would also move the Copyright file contents into the Changelog, since the contributor...
Related to the redesign of the changelog format in #154 it might also be a good idea to think about migration/upgrade notes. http://keepachangelog.com/ also has a discussion about that: https://github.com/olivierlacan/keep-a-changelog/issues/34...