tftsr-devops_investigation/node_modules/ejs/usage.txt
Shaun Arman 8839075805 feat: initial implementation of TFTSR IT Triage & RCA application
Implements Phases 1-8 of the TFTSR implementation plan.

Rust backend (Tauri 2.x, src-tauri/):
- Multi-provider AI: OpenAI-compatible, Anthropic, Gemini, Mistral, Ollama
- PII detection engine: 11 regex patterns with overlap resolution
- SQLCipher AES-256 encrypted database with 10 versioned migrations
- 28 Tauri IPC commands for triage, analysis, document, and system ops
- Ollama: hardware probe, model recommendations, pull/delete with events
- RCA and blameless post-mortem Markdown document generators
- PDF export via printpdf
- Audit log: SHA-256 hash of every external data send
- Integration stubs for Confluence, ServiceNow, Azure DevOps (v0.2)

Frontend (React 18 + TypeScript + Vite, src/):
- 9 pages: full triage workflow NewIssue→LogUpload→Triage→Resolution→RCA→Postmortem→History+Settings
- 7 components: ChatWindow, TriageProgress, PiiDiffViewer, DocEditor, HardwareReport, ModelSelector, UI primitives
- 3 Zustand stores: session, settings (persisted), history
- Type-safe tauriCommands.ts matching Rust backend types exactly
- 8 IT domain system prompts (Linux, Windows, Network, K8s, DB, Virt, HW, Obs)

DevOps:
- .woodpecker/test.yml: rustfmt, clippy, cargo test, tsc, vitest on every push
- .woodpecker/release.yml: linux/amd64 + linux/arm64 builds, Gogs release upload

Verified:
- cargo check: zero errors
- tsc --noEmit: zero errors
- vitest run: 13/13 unit tests passing

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
2026-03-14 22:36:25 -05:00

25 lines
1.6 KiB
Plaintext

EJS Embedded JavaScript templates
{Usage}: ejs [options ...] template-file [data variables ...]
{Options}:
-o, --output-file FILE Write the rendered output to FILE rather than stdout.
-f, --data-file FILE Must be JSON-formatted. Use parsed input from FILE as data for rendering.
-i, --data-input STRING Must be JSON-formatted and URI-encoded. Use parsed input from STRING as data for rendering.
-m, --delimiter CHARACTER Use CHARACTER with angle brackets for open/close (defaults to %).
-p, --open-delimiter CHARACTER Use CHARACTER instead of left angle bracket to open.
-c, --close-delimiter CHARACTER Use CHARACTER instead of right angle bracket to close.
-s, --strict When set to `true`, generated function is in strict mode
-n --no-with Use 'locals' object for vars rather than using `with` (implies --strict).
-l --locals-name Name to use for the object storing local variables when not using `with`.
-w --rm-whitespace Remove all safe-to-remove whitespace, including leading and trailing whitespace.
-d --debug Outputs generated function body
-h, --help Display this help message.
-V/v, --version Display the EJS version.
{Examples}:
ejs -m $ ./test/fixtures/user.ejs -f ./user_data.json
ejs -m $ ./test/fixtures/user.ejs name=Lerxst
ejs -p [ -c ] ./template_file.ejs -o ./output.html
ejs -n -l _ ./some_template.ejs -f ./data_file.json
ejs -w ./template_with_whitspace.ejs -o ./output_file.html