• 0 Posts
  • 300 Comments
Joined 2 years ago
cake
Cake day: July 18th, 2023

help-circle



  • So I ended up reading up on the original comics because I knew they were a bit darker than the cartoons. It seems shredder is only in volume 1 of 4. In it he’s basically a New York Yakuza boss that kills splinters master. So splinter trains the turtles to kill shredder. After that he does get resurrected once, but after that he stays dead.

    Volume 2 cover a full on battle with DARPA (for experimenting on aliens and turtles), Volume 3 has a possible daughter of shredder trying to get revenge, but volume 4 retcons volume 3 and focuses on a future where aliens come to earth and the turtles can roam the streets as “aliens” (which isn’t that weird for the series as aliens first appear in volume 1).

    So, yeah, it gets kinda weird.




  • jacksilver@lemmy.worldtoSelfhosted@lemmy.worldgoodbye plex
    link
    fedilink
    English
    arrow-up
    2
    ·
    12 days ago

    Looks like there is a config and cache location in their docker scripts. The easiest way to make a docker application portable is to bind mount the config and cache. That way you have access to the actual files and could copy them to your windows partition.

    If you’re already using a volume for that data, I think it becomes a bit trickier. I know technically you can move or copy volumes, but I’ve never tried. Although you could still bind mount a random directory and still copy the files out.






  • jacksilver@lemmy.worldtoSelfhosted@lemmy.worldDocker Backup Stratagy
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    17 days ago

    Yep, bind mount the data and config directories and back those up. You can test a backup by spinning up a new container with the data/config directories.

    This is both easy and generally the recommended thing I’ve seen for many services.

    The only thing that could cause issues is breaking changes caused by the docker images themselves, but that’s an issue regardless of backup strategy.



  • Yeah, but sizing is user dependent. So unless it’s based on the users purchasing history it’s useless what the average person does.

    If it said “L is your recommended size based on your purchase habits and customer data”, then sure. But it just says we recommend L because that’s what other people said/ordered, which makes no sense.



  • Just want to expand on this as it’s the most direct explanation.

    With two die there are 6 ways to you can roll a seven (each side has one way to add up to seven), and 36 total combinations (6 sides * 6 sides). So the odds are 6 times out of 36 or 6/36.

    With one weighted die, you have a set value (say 3 for example). There is only one side on the other die that will equal 7 (4 in our example). So you have 1 out of 6 possibilities, or 1/6 chance.

    However, this is only true for 7. If you were targeting 2 for example, the odds can change substantially. Normally you have one way to get 2 (1 and 1) so you’d have 1 out of 36 possible rolls or 1/36. If the weighted die was weighted to 6 though, you’d never be able to get 2, so your odds would be 0.



  • I saw Boox called out, but not the Boox Palma². I just got it and it’s been pretty nice. The major draw is the form factor though as it’s phone sized making it pretty portable.

    It runs android and I’ve set it up to work with AudioBookshelf and Komga

    AudioBookshelf, while designed for audiobooks, allows you to download books for offline reading and seemed the best all in one for books self hosting. It also has a native android app.

    Komga seems pretty amazing for manga and comic books (haven’t settled on an app, just using the browser now). The e-ink display isn’t the best for reading this medium, but it’s not terrible for black and white comics.

    Since both of those are self-hosted solutions they could integrate with readarr pretty easily (although audiobookshelf’s folder structure can be frustrating).



  • Some of the commands I use a lot for debugging containers, in case you go down that route:

    • docker run --rm -it --entrypoint bash <image_name>
    • This command let’s you enter a docker image with bash so you can test commands and treat it like a temporary VM. Great way to see how the image is setup
    • docker exec -it <container_name>
    • This let’s you enter a running container with bash. A great way to inspect why something might not be working or check mounted volumes, etc.