Asides

@gohugoio #GoHugo appears to be releasing updates at a rapid pace lately.

How to make sure that you’re getting the updated file in #PowerQuery, without the browser’s or server’s caching conflict: deuts.org/∞

#BDO now has a new online online banking website, the functionality of which is pretty much like its mobile app –> No Trust Accounts view or transactions (yet?). At least now it seems to accept auto-fill from my favorite password manager.

@reiver @deuts No, I suppose the 5GB are mostly the cached media from my timeline. They actually expire, 7 days I think by default.

@notnorm I use #Pushover for notification, and I have this in the URL: WATCHTOWER_NOTIFICATION_URL: pushover://shoutrrr:apptoken@userkey/?title=Green

I also have SKIP_TITLE set to true: WATCHTOWER_NOTIFICATION_SKIP_TITLE: true

My #GoToSocial instance is now online. Pulled the image 0.18.0-rc2 and now everything seems back to normal:

services:
  gotosocial:
    image: superseriousbusiness/gotosocial:0.18.0-rc2

Here’s the Github issues that explained what happened: github.com/∞

I now got the status back up notification from #UptimeRobot:

Monitor is UP: Deuts One ( deuts.one/∞ ). It was down for 31 hours and 14 minutes.

What did we learn from this experience?

1. Exclude GoToSocial in #Watchtower automatic updates.
2. Stick to explicit version number in your compose.yml file.
3. Time to re-think self-hosting your own Fediverse instance.