Neal Wilson ✅ @neal@social.typica.us

The last time I did a project that hooked into a third party API that speaks JSON I used rapidjson to pull data out of the responses. This time around I'm just shoving the responses into a jsonb column in PostgreSQL and querying that. There are benefits to either approach. Mostly I just wanted to try something different and having 1 fewer dependency to track isn't a bad thing.

Tomorrow I have the online run through with my station instructors for the next class I'm teaching so I need to go through the class materials and make sure that's all ready to go tonight. I've taught this class a few times before so it's mostly things like putting in the current sponsors.

Didn't make much progress on the web store today, but I have the start of an employee facing page with info on a given order: What box to use, what to put in the box, where the box is getting shipped to, if the customer has been charged (and if not a so far non-functional button to charge the customer). Also need to add the shipping label generation stuff and sending the customer an email with their receipt and tracking number, but after work I need to switch to a different project.

Knocked out the next page after dinner. The next one is somewhat complex, probably won't get that done tonight.

Cat didn't greet me at the door today. Was too busy sitting on the couch.

I was hoping to have the shop able to take online orders by today but unless I'm unusually productive after dinner that's not happening. The customer facing stuff (aside from product pages) is done but I have a little more work to do on the staff facing side of things and on product pages that don't look awful (I have one thrown together just for functionality testing).

The afternoon has been a little slow so now I have an orders summary page that shows how much of each coffee is on some pending order. The use case is that whoever is roasting coffee can run that report and include that information in their roasting schedule instead of needing to tally up individual orders. Next up is the per-order packing/taking the money/generating a shipping label stuff.

PostgreSQL supports up through 31 which would cause a login attempt to take about 1.5 days to process on the current server. I'll probably want to re-evaluate this on server upgrades to keep that time reasonably steady.

crypt-bf/14 seems about right for hash algorithm speed. It takes my server about 1s to process a login attempt with that.

Staff access authentication code written and tested as working.

My mouth is on fire. I love it.

Time for a giant bowl of super spicy stir fry.

Visited Dad's cat after work.

While the web shop won't have accounts for customers (at least at first, I'm willing to reconsider if people really want that), it looks like I do want to have a login/accounts for staff because otherwise I need to give a bunch of people on staff ssh access to the server (nobody wants that) or I need to leave the back end stuff needed for order processing open to the public (which is relatively safe for the level of access I'm exposing but still seems like a bad idea).

Unfortunately while working on that I failed to realize that I was running out of time with adequate staff for me to grab a lunch so I'm pretending that an orange cream smoothie is food.