rename: provider and stunnel templates to resources/templates/ (#143 stage 1) #182
Loading…
Reference in a new issue
No description provided.
Delete branch "template-rename"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
resources/ mixes templates and configs under config-ish names (#143): the per-type OpenVPN base templates ship as
Airvpn_configetc., and the stunnel template asssl_config, next to actual defaults likefirewall_default.json.Fix
Stage 1 of #143 — the cheap rename:
resources/Airvpn_config(+ Mullvad/ProtonVPN/Windscribe) →resources/templates/{Type}.ovpnresources/ssl_config→resources/templates/stunnel.conf/usr/share/aqomui/templates/update.pycopy_certs seed path,tunnel.pystunnel reads (×2),setup.pydata_files, PKGBUILD install block (theresources/*_configglob is gone)SUPPORTED_PROVIDERSentry must ship atemplates/{Type}.ovpn, so a future provider can't be added registry-only and fail at first importStage 2 (stripping the embedded per-install
auth-user-pass/capaths, injecting them at seed time) stays open on #143, gated on the multi-entry work — and the ProtonVPN template shouldn't be over-invested in before #33 settles.The
{provider}_configdict key in the gui's apply_edit is untouched on purpose: the service ignores it for supported providers (always writes{provider}/openvpn.conf), so it's a D-Bus dict key, not a filename.Verification
ruff check --select E9,F63,F7,F82 .clean; 435 tests pass (434 + the new template guard)packaging/arch/build-branch-and-install.sh, then a provider re-import (copy_certs seeds openvpn.conf from the new path) — the stunnel path only fires on Airvpn/Windscribe SSL connections🤖 Generated with Claude Code
Airvpn_config and friends read as configs but are per-type OpenVPN base templates (blank proto/remote filled in by write_config, seeded once into {entry}/openvpn.conf by copy_certs), and ssl_config is the stunnel template tunnel.py rewrites per connection. Name them what they are and give them their own directory; actual defaults (firewall_default.json) stay in the resources/ root. Installed location moves with them: /usr/share/aqomui/templates/. Stage 1 of #143 -- stripping the embedded per-install paths out of the templates waits for the multi-entry work. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>