• 8 Posts
  • 69 Comments
Joined 2 years ago
cake
Cake day: June 16th, 2023

help-circle
  • OneCardboardBox@lemmy.sdf.orgtoLinux@lemmy.mlPlug-and-play development environment
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    1 month ago

    I set up a very straightforward Godot dev environment yesterday using toolbox which is built on top of rootless Podman.

    • Create a new fedora toolbox
    • Enter toolbox
    • Install DotNet dependencies, git, etc with dnf
    • Install Godot binary from release page
    • Turns out there were other dependencies I needed
    • Godot wanted a few Wayland libs on the container, so I installed Weston (maybe overkill)
    • Godot wanted libxrandr so I added that too
    • Godot just works ™

    The nice thing about toolbox is that it uses my native host Wayland compositor. So whatever I have running in the toolbox can be interacted normally through sway (my host WM).

    You can either distribute a container image with your given toolbox configured, or just document the setup steps.








  • For backup, maybe a blu-ray drive? I think you would want something that can withstand the salty environment, and maybe resist water. Thing is, even with BDXL discs, you only get a capacity of 100GiB each, so that’s a lot of disks.

    What about an offsite backup? Your media library could live ashore (in a server at a friend’s house). You issue commands from your boat to download media, and then sync those files to your boat when it’s done. If you really need to recover from the backup, have your friend clone a disk and mail it to you.

    Do you even need a backup? Would data redundancy be enough? Sure if your boat catches fire and sinks, your movies are gone, but that’s probably the least of your problems. If you just want to make sure that the salt and water doesn’t destroy your data, how about:

    1. A multi-disk filesystem which can tolerate at least 1 failure
    2. Regular utilities scanning for failure. BTRFS scrubs, for example.
    3. Backup fresh disks kept in a salt and water resistant container (original sealed packaging), to swap any failing disk, and replicate data from any good drives remaining.
    4. Documentation/practice to perform the aforementioned disk replacement, so you’re not googling manpages at sea.

    This would probably be cheapest and have the least complexity.



  • I recommend that if you go with a home carbonation system, that you look for one you hack your own CO2 refills for.

    Some people buy a CO2 tank and regulator, then hook it straight up to their machine. I have a large CO2 tank in the basement with an adapter to refill the individual proprietary canisters. I got the tank free from a friend, and then paid 30 USD to have it certified (good for 10 years) and 30 USD to have it recharged with beverege-grade CO2. Buying an adapter was 40 USD

    My large tank holds ~5kg of CO2, and it costs about 17 USD to officially refill one of the small canisters with 500g of CO2. Thus, even if I didn’t get the tank for free (new ones cost ~120 USD), the large tank would still pay for itself after filling it one time.















  • What would happen is:

    1. You take the check and cash it (assuming they accept it at all)
    2. They find out it’s fake
    3. You have to give the money back before Rocco rings your doorbell with a baseball bat in hand

    Doesn’t seem worth it to me.

    In truth though, they’d never accept the check. 99% of the time, scammers send an image of a check, then ask you to print it and use mobile deposit to put in your account. That way, nobody ever touches it and realizes it’s a shitty jpeg on printer paper. It wouldn’t fool anyone IRL.

    Sometimes, they might send an actual check that they stole and doctored up, but that’s too much work for a scammer most of the time.