OS/Environment

None yet, but I'm working on OS X v10.11.6 'El Capitan' client-side. (See 'The way of deployment (cloud or local)' below for details on considered server infrastructure.)

Ansible version

None yet, as I haven't yet gotten that far into setting up Algo.

Version of components from requirements.txt

Not applicable (see above.)

Summary of the pro

Right now in different places in the SE codebase there are references to /opt and then as well to /usr.

All SE code should reference one place only. Could someone please create a PR that fixes this.

This PR should also take PR #454 into consideration (no conflicts)

PiVPN is currently failing on Linting tests,

https://travis-ci.com/github/pivpn/pivpn/jobs/475625045

PiVPN scripts should pass on shellcheck and this should be later used to evaluate PR quality.

Since it is not Breaking anything in the script, I have added allow_failures for linting stage until this has been closed.

Is your feature request related to a problem? Please describe.

Though https://www.home-assistant.io/ runs on what appears to be Debian, neither deb nor apt are present and all add-on functionality is expected to be done via Home Assistant plugins.

Describe the solution you'd like

It would be great to have Tailscale support as a HassIO plug-in for Home Assistant.

**Describe alte

I think it would be good to describe/list the capture technologies Wireguard is using for each platform. e.g. Windows it using wintun.net driver, Linux it is using /dev/tun etc.

Likely an advanced topic.

Got seemingly invalid client config by these steps:

• Run the script, add client with name example
• Remove WireGuard using script menu
• Run the script again, specified same client name example

The resulting file has.:

[Interface]
...

[Peer]
...
[Interface]
...

[Peer]
...

• make select for language and region (based on tmdb regions/languages)
• use slider for max download size

Is your feature request related to a problem? Please describe.
Hello team.
I have a task to deploy a tiny and cute frontend, which will distribute wg configs for users of our organization. I decided to use your package, because it is 100% suitable.
We use dedicated server as a wg endpoint (VyOS cluster on vrrp), so I don't need to create peers from UI. I am populating config.json by ansible

dsnet has no tests at the moment. I'd really appreciate PRs that add unit tests.