[ansible] Add Ansible article with references and tags

[friesenkiwi]

Hi. I have developed an Ansible collection that contains roles both for administration of an uberspace itself (including tools, domains, webbackends, price etc.) and certain software to install into it:

• https://github.com/friesenkiwi/ansible-collection-uberspace
• https://galaxy.ansible.com/friesenkiwi/uberspace

The roles for the software are based on lab articles.

My main driver is that I'd like to enable other people to just execute one command and have a up and running production-ready software from scratch, including uberspace registration and domain DNS config (via INWX). THis already works for Pleroma and Prosody

This PR includes an article about Ansible itself, as well as a tag and a note for each article for which a known Ansible role exists:

• PostgreSQL
• Coturn
• Prosody
• Pleroma
• Babybuddy

I'd be very happy to adjust this PR and it's contents as well as the collection/roles according to comments. Also of course happy if you'd like to adapt the collection officially or if anybody would like to contribute to it e.g. by modeling some other lab article as a new role.

[luto]

Aw, this is so nice, but we can't include it :( There are a couple of projects adding ansible modules to uberspace, for example the one macrominds made. However, we're unable to provide support for 3rd-party ansible modules and we provide support for everything in the lab. So we can't include the modules in the lab. Sorry :(

[friesenkiwi]

@luto All right, I understand the problem that support from you might be expected by users if the roles/modules are presented too prominently in the lab and you cannot provide it.

On the other hand, would you think these community contributions could also be valuable to uberspace users in a way? Because if so, maybe we could find some kind of middle ground, like e.g. just one page "Unsupported 3rd party community contributions" with explicit support waiver where only links to external resources are listed or so?

For example I myself wasn't aware of @macrominds' contribution (so thanks for linking!) although I had looked around before.

Ah, I was just thinking, maybe you suspect users might be generating more "classical" support effort after using one of these roles and breaking something? Of course there's a possibility that could happen, but I would argue:

• Users who know what Ansible is, how to install and use it probably also most of the time know their way around
• It might actually lower the amount of support needed in certain cases, if specific configurations work "out of the box"
• The roles could be adjusted so it writes some file to "mark" accounts which have used the role and therefore you could easily spot them and explain that support is not possible
• I could also otherwise change the roles if you deem things too risky or undesireable
• There will be left some "Restrisiko", I agree. It could be a decision to try it out for a while and see if it creates problems and if yes remove the reference again?

Cheers,

[tpraxl]

@friesenkiwi here is the issue for the macrominds roles, providing the group readme link, FYI. I closed the issue due to a lack of interest.