Shipped this project!
added lots of things!
- ai processing (specify how many copies u want, color or just white and black? YOU decide)
- store files in R2
- Better reviewing system
- logs/timeline
- other little things :)
added lots of things!
Log in to leave a comment
WOW! It’s been a long time.
I added a few things, such as:
And… that’s it for now :)
Log in to leave a comment
As you can see per the previous devlogs, i implemented a new dashboard and authentication system, where you are able to see what you sent to the printer.
I really liked how it turned out, but there’s still lots of room for improvement. It was really challenging debugging Cloudflare routing emails, since they are a bit annoying. :)
I implemented a new system that allows you to see your print jobs in the Brick Dashboard. You can see if your job is approved, pending, or rejected.
There’s also print credits! Print credits are the cost for your print. If you have enough print credits, your job will go trough automatically. If you don’t, it will then go to a pending state that an admin can either approve or reject.
Log in to leave a comment
I built an automation worker that receives emails from my printer’s email ([email protected]) and prints its files in my printer. I’m happy that it finally worked. I’m not proud of the CF worker amp vibecoding, but i guess failure is a way to learn more :)
Hi hi! Wow, first devlog has nearly 10h lol. What i did here is basically set up the project, and made the functionality that prints files whenever i send them to my printer’s email!
In this time, i also did a lot of trial and error with Amp for the Cloudflare Worker. I ended up removing in it a commit (you can find at https://github.com/afonsoingles/brick-core/commit/162f415fc240b1d63ae05d6d8ffc6ab5e04fa6f8) since it didn’t work properly.
Below are some pictures of the errors that the printer gives when you didn’t send any files and a message for when you are not authorized to print.