Closed justinclift closed 5 months ago
@MKleusberg FYI. :smile:
This isn't deployed yet. I'll probably do it Thursday, as I have other (unrelated) stuff I need to do tomorrow instead.
@MKleusberg @chrisjlocke This has been deployed to production now. Actually, everything right up to the latest commit as of right now (7f5821270a77bd38e279527731dc40f034599604) is now live. :smile:
@MKleusberg The "Usage" page is throwing an error (in production) when the user doesn't have usage data to display:
Would you be ok to take a look at that? I'm pretty sure it'll be a simple fix, but I'm so desperately in need of sleep that I'd better not try it. :wink:
And the dark mode stuff? I see a blog post in the making... ;)
Yeah, it's in there too. I'll take a look at that error above in a few hours.
Looks like using coalesce()
in the ApiUsageData()
function should fix the problem. A fix with that is just running through the Cypress tests on my local pc now. If it passes, I'll push that to the master
branch then deploy it to our infrastructure.
Yep, that worked. The fix is now added to our master
branch, and has been deployed to production.
Awesome :+1:
As we're looking to use a dedicated Memcached server shared between our backend systems, we'll be passing traffic over the wire for that environment.
This PR adds the code needed for using TLS with memcached. It's only needed in production though.
Note that this requires memcached to be configured with TLS. On our current Ubuntu 20.04 LTS servers, it needs this added to their
/etc/memcached.conf
file:The
SERVER_FQDN
piece needs updating for each individual server in question. :wink:Take special note of the
fullchain.pem
file name there. Don't usecert.pem
instead, otherwise you'll get errors when the client doesn't want to connect to the TLS server ("Unknown Authority").