Possible suggestion(s) for small additions/enhancements

[LuboGD]

Hello, first thank you for making this tool, it does a great job of automating wireguard configuration!

There a still a few steps which are explained well on/in the README.md web page/file, but still done manually.

I put together 3 very simple shell scripts to automate those 3 steps: (the files are named briefly but descriptive of their function)

1. install-easy-wg-quick-prerequisites-debian.txt (this corresponds to sudo apt install plus all the packages you list as prerequisites, and automates it)
2. clear-easy-wg-quick-configuration.txt (this corresponds to the -c command line switch, and automates it)
3. deploy-updated-wghub.conf.txt

(this corresponds to the command lines shown below, and automates them)

Important: Deploy updated wghub.conf configuration to WireGuard with wg-quick:
sudo wg-quick down ./wghub.conf # if already configured
sudo wg-quick up ./wghub.conf
sudo wg show # to check status

I'm attaching the shell script files, which like the original script should have execute permissions
install-easy-wg-quick-prerequisites-debian.txt
clear-easy-wg-quick-configuration.txt
deploy-updated-wghub.conf.txt

Thank you for your creation, and I hope you will seriously consider adding these to the project, I think this makes the tool even easier to use.

[burghardt]

Thank you for your feedback and for sharing your scripts! I really appreciate the effort you've put into improving the usability of easy-wg-quick and sharing your thoughts. Here are mine:

1. Dependency installation: While I agree that simplifying dependency installation is valuable, automating it directly in the script is out of scope because the process is highly OS dependent. Different systems have unique package managers and versions that may require special handling. I have documented what needs to be installed in README.md, but this is quickly outdated (e.g. on FreeBSD).
2. Delete configuration: Removing configurations programmatically seems risky and could have unintended consequences. Instead, the script supports the -c or --clear parameter, which prints out an exact list of file extensions that you can manually remove to safely start over.
3. Updating the runtime configuration: Handling runtime configurations programmatically is both OS-specific and error-prone, especially in scenarios involving remote systems over tunnels. The script provides clear instructions on what steps to take, but gives users the flexibility to perform these updates in the way they prefer (e.g. wg-quick, systemd, rc scripts, etc.).

This report is an excellent example of how to extend and use the script, but it doesn't fit the scope of a bug report or PR. I will move it to the Discussions section so that others can benefit from your showcase and possibly collaborate further.

Thanks again for sharing your ideas and scripts - they provide valuable insight into how the tool is being used!