drukscode/drukscode-v2
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
drukscode-v2/docs/guide/app-actions/edit-common-config/config-templates.md
OpenCode AI e9899d2e6d
Some checks failed
Android CI Build / check (push) Has been cancelled
Details
Android CI Build / package-apks (push) Has been cancelled
Details
Docs Deploy / build (push) Has been cancelled
Details
Module Market Check / Validate modules/ (push) Has been cancelled
Details
Module Market Publish / Generate submissions.json (push) Has been cancelled
Details
Docs Deploy / deploy (push) Has been cancelled
Details
Initial DruksCode V2: fresh fork of web-to-app (f3b488e) with DruksCode identity 
- Package rename com.webtoapp -> br.com.drukstech.codeapp
- Product rename WebToApp/web-to-app -> DruksCode/drukscode
- Design system Wta* -> Dkc*
- applicationId br.com.drukstech.codeapp (.play for gplay flavor)
- rootProject.name DruksCode
- Fresh git history (upstream kept as remote for sync)
2026-09-12 02:42:02 +02:00

1.5 KiB
Raw Blame History

Config Templates

Save the whole common config as a named template once, then apply it to any app in one tap — so a heavily customized browser setup never has to be re-configured app by app.

Where: the Config Templates button (library icon) in the top bar of the Edit Common Config editor.

What a template contains

A template is a full snapshot of the common config (WebViewConfig) — browser behavior, interface, network, privacy, toolbar and everything else configured in that editor. Applying a template replaces the target app's entire common config with the snapshot: the result is exactly what was saved, never a mix of old and new values. App-type-specific settings (entry files, ports, dependencies) and APK export settings are not part of a template.

Using templates

  • Save as template — snapshots the config currently shown in the editor under a name (1–40 chars). Saving again with the same name overwrites the old snapshot.
  • Apply — tap a template name in the card to replace the current app's common config with it. The change lands in the editor like any manual edit; review and save as usual.
  • Manage templates — rename or delete saved templates.

Notes

  • Templates are stored locally (config_templates.json in app storage) and survive app updates.
  • The in-app Agent can also manage templates: ListConfigTemplates, SaveConfigTemplate, ApplyConfigTemplate, DeleteConfigTemplate.