docs: align output flow with single-job process
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Output Pipeline Overview
|
||||
|
||||
This directory contains the post-processing side of ResumeCustomizer. It is responsible for taking job-targeted Markdown resumes produced elsewhere in the system and turning them into printable DOCX/PDF artifacts.
|
||||
This directory contains the post-processing side of ResumeCustomizer. It is responsible for taking a job-targeted Markdown resume produced elsewhere in the system and turning it into printable DOCX/PDF artifacts.
|
||||
|
||||
## Directory Layout
|
||||
- `ForRelease/inbox`: drop a single `*.md` file here to trigger conversion.
|
||||
@@ -20,7 +20,7 @@ cd output/Docker
|
||||
The script detects either the Docker Compose plugin or the legacy `docker-compose` binary and forwards any additional arguments you supply (`down`, `logs`, etc.). The stack registers under the project name `RCEO-AI-ResumeCustomizer-Output`, and the primary container is `RCEO-AI-ResumeCustomizer-Output-Processor`.
|
||||
|
||||
## What the Watcher Does
|
||||
1. Polls `ForRelease/inbox` every few seconds for Markdown files.
|
||||
1. Polls `ForRelease/inbox` every few seconds for a single Markdown resume.
|
||||
2. Runs Pandoc using the shared DOCX and LaTeX templates to generate DOCX/PDF.
|
||||
3. Drops the exports into the timestamped folder under `ForRelease/outbox`.
|
||||
4. Moves the original Markdown into the matching timestamp folder under `ForRelease/processed`.
|
||||
|
||||
Reference in New Issue
Block a user