mirror of
https://github.com/Donkie/Spoolman.git
synced 2026-10-21 17:42:16 -05:00
Donkie
e09d63b443
Most of the world writes 1,75 rather than 1.75, and `<input type="number">` only accepts the separator the browser locale dictates: everything else it reports as an empty value. A user typing a comma therefore watched a weight or a diameter silently come out blank or, once the separator was dropped, a hundred times too large. The same input type also accepts "e", "+" and "-" anywhere in the text, since they are legal exponent syntax, and then reports the whole value as empty too, so "1e" read back as nothing at all. Numeric fields are now text inputs with `inputmode="decimal"`, guarded by a shared `numericInput` action that filters at the keystroke: both separators go in, letters cannot, and a pasted "12,5 g" is cleaned rather than refused. Reading is centralised in `parseDecimal`, which takes either separator and returns null instead of NaN for text that is not a number, so an unset field stays distinguishable from a real 0. What the parent, and the API, receive is always canonical. The typed separator stays on screen: each field keeps a draft of the text and gives it up only when the value moves somewhere that text no longer means, so storing 1.5 does not rewrite a typed "1,5" between keystrokes. Arrow-key stepping, which was native to the old input type, is now the component's own. Covers the spool/filament/vendor inspectors, the add-spool modal (whose price box was a bare text input accepting anything at all), extra fields of every numeric type, the extra-field editor's order box and the low-stock threshold.
Keep track of your inventory of 3D-printer filament spools.
Spoolman is a self-hosted web service designed to help you efficiently manage your 3D printer filament spools and monitor their usage. It acts as a centralized database that seamlessly integrates with popular 3D printing software like OctoPrint and Klipper/Moonraker. When connected, it automatically updates spool weights as printing progresses, giving you real-time insights into filament usage.
Features
- Filament Management: Keep comprehensive records of filament types, manufacturers, and individual spools.
- API Integration: The REST API allows easy integration with other software, facilitating automated workflows and data exchange.
- Real-Time Updates: Stay informed with live spool updates through Websockets, providing immediate feedback during printing operations.
- Central Filament Database: A community-supported database of manufacturers and filaments simplify adding new spools to your inventory. Contribute by heading to SpoolmanDB.
- Web-Based Client: Spoolman includes a built-in web client that lets you manage data effortlessly:
- View, create, edit, and delete filament data.
- Search, group and filter your inventory by manufacturer, material, location and more.
- Add custom fields to tailor information to your specific needs.
- Design and print labels with QR codes for easy spool identification and tracking.
- Contribute to its translation into 18 languages via Weblate.
- Database Support: SQLite, PostgreSQL, MySQL, and CockroachDB.
- Multi-Printer Management: Handles spool updates from several printers simultaneously.
- Advanced Monitoring: Integrate with Prometheus for detailed historical analysis of filament usage, helping you track and optimize your printing processes. See the Wiki for instructions on how to set it up.
Spoolman integrates with:
- Moonraker and most front-ends (Fluidd, KlipperScreen, Mainsail, ...)
- OctoPrint
- OctoEverywhere
- Home Assistant
- MCP Server - Manage your filament inventory through AI assistants like Claude using the Model Context Protocol
Web client preview:
 |
 |
| Dashboard — spools as cards, grouped by location or any other field. Drag one to move it. | Label designer — QR labels built from any spool, filament or vendor field. |
Installation
Please see the Installation page on the Wiki for details how to install Spoolman.
If the new client misbehaves on your setup, set SPOOLMAN_LEGACY_CLIENT=TRUE to go back to
the previous one. Both ship in every release and talk to the same API, so your data is
untouched either way — but please report the problem
so it can be fixed.