ive been away for a while, some time life just hits and you have stuff to do, large portions of this time went into building filamentdude, as described below. ofcourse just building a data base wasnt enought. so i went overboard building a fully selfhosted control program for my printer.
keep track of your print projects, keep multiple files in one place. a visual overview of al your rolls of filaments, and everytime adjusting the amount of filament manually sucks, so filamentdude connects to your printer and pulls the amount of filament used from the gcode file. and since i have all my files here in one place already, i also build it so it can start the prints on my printer. filamentdude exist out of 4 docker containers. 1 container for the postgress database, 1 container for the backend. the backend contains the apirouters, services and handles the database. than filament dude itself, the front end actually doesnt do a whole lot but host the graphical interface and most importantly contains the services necessary to connect to your printers api. because of security the frontend can only connect to printers on the local network, leaving a gap when hosting externally or outside the network where your printer lives, so there is the last container, a simple agent that acts as gateway between your printers api and filamentdude, so you never have to expose any ports on your local network.
since i hate qr codes and typing in roll codes to find them in the database i build in a function to read and write Ntag stickers. stick a ntag on every new roll put it in the database and everytime you connnect a new roll to your printer, you just scan the tag.
here you will find all three containers, im sorry for the lack of documentation, im working on it, if you want to use it and have question, contact me and il be happy to help. https://hub.docker.com/u/digitdude

everyone here with a 3d printer knows how it goes, you start printing and buying filament, because every roll looks exciting and all the different options just scream to be tried. so slowly i' m collecting a shit ton of filaments rolls of different brands and specifications. sometime for project you find these perfect settings, 2 months later you forgot how you got those perfect ironing settings and have to test all over again.
well i screwed my self over so many times with this, im building filament dude. a locally hosted filament database, which cant track every roll and al those special settings. so you never loose them again.

some things just deserve a special place in my heart, i can tell you html and css aren't those things. fixed the scrolling and centering issues, making everything less awkard, the site i mean not us people.

slowly died fixing the coffeboard. fixed it so every body can see i drink way to much coffee, show every one how caffeinated you are.

to finish up the chatbox, authentication and coffeemachine data. i completely restructered the database to support future updates and flexibility.
also added database rules to prevent unauthorized access.

completely rebuild the login logic of the chatbox/site. now names are protected by password and login.
because i think privacy is still big, login is just a name and password nothing else
with this rework i also will be able to build a leadership board on who drank the most coffee and who put on the most pots of coffee, so look out for that update

grab a cup or put on a pot for everyone, after a while your cup is empty and you can grab a new one

coffee machine is fixed, put up a brew for other visitors when its empty, next up a counter.

trying to get nextcloud online, was not carefull crashed the vm, than crashed the whole server

spent the afternoon fucking around with HTML/CSS. gave up and asked claude to finish up. i feel shame.

fixed the vibe coded piece of shit claude called a chatbox