Splitting it

[FlohEinstein]

Found your project, very promising, almost what I need. But it contains your management interface and Wireguard in the same container. Had a quick look at the sourcecode if I could easily split it, but it doesn't look that way. I'd like to run the management in a different container, maybe even a different machine.

So this is a feature request, probably quite a big one:

• two images/containers that don't have to run on the same machine
• the management interface container can run without special docker privileges, on a secure machine, possibly even only on-demand
• the wireguard container runs in network mode host, provides the wireguard connectivity and a port where the management interface connects to
• some kind of security feature should secure the management port, best would be LDAP_ADMIN_GROUP

Let me know what you think

[h44z]

This application is designed to be as simple to setup and use as possible. A user should be able to easily run a single binary which provides the whole configuration UI and functionality.

Splitting up the WireGuard configuration part does not only include separating the WireGuard API calls but also separating configuration file management and network interface management into a separate binary.

In terms of security I fully support your request, it would be really good if the portal code does not run with administrative rights.

Currently I don't have the time to implement such a big feature, but I will keep it in the backlog!