Skip Navigation

User banner

Admiral Patrick

@ ptz @dubvee.org

Posts
227
Comments
1895
Joined
3 yr. ago

I learned to play the guitar growing up as a young rapscallion in Mississippi. But things didn't really take off until I moved to Memphis. There I met the Colonel and the hits just kept coming. Unfortunately, the fame went to my head, I gained a lot of weight, started wearing a white jumpsuit, and ate tranquilizers like they were trail mix. Then, in 1977, I died on the toilet.

Or did I?


I also develop Tesseract UI for Lemmy/Sublinks

  • Like so many other shows, it's on my watch list. Just haven't gotten down to it yet.

  • Siskel & Ebert give the film no thumbs up: "Not even worth pirating to watch ironically".

  • What show are these based on? I feel like I need to watch it.

    Edit: Brooklyn Nine-nine?

  • That's probably the next wheel some overzealous Rust dev will reinvent.

  • I also run (well, ran) a local registry. It ended up being more trouble than it was worth.

    Would you have to docker load them all when rebuilding a host?

    Only if you want to ensure you bring the replacement stack back up with the exact same version of everything or need to bring it up while you're offline. I'm bad about using the :latest tag so this is my way of version-controlling. I've had things break (cough Authelia cough) when I moved it to another server and it pulled a newer image that had breaking config changes.

    For me, it's about having everything I need on hand in order to quickly move a service or restore it from a backup. It also depends on what your needs are and the challenges you are trying to overcome. i.e. When I started doing this style of deployment, I had slow, unreliable, ad heavily data-capped internet. Even if my connection was up, pulling a bunch of images was time consuming and ate away at my measly satellite internet data cap. Having the ability to rebuild stuff offline was a hard requirement when I started doing things this way. That's now no longer a limitation, but I like the way this works so have stuck with it.

    Everything a service (or stack of services) needs is all in my deploy directory which looks like this:

     
        
    /apps/{app_name}/
        docker-compose.yml
        .env
        build/
            Dockerfile
            {build assets}
        data/
            {app_name}
            {app2_name}  # If there are multiple applications in the stack
            ...
        conf/                   # If separate from the app data
            {app_name}
            {app2_name}
            ...
        images/
            {app_name}-{tag}-{arch}.tar.gz
            {app2_name}-{tag}-{arch}.tar.gz
    
      

    When I run backups, I tar.gz the whole base {app_name} folder which includes the deploy file, data, config, and dumps of its services images and pipe that over SSH to my backup server (rsync also works for this). The only ones I do differently are ones with in-stack databases that need a consistent snapshot.

    When I pull new images to update the stack, I move the old images and docker save the now current ones. The old images get deleted after the update is considered successful (so usually within 3-5 days).

    A local registry would work, but you would have to re-tag all of the pre-made images to your registry (e.g. docker tag library/nginx docker.example.com/nginx) in order to push them to it. That makes updates more involved and was a frequent cause of me running 2+ year old versions of some images.

    Plus, you'd need the registry server and any infrastructure it needs such as DNS, file server, reverse proxy, etc before you could bootstrap anything else. Or if you're deploying your stack to a different environment outside your own, then your registry server might not be available.

    Bottom line is I am a big fan of using Docker to make my complex stacks easy to port around, backup, and restore. There's many ways to do that, but this is what works best for me.

  • Yep. I've got a bunch of apps that work offline, so I back up the currently deployed version of the image in case of hardware or other failure that requires me to re-deploy it. I also have quite a few custom-built images that take a while to build, so having a backup of the built image is convenient.

    I structure my Docker-based apps into dedicated folders with all of their config and data directories inside a main container directory so everything is kept together. I also make an images directory which holds backup dumps of the images for the stack.

    • Backup: docker save {image}:{tag} | gzip -9 > ./images/{image}-{tag}-{arch}.tar.gz
    • Restore docker load < ./images/{image}-{tag}-{arch}.tar.gz

    It will backup/restore with the image and tag used during the save step. The load step will accept a gzipped tar so you don't even need to decompress it first. My older stuff doesn't have the architecture in the filename but I've started adding that lately now that I have a mix of amd64 and arm64.

  • I use the web version rather than the app, but I want to say the app can store the library on the SD card if you have one of sufficient size lying around and if the Redmi has the slot for one. But as someone else said, there are smaller versions you can download if you can't fit the full one.

    Not trying to push Kiwix on you, but I just can't emphasize enough how handy it is to have offline Wikipedia always on hand.

    • Termux has lots of possibilities
    • Pair it with a Meshtastic node and make it a dedicated communicator
    • I run HomeAssistant and Emby and have several old smartphones to work with, so one lives in each room and act as remotes for those
    • Setup Asterisk and make a VoIP system using old smartphones and SIP clients as handsets
    • Check if PostmarketOS supports it. I haven't used it, but it basically turns your phone into a Linux machine if I understand correctly
    • Use it as your "ugh, I have to use an app for [THIS]?!" phone. Basically things that require an app for setup or one-off apps you can't avoid using.
    • Make your own little portable Library of Alexandria. Install Kiwix and download a bunch of ZIMs from their library. If you've got at least 130 GB to work with, you can even fit the entire Wikipedia dump with images and have that locally.

  • Deleted

    Permanently Deleted

    Jump
  • If she had simply resigned from her position when she began experiencing health issues, it would have allowed her successor to be nominated and approved under a democratic administration.

    There's no guarantee that would have happened. See Mitch McConnell and Merrick Garland

  • Deleted

    Permanently Deleted

    Jump
  • Deleted

    Permanently Deleted

    Jump
  • Deleted

    Permanently Deleted

    Jump
  • I realize you're probably not serious, but, still, voter disenfranchisement is both a slippery slope and a tactic employed by those everyone calls fascists. Two wrongs do not make a right and all that.

  • I've used SA for over 10 years and am happy with it. It's a bit of a pain to get set up and set to train, but otherwise still works well for me.

    I've also heard good things about rspamd but I still haven't even tried it out yet.

  • TenForward: Where Every Vulcan Knows Your Name @lemmy.world

    Tinker Tenor Doctor Spice Girl

  • TenForward: Where Every Vulcan Knows Your Name @lemmy.world

    Follow up to my previous post....

  • TenForward: Where Every Vulcan Knows Your Name @lemmy.world

    me_irl / Cheers! 🍻

  • TenForward: Where Every Vulcan Knows Your Name @lemmy.world

    A True Story of Unintended Consequences

  • TenForward: Where Every Vulcan Knows Your Name @lemmy.world

    🎵 Damn it feels good to be a gangsta🎵

  • TenForward: Where Every Vulcan Knows Your Name @lemmy.world

    This is why you don't get promoted, Harry. You install recursive functions without specifying exit conditions.

  • Science Memes @mander.xyz

    Virtual Particles

  • Not The Onion @lemmy.world

    Permanently Deleted

    www.thedailybeast.com /marjorie-taylor-greene-is-now-adding-lasers-to-her-hurricane-helene-conspiracy
  • politics @lemmy.world

    Trump Promises 'Very Large Faucet' Will Funnel Water from Oregon to Los Angeles

    gizmodo.com /trump-promises-very-large-faucet-will-funnel-water-from-oregon-to-los-angeles-2000504652
  • TenForward: Where Every Vulcan Knows Your Name @lemmy.world

    It's them got dang vidya games, I tell ya whut.

  • TenForward: Where Every Vulcan Knows Your Name @lemmy.world

    At least buy me a drink first, mon time capitaine.

  • TenForward: Where Every Vulcan Knows Your Name @lemmy.world

    Oops!

  • TenForward: Where Every Vulcan Knows Your Name @lemmy.world

    "Don't you judge me. Do you know how hard it is to cook for this family? Not very, but I can't handle much."

  • TenForward: Where Every Vulcan Knows Your Name @lemmy.world

    Voyager takes a wrong wormhole at Albuquerque: Part 2

  • TenForward: Where Every Vulcan Knows Your Name @lemmy.world

    Voyager takes a wrong wormhole at Albuquerque

  • TenForward: Where Every Vulcan Knows Your Name @lemmy.world

    Just paint the old prop grey and turn it on its side. No one will notice.

  • TenForward: Where Every Vulcan Knows Your Name @lemmy.world

    I respect when spirit guides are kind of jerks

  • TenForward: Where Every Vulcan Knows Your Name @lemmy.world

    (Beep boop) Please clarify parameters

  • TenForward: Where Every Vulcan Knows Your Name @lemmy.world

    Appreciation Post

  • Linux @programming.dev

    20 years later, real-time Linux makes it to the kernel - really

    www.zdnet.com /article/20-years-later-real-time-linux-makes-it-to-the-kernel-really/