We currently use external runners (Blacksmith.sh), but that didn't shield us from this as GitHub actions is still the control plane for triggering and monitoring them.
We're now considering Buildkite (apparently they have a GH actions migration tool) or self hosting something (GitLab CI, maybe even Jenkins), as it looks like that would've kept ticking over since we're still seeing webhooks being triggered today during the downtime.
Not quite a comparable alternative. I use Pagefind and it's great for static sites but the search is all client side JS, there's no PHP (or otherwise) client to use it's generated index on the server.
A comparable alternative might be TNTSearch: https://github.com/teamtnt/tntsearch though that requires some (common) PHP extensions to be available, which this library does not require.
Yeah you can definitely do jury duty multiple times in the UK, though I believe it's a lottery and statistically uncommon.
I've ended up doing it twice, within a few years of each other. Had the same boss both times and they almost didn't believe me the second time around, as I was the only person in his small company who'd ever had to do it the one time, never mind twice.
>I know everyone jusy says "build your own!!!11" I used to be like that too I love tech. But sometimes we just want a tool that just plugs in and works, so we can reach our final goal faster.
Same here. I have a couple of boxes running Proxmox in my homelab and I like to tinker, but I also have a DS918+ ticking away with my most important files as I just want something simple that works and is reliable
Half of the "build your own" stuff I've had over the years has at some point broken in some weird and exotic way, requiring a bit more manual upkeep and tweaking than I'd like from a box that is mostly just an SMB share
Slight mitigation to this is you can add an automation via the Shortcuts app to be triggered when airplane mode is enabled, and set the actions to immediately lock your device and disable airplane mode
Downside is that you need to manually disable the automation if you actually wish to use airplane mode (and also remember to re-enable it when done)
Unfortunately I've found the screens on the older ones to be quite fragile (at least the 4th gen)
I went through a phase of buying used 4th gen ones off ebay so that I could have physical buttons to turn the page, but within a couple of months they would always end up up with cracked screens
They would be stored in my bag next to my laptop (and in a case) but at some point I would end up pulling it out to read and find a cracked screen
I think I went through 4 of them before I called it quits, my current paperwhite is still going strong (just no buttons sadly)
Mind sharing your thoughts on other options? I've only been exposed to Tailwind recently and been thinking about utilising a UI component library at some point
> The only exception I have to this is S3. There are so many S3 compatible providers that I don't see any problem with using S3.
I've strongly held this view in the past but after recently being on a project where we trialed using other providers, there's a lot missing compared to the AWS S3 offering that has made me rethink this stance a bit
Permissions being a big one, many providers offer little to no fine grained control. With Digital Ocean for example it's all or nothing, you can only generate access keys that gives full access to all buckets[0]
I have two identical monitors (Lenovo ThinkVision P27h-20) that I can reliably reproduce the random position switching under macOS when waking from sleep
The solution I've come to is to use USB-C with one, and HDMI with the other. This way they both have a unique footprint and macOS keeps them in the correct position. The main downside, I lose use of the USB ports on the one monitor
Had a good experience with RTK Query, lives under redux toolkit but does much more than just reducing the boilerplate for redux which I don't think many people have noticed
I migrated a project to it from react query last year as we liked the react query style hooks and some of its behaviour, but found our usage of react query was getting a bit messy when we started adding dozens and dozens of more endpoints in a large app. Lots of things felt spread out and duplicated, we wanted to centralise things a bit (and simplify the typing) without adding a ton of custom hooks or abstractions
With RTK Query we got to move all the endpoint definitions, cache invalidation behaviour (we had many endpoints that used parameters from many other endpoint responses) and TS definitions to a single place. Also it uses redux underneath so we got the redux tools as well
I'd still use either projects again in the future, just depends on the project
RTK Query felt really good when dealing with a ton of microservices, but maybe overkill if you don't have a ton of endpoints where responses feed into other request parameters
Thanks for this, beyond anything I'll likely ever do myself but a fun read :)
FYI the link to part 3 at the bottom of part 2 [1] seems to be unreachable via mouse. On desktop the element img.terminal_in_demo_with_window is overlapping and blocking the link for me
Potentially the app could link out to a hosted webpage that allows selecting a location using a decent map and search UI, with network capability (but without requiring it in app)
Then on selecting a location you present a button that then jumps you back into the app via a universal link (passing in lon/lat)
Currently in the process of cycling a few thousand passwords myself. Realised I just have to nip away at it a bit each day
Time boxed to about 15 mins a day, it hasn't felt like too much of a burden. But also finding I can just delete quite a few, as my vault is over a decade old and many sites/services are now defunct
Will take another month or so, but have the more recent/crucial ones done already so worst case someone might crack my old digg password
We're now considering Buildkite (apparently they have a GH actions migration tool) or self hosting something (GitLab CI, maybe even Jenkins), as it looks like that would've kept ticking over since we're still seeing webhooks being triggered today during the downtime.