RE:
Thanks for testing it Jan! My "Windows" box is a small NUC so took all day (8.5 hrs in total) to compile PrusaSlicer from source. I'll spend today debugging your issue because I'm curious why it's not working for you. I'll create a new version instead of overwriting the existing one once it's fixed. Stay tuned.
No problem! Take your time. Maybe it's my fault. I'll try again from the beginning 😉
I got it working in Windows 11 with FilamentDB running in Docker and PrusaSlicer running a local executable. The changes I make to a filament in PrusaSlicer automatically updates the filament in the DB. I'll go from the beginning and update the installation instructions for Windows. So far what I did:
I've scratched out my username and token and replaced here with so just substitute yours.
docker run -d -p 3000:3000 -e MONGODB_URI="mongodb://:@ac-jcusmzf-shard-00-00.szg2imn.mongodb.net:27017,ac-jcusmzf-shard-00-01.szg2imn.mongodb.net:27017,ac-jcusmzf-shard-00-02.szg2imn.mongodb.net:27017/filament-db?ssl=true&authSource=admin&replicaSet=atlas-m3fwaw-shard-0&appName=Filaments" ghcr.io/hyiger/filament-db:latest
Then just pull up http://localhost:3000 in a browser. It should come up. PrusaSlicer connected to it and I was able to pull in and edit my filaments
As a test I changed 9.0 to 9.5:
RE: PrusaSlicer 2.9.4 - Filament Edition (A complete filament workflow)
When I try to start the AppImage for your PrusaSlicer I get the following error:
I checked and the package gvfs which contains this library is installed in version 1.6
I can pull your github and create a local build to see if that works. I have built the current version of PS on my system before so I know that this could take while for a complete build. I'll report back ...
RE: PrusaSlicer 2.9.4 - Filament Edition (A complete filament workflow)
When I try to start the AppImage for your PrusaSlicer I get the following error:
I checked and the package gvfs which contains this library is installed in version 1.6
I can pull your github and create a local build to see if that works. I have built the current version of PS on my system before so I know that this could take while for a complete build. I'll report back ...
Is your Debian setup ARM or x64 (intel/amd)? I can setup debian distro on a VM and test it.
RE: PrusaSlicer 2.9.4 - Filament Edition (A complete filament workflow)
I'm sorry, Hyiger. I can't get it to work.
I uninstalled everything again—both the Filament Database and PrusaSlicer 0.0.8. I also cleared my Chrome browser data. Them i reinstall all new files again.
I suspect something is still going wrong in the Docker program. Because when I load the address “ http://localhost:3000” there, Filament DB V1.5.0 appears instead of V1.6.0.I also can't create filaments there; that only works in the program.
Mods for Core One: Core One HT 450 degrees, Comfortable display , Very fast print start and Reducing noises
Mods for Prusa XL: Very fast print start
RE:
I'm sorry, Hyiger. I can't get it to work.
I uninstalled everything again—both the Filament Database and PrusaSlicer 0.0.8. I also cleared my Chrome browser data. Them i reinstall all new files again.
I suspect something is still going wrong in the Docker program. Because when I load the address “ http://localhost:3000” there, Filament DB V1.5.0 appears instead of V1.6.0.I also can't create filaments there; that only works in the program.
I've been replacing the versions a lot rather than creating new ones so the 1.5.0 is now quite "old" I don't think the 1.5.0 version has the PrusaSlicer REST endpoints. Can you try this? Otherwise, try the stand-alone installer: https://github.com/hyiger/filament-db/releases/tag/v1.6.0
docker stop $(docker ps -q) docker system prune --all docker run -d -p 3000:3000 -e MONGODB_URI="mongodb://uname:[email protected]:27017,ac-jcusmzf-shard-00-01.szg2imn.mongodb.net:27017,ac-jcusmzf-shard-00-02.szg2imn.mongodb.net:27017/filament-db?ssl=true&authSource=admin&replicaSet=atlas-m3fwaw-shard-0&appName=Filaments" ghcr.io/hyiger/filament-db:latest # replace uname and passwd with yours
RE: PrusaSlicer 2.9.4 - Filament Edition (A complete filament workflow)
I am on amd64 platform.
RE: PrusaSlicer 2.9.4 - Filament Edition (A complete filament workflow)
The build of the deps just completed, on to the main build now.
RE: PrusaSlicer 2.9.4 - Filament Edition (A complete filament workflow)
I'm sorry, Hyiger. I can't get it to work.
I uninstalled everything again—both the Filament Database and PrusaSlicer 0.0.8. I also cleared my Chrome browser data. Them i reinstall all new files again.
I suspect something is still going wrong in the Docker program. Because when I load the address “ http://localhost:3000” there, Filament DB V1.5.0 appears instead of V1.6.0.I also can't create filaments there; that only works in the program.
Ah.... I think I know what is wrong. The dev version (built from source) uses port 3000 but the release version uses 3456. If you are running from docker 3000 should still be OK but if you are connecting to the installed version the URL should be http://localhost:3456. Please use this in the PrusaSlicer configuration
RE: PrusaSlicer 2.9.4 - Filament Edition (A complete filament workflow)
I am on amd64 platform.
I'll install an AMD64 debian distro and test it.
RE: PrusaSlicer 2.9.4 - Filament Edition (A complete filament workflow)
I'm creating new versions of both PrusaSlicer and Filament DB to force the ports on both to be 3456 instead of 3000 for dev (local build) and 3456 for release. That should clear up a lot of the confusion.
RE: PrusaSlicer 2.9.4 - Filament Edition (A complete filament workflow)
Ah, I tried this on my W11 VM and I can connect to the webservice with Firefox. But when I try to import my config bundle from PrusaSlicer it gives me a network error. I removed the insecure bit from the file in Windows after copying it from my linux host. But that did not change anything.
The filament DB interface in Firefox shows a green "connected" badge. I guess that is a good thing? 🙂
RE:
Ah, I tried this on my W11 VM and I can connect to the webservice with Firefox. But when I try to import my config bundle from PrusaSlicer it gives me a network error. I removed the insecure bit from the file in Windows after copying it from my linux host. But that did not change anything.
The filament DB interface in Firefox shows a green "connected" badge. I guess that is a good thing? 🙂
"Connected" means it's connected to the MongoDB Atlas. I'm in the process now of refining the Windows installation and setup. I haven't used Windows in a very long time (I'm a MacOS/Linux guy). So at the moment, I'm doing a clean install on Windows 11 and will update the tutorial and installation guide to make this easier.
RE: PrusaSlicer 2.9.4 - Filament Edition (A complete filament workflow)
The build on my linux system failed. During the build I saw a lot of purple warnings and it seems to me that this was more that I had on my last build of the Prusa version of PS.
make[1]: [CMakeFiles/Makefile2:1924: src/slic3r/CMakeFiles/libslic3r_gui.dir/all] Fehler 2
make: [Makefile:146: all] Fehler 2
RE: PrusaSlicer 2.9.4 - Filament Edition (A complete filament workflow)
Can you try this? Otherwise, try the stand-alone installer: https://github.com/hyiger/filament-db/releases/tag/v1.6.0
That's exactly what I did. So far, I've only used the EXE file.
docker stop $(docker ps -q) docker system prune --all docker run -d -p 3000:3000 -e MONGODB_URI="mongodb://uname:[email protected]:27017,ac-jcusmzf-shard-00-01.szg2imn.mongodb.net:27017,ac-jcusmzf-shard-00-02.szg2imn.mongodb.net:27017/filament-db?ssl=true&authSource=admin&replicaSet=atlas-m3fwaw-shard-0&appName=Filaments" ghcr.io/hyiger/filament-db:latest # replace uname and passwd with yours
That was the result:
PS C:\Users\jan**L> docker stop $(docker ps -q)
16af1d6df9a9
PS C:\Users\jan**L> docker system prune --all
WARNING! This will remove:
- all stopped containers
- all networks not used by at least one container
- all images without at least one container associated to them
- all build cache
Are you sure you want to continue? [y/N] y
Deleted Containers:
16af1d6df9a9121d67f04eddc35b71e97e5ed8b94a396d66214f93e332496c6c
bb510c31f9aa596e3f59fbea6db73bdc134cdef79a1dabcf4f66d69990c6e6ba
92a087c22da7779a51ac6b4631bd51745f4ebc47db6093c9d83c23cfbf8d29f5
7b7e2baff9fb5920a00d33bc6b6d8e7a11654b017d29de6c80e0d11bc67b5954
ffd8b47154870486d9c5a77e8bdfd496854e4d2b43d48b6366162d12353ccb40
590aa29d79d3f4bc2167cfb4eb935b3ffd501a211a8e70d80bf2affc2afb8b24
ee7154ed6998e370e24774ec0d3ba22dba5b9afcfd44c2e33ad5308cc23f60b7
15d5637b8cac6f4f5e1c44499e055f6132e646b3412d46c0c11ba9f411572d46
442566072dbec2e2bc9d572e2761a4453425ab5c3a52f95ce5b956ccaa40077e
f2e52768ea76c943b99cbd6d65e0c46fdbc8c7881f97720a7ef337500a6dfca0
Deleted Images:
untagged: ghcr.io/hyiger/filament-db:latest
deleted: sha256:8f09cd75627f24b3f1032182896edf6233052350eafdc2774bb6efa52fbf99c0
deleted: sha256:c0576388286ec92bddd917fd7b9786f509290ad3cc0782c6492db52e63e13e14
deleted: sha256:c496b6ff8458e603ecde3be853f40ef9b4880e2006cce65116553d0fd6072c80
Total reclaimed space: 70.44MB
PS C:\Users\ja*s> docker run -d -p 3000:3000 -e MONGODB_URI="mongodb://jan*L:***LL**@ac-jcusmzf-shard-00-00.szg2imn.mongodb.net:27017,ac-jcusmzf-shard-00-01.szg2imn.mongodb.net:27017,ac-jcusmzf-shard-00-02.szg2imn.mongodb.net:27017/filament-db?ssl=true&authSource=admin&replicaSet=atlas-m3fwaw-shard-0&appName=Filaments" ghcr.io/hyiger/filament-db:latest
Unable to find image 'ghcr.io/hyiger/filament-db:latest' locally
latest: Pulling from hyiger/filament-db
docker: failed to copy: httpReadSeeker: failed open: failed to do request: Get "https://pkg-containers.githubusercontent.com/ghcr1/blobs/sha256:e725de0246035ae916f51f02dd8d6c63f8423ab7aa9848559a5c7b475d6e45ec?se=2026-04-04T20%3A15%3A00Z&sig=VtoKDg2cnm6%2Fo9iD9htrBRkIVrdtij884lZhiTpdu1o%3D&ske=2026-04-05T13%3A27%3A14Z&skoid=fb3d2a07-ec6c-4fe4-aced-9efe0fd2fe1a&sks=b&skt=2026-04-04T13%3A27%3A14Z&sktid=398a6654-997b-47e9-b12b-9515b896b4de&skv=2025-01-05&sp=r&spr=https&sr=b&sv=2025-01-05&hmac=46d119878acddb8e7c882a0e7e412a89d93ca72f359e0f8301d884355473a18f": EOF
Run 'docker run --help' for more information
Mods for Core One: Core One HT 450 degrees, Comfortable display , Very fast print start and Reducing noises
Mods for Prusa XL: Very fast print start
RE: PrusaSlicer 2.9.4 - Filament Edition (A complete filament workflow)
The build on my linux system failed. During the build I saw a lot of purple warnings and it seems to me that this was more that I had on my last build of the Prusa version of PS.
make[1]: [CMakeFiles/Makefile2:1924: src/slic3r/CMakeFiles/libslic3r_gui.dir/all] Fehler 2 make: [Makefile:146: all] Fehler 2
I'm in the process of getting a Debian distro setup. I'll run through the installer and see what it going on.
RE:
Can you try this? Otherwise, try the stand-alone installer: https://github.com/hyiger/filament-db/releases/tag/v1.6.0
That's exactly what I did. So far, I've only used the EXE file.
That was the result:
Ooof. OK. I'm in the process of doing a rebuild so it probably deleted the image from the repo. I'll have a look. Could you try running the installer instead? And then try to connect with localhost:3456. If you see a message about the web server crashing, delete %APPDATA%\filament-db\config.json then run again
RE: PrusaSlicer 2.9.4 - Filament Edition (A complete filament workflow)
OK. I have Windows self-installers working. After installing the Filament DB, try to open http://localhost:3456 in a browser, it should pull up a web-page. Please note that it will take approx 10 minutes to install (for me at least) since it is not signed and so Windows does a very thorough scan. Next install PrusaSlicer then go into config settings and set the Filament DB URL to http://localhost:3456. Restart PrusaSlicer and it should pick up your filaments
Here is what I will test next:
- Running Filament DB in Docker on Windows
- Installing and running on a Debian and Ubuntu distribution
FilamentDB-1.7.0-windows-x64-setup.exe
PrusaSlicer-PrusaSlicer-2.9.4-Calibration-0.0.9-win64-setup.exe
RE:
Docker is working correctly, make sure to map the ports correctly the command is (note the mapping of 3456 to 3000 (internal port inside the container) and remember to replace user:password with your own.
docker run -d -p 3456:3000 -e MONGODB_URI="mongodb://user:[email protected]:27017,ac-jcusmzf-shard-00-01.szg2imn.mongodb.net:27017,ac-jcusmzf-shard-00-02.szg2imn.mongodb.net:27017/filament-db?ssl=true&authSource=admin&replicaSet=atlas-m3fwaw-shard-0&appName=Filaments" ghcr.io/hyiger/filament-db:latest
RE:
A quick note, the Windows installer takes a VERY long time > 20 minutes. There are thousands of node.js modules and Windows Defender has to scan every one of them. I'm trying to work out a way to make this faster.
Alternatively you can download the zip file, unzip and run in-place rather than do a full install.
If you see a dialog box popup on startup with a Javascript error that means there is a stale version of standalone MongoDB. Just kill it and restart. Same if you see a "Webserver failed to start" I'm looking into how to clean this up correctly.
Also, please always grab the latest releases. The current one for Filament DB is 1.7.1
RE:
With regard to the long install time on Windows, I'm also on a 1.4ghz 16gb 4-core NUC so it's probably WAY slower than yours.