• 1 Post
  • 14 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle

  • 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!










  • 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 🤷‍♂️



  • 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.