docs: print file routing - #326
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughThis PR adds documentation for FDM Monster’s print file routing: a new guide describing watched-folder and slicer-comment routing, environment variables to configure watched folders, a Docker+Samba example, and a sidebar entry to surface the page. ChangesPrint File Routing Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related issues
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint skipped: no ESLint configuration detected in root package.json. To enable, add Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/configuration/environment_variables.mdx`:
- Line 72: The description for WATCHED_FOLDER_POLLING is too broad; update the
table text for the `WATCHED_FOLDER_POLLING` variable to scope polling as
required only for Docker Desktop bind mounts and network shares (or adjust to
mirror the routing guide's exact matrix), and clarify that local Linux Docker
setups and local disks may support native events and can set polling to `false`;
modify the single-line table entry accordingly to avoid stating "required for
Docker bind mounts" generically.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 0c39b3de-e1e5-4f43-bae1-3c2e9a1cbfe2
📒 Files selected for processing (3)
docs/configuration/environment_variables.mdxdocs/software_usage/print_file_routing.mdxsidebars.ts
Part of fdm-monster/fdm-monster#5290.
New Software usage → Print File Routing page: how routing works, the watched folder (
by-printer//by-tag/, consume vs library, polling), thefdmm_targetslicer tokens, what happens when a file matches more than one printer, and a deployment-examples section (incl. a Samba-share docker-compose for slicing from a separate PC).Also adds the
WATCHED_FOLDER_*variables to the Environment Variables reference, plus a sidebar entry.Documentation: Print File Routing Guide
Added a new user-facing guide explaining how FDM Monster automatically routes sliced files to the correct printer or printer group. Highlights:
This should make it easier for users to set up distributed or multi‑printer workflows and networked slicing.