6 Commits

Include renames

Author	SHA1	Message	Date
maeneko	a358504e2a	Bump to Beta 0.2.1 ... Covers all six places the version is written down: .env, the copy install.sh keeps because it prints its banner and builds the release URL before the archive with .env exists, the three package.json files, and the /ui/brand example in the README.	2026-09-10 00:24:18 +03:00
maeneko	602c0416ba	Move panel name and version into .env, bump to Beta 0.2.0 ... The product name, the channel word "Alpha" and the version were scattered across install.sh, the CLI banner, two spots in App.tsx and three package.json files, so a rename or a bump meant editing strings in code. They now live in one committed .env at the project root (BRAND, CHANNEL, VERSION), shipped inside the release archive and read at runtime: the CLI loads it after cli.env — so real env and machine settings still win — and injects the three values into awg-ui, which serves them from GET /ui/brand for the wordmark. awg-ui also parses the same file directly, so `npm run server` in dev shows what production shows. install.sh keeps its own VERSION and CHANNEL and says why: it prints the banner and builds the release URL before the archive holding .env has been downloaded. It writes BRAND into cli.env only when the operator passed one explicitly, so the file stays the single source otherwise. Version bumped to Beta 0.2.0 across .env, install.sh and the three package.json files.	2026-08-29 03:08:51 +03:00
maeneko	b097ccd5fb	Bump version to 0.1.4.2 ... Ships the AWG_GEN/AWG_PIN installer switches and module-version surfacing from the previous commit.	2026-08-25 15:00:59 +03:00
maeneko	6fdacd71c3	Fix 3.1 rollout on servers with an older loaded module and UFW ... Three defects surfaced on a real upgrade from 2.0. The module gate read modinfo, which reports the version on disk. apt --only-upgrade rebuilds the DKMS module but does not replace the one already loaded, so the installer wrote a 3.1 conf that the running 2.0 module rejected with 'Unable to modify interface: Invalid argument'. It now compares /sys/module/amneziawg/version, reloads the module when it lags behind the disk, and decides the generation from the loaded version only. Bringing the interface up is the only real proof the kernel accepted the 3.1 parameters, so a failure there no longer aborts the install: it enables dynamic debug, retries, prints the amneziawg lines from dmesg, then strips the 3.x keys and comes up on 2.0. The rejected conf is kept as awg1.conf.awg31. PostUp appends 'iptables -A FORWARD', but UFW inserts its jumps at the head of the chain, so client traffic was dropped with '[UFW BLOCK] IN=awg1 OUT=eth0' — the tunnel connected and had no internet. When UFW is active the installer now adds 'ufw route allow in on awg1 out on eth0' and opens the AWG and UI ports. Version 0.1.4.1.	2026-08-17 18:48:38 +03:00
maeneko	01d8524f8c	Bump version to 0.1.4 ... install.sh drives the release URL and tarball name off VERSION, so the matching tag is v0.1.4. awg-ctrl/package.json was still on the default 1.0.0 and is now in step with cli and awg-ui.	2026-08-17 18:01:35 +03:00
maeneko	54ffcf9bc0	Initial commit	2026-07-10 00:19:05 +03:00