both mobile and desktop have the plaintext notes in a sqlite db. they’re “easy enough” to export if you’re bailing on the app, but not to regularly switch between two different apps

Are you using PersistentVolumes? If your storage class supports it, looks like there’s a volume snapshot concept you can use, have you looked into that?

Not sure what you’re doing, but if we’re talking about a bog standard service backed by a db, I don’t think having automated reverts of that data is the best idea. you might lose something! That said, triggering a snapshot of your db as a step before deployment is a pretty reasonable idea.

Reverting a service back to a previous version should be straightforward enough, and any dedicated ci/cd tool should have an API to get you information from the last successful deploy, whether that is the actual artifact you’re deploying, or a reference to a registry.

As you’re probably entirely unsurprised by, there are a ton of ways to skin this cat. you might consider investing in preventative measures, testing your data migration in a lower environment, splitting out db change commits from service logic commits, doing some sort of blue/green or canary deployment.

I get fairly nerd-sniped when it comes to build pipelines so happy to talk more concretely if you’d like to provide some more details!

The two factors at an ATM are possession of your bank card + knowledge of your pin. (it also takes your photo, for good measure)

GitHub will happily accept a smart card or whatever, if an extra plastic rectangle jives with you more than an OTP generator.

Your two factors shift to possession of your password vault + knowledge of the password to it. You’re okay IMO.

You also still get the anti-replay benefits of the OTPs, though that might be a bit moot with TLS everywhere.

Be careful, if you get a .pizza, you are only legally allowed to spend the donations on pizza.

just to give you the term to search for, these types of applications are called snippet managers. for example, https://snibox.github.io/

there’s a ton of them around. I don’t have a particular one that I recommend, since it’s not something I use in my workflow.

yep. they’re still here. they got smaller, and we call them “tracking pixels” now.

it’s just an image, which, server side, you can count the number of times it got loaded. easy to embed and no js required.

That’s interesting, okay. Is svn doing compression of those binaries for you?

Not to say “you’re holding it wrong”, but I’m curious about your workflow here. You clone these binaries every time you come back to a project?

I don’t get it, who in their right mind hosts development stuff on a Windows clunker?

Same question, but Subversion. Switch to git. Import your repos with git-svn.

Hey, thanks for that, I appreciate you sharing your list.

One option you can consider with fairmail and gmail is to use an “app password” to authenticate to IMAP, instead of oauth. That might work better when backing up with neo backup?

That’s an interesting suggestion, thanks! I might wind up trying that for android auto + google voice 🤔

Hmm, thanks for the suggestion… this looks like it might be mainly for only pixel devices? Or devices that have a LineageOS build? I might be frustrated enough with the problem to learn Nix, but I don’t want to be limited to particular hardware.

I don’t have a particular guide at the tip of my fingers, but I can share some recommendations based on my experience:

• prefer a phone with USB-c if you plan on connecting USB things to it. the otg adapters for micro-b are kinda hit and miss when it comes to keeping the phone connected to power as well.
• look out for clearances of those carrier locked prepaid phones from physical stores, you can get nice devices for nearly nothing
• whatever you’re running on the phone, make sure it starts at startup, so you don’t need to go launching everything if you reboot for some reason
• if the phone is"mission critical" e.g. random restart while in the middle of a print is unacceptable, turn off all the automatic updates and such.
• a VNC server has been helpful, to remotely poke at the phone if I’m too lazy to go do it physically
• get something that’ll keep the screen off the phone on. I’ve encountered reduced performance regardless of what battery optimizations I’ve turned off without doing that but YMMV depending on ROM.

I fully expect the screen thing and the batteries bring in there constantly charging to kill the phones I’m using eventually, but it’s something I expect and accept. my octoprint phones have been fine so far, for a bit over a year 🤷‍♂️

The value proposition of old or used android phones as SBCs is insane! You’ve probably got some in your drawers, or can at worst buy some carrier locked ones for 30$. You get a device with better compute than a raspberry pi, with a screen, cameras, speakers, flashlight and battery attached!

Personally, I use them to run and monitor my 3d printers.

Why do you need to back up that server data? The great thing about joplin, is that the full content of your notes (and history) is distributed, like a git repo. As long as you have one device left with your notes, everything else can be bootstrapped from there. If your sync server burns down, start a new one and sync your notes to it again.

I’ve been very happy with roku tvs at home and a roku stick “to-go”. Very simple interface with minimal ads that you can block.