This is a properly cursed country selector!
There's just so many little details that make me go, "huh?"
Remote
Mike Coats 🏴🇪🇺🌍♻️
@mike@mikecoats.social
mastodon 4.7.2An unending tinkerer of all things hardware and software.
Views & posts are my own. Re-posts not endorsements.
Profile photo: Evelyn/OSHWA
393 Followers
440 Following
17 Posts
Joined May 14, 2022
Location:
Inverness, Scotland
Website:
Codeberg:
My latest blog post: Keeping it old school, Unix style, with inetd services!
https://mikecoats.com/simple-inetd-services/
How to build quick and dirty network services, the Unixy, way with the venerable inetd approach.
@revk@toot.me.uk Got this through just this morning.
Tindie’s new owners are EETree LLC out of Washington State, represented by Gongyu Su.
@neil@mastodon.neilzone.co.uk I do something similar at work for an *.internal domain system that needs secure certs, and I've written up a simplified version of it here,
https://mikecoats.com/trusted-certificates-private-servers-part-1/
Looking forward to your write-up!
Replying to
@Edent@mastodon.social 100% this. I’ve deleted the apps (both, still) and nuked my account as fully as I could manage and I’ve left Matrix behind.
I can’t believe it, but IRC is still a better chat experience than Matrix and it’s basically got the same UX it’s had since the 90s. Even on mobile, I’d still rather use IRC.
@_thegeoff@mastodon.social “ooh, cheese baguette!” is still a part of our household vocabulary.
@jonty@chaos.social @Floppy@mastodon.me.uk Hey, as the Head of Technology for a NDPB, let me know if you want to add one more to your collection?! :D
@tek@freeradical.zone That’s amazing! Truly. Well played.
@Wrewdison@masto.hackers.town WannaKnowHowIGotTheseScars.gif
Replying to
@stargirl@hachyderm.io Sorry (sincerely)!
Replying to
@LaF0rge I’m sure you’ll have had plenty of replies already, but I’d be happy to lend a hand with this project.
Replying to
@thisismissem@hachyderm.io @renchap@oisaur.com @andypiper@macaw.social
4.2.0 - 4.2.2 will no longer install as a gem has been yanked.
4.2.3 has a change in node versions to be aware of on an old server, but the instructions for 4.2.0 can be followed on 4.2.3 to get the DB migrations in place.
4.2.4 has a change in ruby versions to be aware of, but once that's fixed you're fine.
4.2.5 - 4.2.15 all install without error.
Replying to
@thisismissem@hachyderm.io @renchap@oisaur.com @andypiper@macaw.social I went the long, but more easy to troubleshoot, route and cross-graded 4.1.22 to 4.2.0 and went upwards version by version from there. I've probably blacklisted my server's IP with rubygems, but I got there!
Replying to
@andypiper@macaw.social are there any good documents that detail how to upgrade between 2 versions? The GitHub release notes are usually pretty decent about going up within a version, ie 4.1.x to 4.1.y, but I think I’ve missed the instructions for going from 4.1.x up to 4.2.x and 4.3. x.
Is it just read everything, take copious backups and try everything?
@pwaring@social.xk7.net Thanks for sharing. I’m in a similar situation, so having a recommendation for a secondary provider is really helpful.
@Edent@mastodon.social Hadestown is brilliant! I’ve a bootleg Billy Bragg cover of Why We Build The Wall that I recorded when he last toured up this way.
@ianm@c.im You got further than me, then!