Custom templates (#594)

* allow custom mail templates (#533)

* allow to override embedded frontend (#533)

docs/documentation/configuration/overview.md

@@ -74,6 +74,7 @@ mail:
   from: Wireguard Portal <noreply@wireguard.local>
   link_only: false
   allow_peer_email: false
+  templates_path: ""
 
 auth:
   oidc: []
@@ -96,6 +97,7 @@ web:
   expose_host_info: false
   cert_file: ""
   key_File: ""
+  frontend_filepath: ""
 
 webhook:
   url: ""
@@ -485,6 +487,11 @@ To send emails to all peers that have a valid email-address as user-identifier,
   If false, and the peer has no valid user record linked, emails will not be sent.
   If a peer has linked a valid user, the email address is always taken from the user record.
 
+### `templates_path`
+- **Default:** *(empty)*
+- **Environment Variable:** `WG_PORTAL_MAIL_TEMPLATES_PATH`
+- **Description:** Path to the email template files that override embedded templates. Check [usage documentation](../usage/mail-templates.md) for an example.`
+
 ---
 
 ## Auth
@@ -841,6 +848,14 @@ Without a valid `external_url`, the login process may fail due to CSRF protectio
 - **Environment Variable:** `WG_PORTAL_WEB_KEY_FILE`
 - **Description:** (Optional) Path to the TLS certificate key file.
 
+### `frontend_filepath`
+- **Default:** *(empty)*
+- **Environment Variable:** `WG_PORTAL_WEB_FRONTEND_FILEPATH`
+- **Description:** Optional base directory from which the web frontend is served. Check out the [building](../getting-started/sources.md) documentation for more information on how to compile the frontend assets.
+  - If the directory contains at least one file (recursively), these files are served at `/app`, overriding the embedded frontend assets.
+  - If the directory is empty or does not exist on startup, the embedded frontend is copied into this directory automatically and then served.
+  - If left empty, the embedded frontend is served and no files are written to disk.
+
 ---
 
 ## Webhook

docs/documentation/usage/mail-templates.md

@@ -0,0 +1,49 @@
+WireGuard Portal sends emails when you share a configuration with a user. 
+By default, the application uses embedded templates. You can fully customize these emails by pointing the Portal 
+to a folder containing your own templates. If the folder is empty on startup, the default embedded templates 
+are written there to get you started.
+
+## Configuration
+
+To enable custom templates, set the `mail.templates_path` option in the application configuration file 
+or the `WG_PORTAL_MAIL_TEMPLATES_PATH` environment variable to a valid folder path.
+
+For example:
+
+```yaml
+mail:
+  # ... other mail options ...
+  # Path where custom email templates (.gotpl and .gohtml) are stored.
+  # If the directory is empty on startup, the default embedded templates
+  # will be written there so you can modify them.
+  # Leave empty to use embedded templates only.
+  templates_path: "/opt/wg-portal/mail-templates"
+```
+
+## Template files and names
+
+The system expects the following template names. Place files with these names in your `templates_path` to override the defaults.
+You do not need to override all templates, only the ones you want to customize should be present.
+
+- Text templates (`.gotpl`):
+  - `mail_with_link.gotpl`
+  - `mail_with_attachment.gotpl`
+- HTML templates (`.gohtml`):
+  - `mail_with_link.gohtml`
+  - `mail_with_attachment.gohtml`
+
+Both [text](https://pkg.go.dev/text/template) and [HTML templates](https://pkg.go.dev/html/template) are standard Go 
+templates and receive the following data fields, depending on the email type:
+
+- Common fields:
+  - `PortalUrl` (string) - external URL of the Portal
+  - `PortalName` (string) - site title/company name
+  - `User` (*domain.User) - the recipient user (may be partially populated when sending to a peer email)
+- Link email (`mail_with_link.*`):
+  - `Link` (string) - the download link
+- Attachment email (`mail_with_attachment.*`):
+  - `ConfigFileName` (string) - filename of the attached WireGuard config
+  - `QrcodePngName` (string) - CID content-id of the embedded QR code image
+
+Tip: You can inspect the embedded templates in the repository under [`internal/app/mail/tpl_files/`](https://github.com/h44z/wg-portal/tree/master/internal/app/mail/tpl_files) for reference. 
+When the directory at `templates_path` is empty, these files are copied to your folder so you can edit them in place.