dano-operations

Operations workspace with thin wrappers that delegate tooling to dano-tools.

Principle

• Keep automation logic in dano-tools.
• Keep dano-operations focused on operational content and execution entry points.
• Resolve tools path via:
  1. DANO_TOOLS_HOME
  2. sibling fallback ../dano-tools

Included wrappers

• scripts/convert.sh -> dano-tools/scripts/convert.sh
• scripts/flyer.sh -> dano-tools/toolkits/flyers/scripts/flyer.sh

Prerequisites

• dano-tools available via DANO_TOOLS_HOME or as sibling folder (../dano-tools)
• recommended for team use: running remote document service via DANO_CONVERT_API_URL
• recommended for team use: DANO_CONVERT_API_KEY if service auth is enabled

With the remote service configured, the team does not need local Pandoc, XeLaTeX, or Python knowledge for normal document conversion.

Quick usage

# Convert file
bash scripts/convert.sh /path/to/file.md PDF eisvogel

# Run flyer generator (interactive)
bash scripts/flyer.sh

# Convert via remote service (recommended once Synology service is up)
export DANO_CONVERT_API_URL=http://<host>:8000
export DANO_CONVERT_API_KEY=<api-key>
bash scripts/convert.sh /path/to/file.md PDF eisvogel

Recommended team entrypoint in dano-tools:

bash ../dano-tools/scripts/menu.sh

Convenience wrapper in this repo:

bash scripts/menu.sh

Recommended team setup:

cp ../dano-tools/.dano-tools.local.env.example ../dano-tools/.dano-tools.local.env

Then fill in the real remote URL and API key once. The dano-tools scripts load that file automatically.

VS Code tasks

Tasks are available in .vscode/tasks.json.

Synology/Portainer stack files

See dano-tools/deploy/portainer/:

• stack-short-term-latex.yml (Pandoc + XeLaTeX + Eisvogel)
• stack-mid-term-hybrid.yml (latex baseline + optional CSS renderer)