Every time I see @goat 'a avi my body has a very confused mixed response of "aw cute" and "oh shit what's she up to this time" and it's very fun every time 10/10
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.
Oracle shipped nine security fixes to curl yesterday: https://linux.oracle.com/errata/ELSA-2019-1880.html - fixes we announced in **2016**. We've announced several more problems after that for the version they ship...
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.
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).
<< Data was stolen from an Amazon Web Services-based storage bucket, which included more than 140,000 Social Security numbers >>
How about all of these 'data breach!!! data was taken OUT OF THE CLOUD!!!!' articles instead start with
"Data was PUT INTO Amazon Web Services, which is a sketchy private company with an extremely bad reputation owned by the world's richest man who is currently being blackmailed and who many Amazon users hope, against all the evidence, isn't a literal Bond Villain.."
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.
Author of Typica software for coffee roasters.