Activity

Afonso

Shipped this project!

Hours: 28.66
Cookies: 🍪 60
Multiplier: 7.39 cookies/hr

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 :)
Afonso
  • Added the ability to download/preview files
  • Actually print files in the printer
Attachment
0
Afonso

WOW! It’s been a long time.
I added a few things, such as:

  • I use AI now to determine the user’s name and email! It turns out that every provider sends it differently, and that caused many problems.
  • With AI processing, you can now say “print this in black and white, not using colors” or “print this 5 times”! Your print job will now follow these instructions.
  • Logs! Logs! Logs! Be able to see what, was done by who and when on your print job!
  • Files are now stored in R2! I previously analyzed files… without seeing them! Their content was obviously stored, but in MongoDB. That didn’t allow me to preview them, and it took lots of time to load. Making a switch to R2 was very cool and challenging.
  • Approve/Reject or set pending! You decide! - Admins can now change their decision after making their first one.

And… that’s it for now :)

Attachment
0
Afonso

Shipped this project!

Hours: 10.24
Cookies: 🍪 96
Multiplier: 9.33 cookies/hr

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. :)

Afonso

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.

Commits

Attachment
0
Afonso

Hi! I implemented an authentication system, that in the future will allow you to see your print jobs/other printer-related things. You are able to login via email OTP or password.
Below is an example of what a user model looks like!

Commits

Attachment
0
Afonso

Shipped this project!

Hours: 9.93
Cookies: 🍪 153
Multiplier: 15.42 cookies/hr

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 :)

Afonso

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.

Attachment
Attachment
1

Comments

kashsuks
kashsuks 2 months ago

really cool project! modern day fax

Afonso

Adding admin key routes

Attachment
0
Afonso

Started up the project and made the database connection work!

Attachment
0