[Question] External database?

[taker218]

I just saw this plugin and since the FilamentManager plugin seems to be abandoned, I wanted to take a look.

Since I have multiple printers and use the spools on all of them I have an external database for my spools. So is it planned to support an external database for storage?
In FilamentManager you could use a postgres database to store your data.

Otherwise I may need to stick to the FilamentManager for now.

[OllisGit]

This is not planed right now. I will put your request to my Backlog: https://github.com/OllisGit/OctoPrint-SpoolManager/projects/1

First thoughts:

• I think support for an existing database with a fixed scheme is maybe not possible
• Switching to an other database like mysql, postgresql were the plugin assign the database-scheme will work
• There will be a CSV Importer/Exporter function, maybe this is a solution

Or do you have other ideas to integrate an external database?

fyi: Currently I finished my other Plugin "PrintJobHistory" and I will "ramp up" my activities into the Spoolmanager

[taker218]

I don't think that you need to support an existing database.
The FilamentManager connected to an existing database server, but used a seperate database to store the data.

I think this could be a feature a lot of people would like to have. For me it would be a make-or-break feature to switch to this plugin.

I think yours could be a lot better then the old one, but I really dig the possibility to use the same database for all printers right now.

[stale]

This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.

[JohnSh3p4rd]

I am also interested in a external database.

In my case, I use two printers with two OctoPrint setups, but they both use the same filament spools. Therefore it would be nice if the filament is being tracked in an external database, where both printers have access (maybe one hosts the database and the second is just a client?), or the database may be synced between the raspberry pis (don't know if this is a solid solution, just an idea).

[portcqb]

Would it be possible even using the included database to have multiple octoprint instances on the same PI use the same database if that would be easier than using and external database solution.

[fredrikbaberg]

Just saw this plugin today, so I haven't tried it yet, but I'd also like support for external database. I'm currently using FilamentManager, where data is stored in a Postgres database on another machine. That way I know the data is safe even if my OctoPrint install breaks (which happens sometimes since I'm doing some development on the same device).

I wouldn't mind if InfluxDB was supported since I already use that for another purpose, but since I setup Postgres only for FilamentManager I think most database solutions would be OK.

[OllisGit]

fyi:I am start implementing a solution for my PrintJobHistory-Plugin. After finishing, I can copy this feature to this plugin.

The status and how it is implemented is documented in my wiki: https://github.com/OllisGit/OctoPrint-PrintJobHistory/wiki/Roadmap-to-an-external-Database

[derekslenk]

Awesome. An external database for this plugin would be a game changer. Do you have a tip jar to fund certain features ?

[edrft99]

I second the tip jar! This is a big feature I am looking for.