type: epic 🤣

type: epic 🤣

Not the adjective but the noun is meant here¹ 🤣

Insane Progress 🎉

Database is completely usable
Cidr Support implemented
All Env Vars are now configurable through the Database
Many Features (like Allowed IPs or Persistent Keepalive) already supported through the database

Anybody who wants to try the new features already and give feedback can use the development tag

What about WG_PATH and PORT envs ? Because some users (like me xD) need to configure them at startup.

What about WG_PATH and PORT envs ? Because some users (like me xD) need to configure them at startup.

Port still works.
I'll add WG_PATH back in

We should add an Advanced Section for Variables like these as they require manual config to the run command or docker compose file. Or it has to stay a env var as this only makes sense before the database is created

Port still works. I'll add WG_PATH back in

Updated the Documentation in feat-ui, WG_PATH remains a Env Var

Noticed @tailwindcss/forms is installed but not activated inside the tailwind.config.ts 🤔

Good Progress yet again.
IPv6 Supported fully
Even more configurable through the database

Waiting now on @tetuaoro to update the ui.
Waiting on feedback on #1353 to implement permission system.

Backend (other than routes) is mostly done

@tetuaoro any update?

A Dynamic Copyright year would be nice, so when it's 2025
2021-2024 become 2021-2025 automated.
I know how to do this on Astro.

Something like:?

const year = new Date().getFullYear()
2021 - {year}

This will be the right one: https://stackoverflow.com/questions/57191154/how-to-show-current-year-in-vue-project

A Dynamic Copyright year would be nice, so when it's 2025
2021-2024 become 2021-2025 automated.

Yes can do that. But doesn't make much sense imo. The software as it was released than only has copyright upto then + it conveys the users that the software is more recent than It actually is

IPv6 (Dual Stack) is now more or less forced.
If Client only supports IPv4/IPv6 there is no problem as you can simply use IPv4/IPv6 Address for the Endpoint (or use a Domain with A and AAAA record)
If Server doesn't support IPv4/IPv6 there could be problems with DNS

• Should be tested on IPv4/IPv6-only server
  • IPv6-only can easily be tested using https://www.euserv.com/de/vserver/root-vserver/v2/vs2-free.php
  • IPv4-only could easily be tested by disabling IPv6? (best would be a server with no IPv6 from the start)

That Peers have IPv6 Addresses shouldn't be a problem as these are only local (should be supported everywhere?)
If problems arise on IPv4/IPv6-only servers there should be the option to disable IPv6 (maybe mutually exclusive IPv4)

Maybe we should replace crc32 with https://www.npmjs.com/package/js-xxhash
or just check if the one-time-code is already used.
mainly for users with large number of peers

Omg, long pull request so)
Maybe, you can to add API? I just need control clients with Ansible, and I don't have time for this feature

Omg, long pull request so)

?

Maybe, you can to add API?

?

I just need control clients with Ansible, and I don't have time for this feature

You can control clients with the API already. You would have to reverse engineer it tho as there is no documentation. This just adds a lot of features and rewrites the whole UI as stated in the description

You can control clients with the API already. You would have to reverse engineer it tho as there is no documentation. This just adds a lot of features and rewrites the whole UI as stated in the description

I need something like this (inside docker): docker compose exec wg-easy wg client create clientname # get ip, keys, docker compose exec wg-easy wg client delete clientname. You have it?

I need something like this (inside docker): docker compose exec wg-easy wg client create clientname # get ip, keys, docker compose exec wg-easy wg client delete clientname. You have it?

Unfortunately, this feature is not currently supported and there are no plans to implement it in the future. The primary purpose of wg-easy is its user interface. If you require terminal-based functionality, this project might not be the best fit for your needs.

I need something like this (inside docker): docker compose exec wg-easy wg client create clientname # get ip, keys, docker compose exec wg-easy wg client delete clientname. You have it?

I see this: https://github.com/wg-easy/wg-easy/blob/master/src/lib/WireGuard.js
If you want, I can add CLI for current version

I see this: https://github.com/wg-easy/wg-easy/blob/master/src/lib/WireGuard.js If you want, I can add CLI for current version

I appreciate your suggestion and the effort you’re willing to put in. However, I believe it’s best to wait for the current pull request to be completed, even though it might take some time.

While your help is highly valued, I don’t think adding a CLI fits the goals of this project at the moment. It could introduce additional maintenance burdens that we’re not prepared to handle right now.

(Would also be fundamentally incompatible with Nuxtnuxt/nuxt#29386; you could maybe write a shell Wrapper for the API?)

@pheiduck What are your opinions?

you could maybe write a shell Wrapper for the API?)

Sorry, I just need cli now)

With the expected IPv6 support, is it possible to enable and disable IPv6 on a per-user basis?

With the expected IPv6 support, is it possible to enable and disable IPv6 on a per-user basis?

Not as of now. Could be added if demand is high. I don't see a valid reason for it tho

when might this be completed, and is this semi-stable to use?

@qvipin I hope by the end of the year. No