jacob.ogden/internal/: wireguard-spoke-agent-0.1.2 metadata and description
Keeps a Windows WireGuard spoke's tunnel installed, current with wireguard-hub's releases, and running
| description_content_type | text/markdown |
| metadata_version | 2.3 |
| requires_dist |
|
| requires_python | >=3.14 |
| File | Tox results | History |
|---|---|---|
wireguard_spoke_agent-0.1.2-py3-none-any.whl
|
|
|
wireguard_spoke_agent-0.1.2.tar.gz
|
|
wireguard-spoke-agent
Keeps a Windows WireGuard spoke's tunnel installed, current with wireguard-hub's releases, and running. It only manages the WireGuard service. Each spoke installs it its own way (for example camera-footage-fs's installer).
On the PC
Everything lives in C:\ProgramData\wireguard-spoke-agent\ (SYSTEM and Administrators only):
settings.env:WG_PEER_NAME,PERSISTED_DIR_LOC, and the optionalPINGKEY/HEARTBEAT_SLUG/ALERTS_HEALTHCHECK_PING_URL/ALERTS_PUSHOVER_TOKEN/ALERTS_PUSHOVER_USER_KEY. Loaded into the agent's own environment before aeth-ext is imported. Until aeth-ext treats a missingALERTS_EMAIL_PWDas "email off", it must also holdALERTS_EMAIL_PWD=unusedandALERTS_RECIPIENTS=[]. The second line stops any SMTP login with the placeholder.<peer>.key: the peer's WireGuard private key.<peer>.confis the filled-in conf the tunnel service was installed from.uv\,python\,tools\,bin\,cache\: uv and the agent's uv-managed install.run.cmdand the scheduled taskwireguard-spoke-agent(SYSTEM, at boot and every 5 minutes) are rendered from this package's templates and kept in sync by the agent.state.json: the last applied hub tag, the task template hash, and any pending--pythonmove.logs\:agent.logandupgrade.log.
What a run does is in the module docstring of src/wireguard_spoke_agent/__main__.py.