Security

Control which programs fugo runs, which environment variables templates may read and which URLs get_remote may fetch.

Templates and themes are code. [security] limits what they can reach.

config.toml
[security]
  enableInlineShortcodes = false
  [security.exec]
    allow = ["^(dart-)?sass(-embedded)?$", "^go$", "^git$", "^npx$"]
  [security.funcs]
    getenv = ["^FUGO_", "^CI$"]
  [security.http]
    methods = ["(?i)GET|POST"]
    urls = [".*"]

config.yaml
security:
  enableInlineShortcodes: false
  exec:
    allow:
    - ^(dart-)?sass(-embedded)?$
    - ^go$
    - ^git$
    - ^npx$
  funcs:
    getenv:
    - ^FUGO_
    - ^CI$
  http:
    methods:
    - (?i)GET|POST
    urls:
    - .*

config.json
{
   "security": {
      "enableInlineShortcodes": false,
      "exec": {
         "allow": [
            "^(dart-)?sass(-embedded)?$",
            "^go$",
            "^git$",
            "^npx$"
         ]
      },
      "funcs": {
         "getenv": [
            "^FUGO_",
            "^CI$"
         ]
      },
      "http": {
         "methods": [
            "(?i)GET|POST"
         ],
         "urls": [
            ".*"
         ]
      }
   }
}

exec.allow, exec.osEnv: The programs fugo may run, and the environment variables they get (by default PATH, HOME, the proxy settings and a few more). fugo runs only git, for enableGitInfo.
funcs.getenv: Environment variables the get_env function may read. The names a project’s .env file defines are always readable.
http.urls, http.methods, http.mediaTypes: What get_remote may fetch.
enableInlineShortcodes: Allow shortcodes defined inside content files.

A blocked action is an error that names the setting to change.