BTRFS should be stable in the case of power loss. That is to say, it ought to recover to a valid state. I believe the only unstable modes are RAID 5/6.
I’d recommend BTRFS in RAID1 mode over mdadm RAID1 + ext4. You get checksumming and scrubs to detect drive failures and data corruptions. You also have snapshotting, in case you’re prone to the occasional fat-fingered rm -rf
.
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:
This would probably be cheapest and have the least complexity.
I wouldn’t trust anything like that to the open internet. It would be better to access the system over a VPN when you’re outside the network.
Barony is fun as hell. Engine is FOSS, but the default game assets require purchase.
You’ve laid out one potential development cycle: FOSS from the get-go, and open collaboration welcome.
However, that’s not the only way that a FOSS game might be developed. The code could be freely licensed, but the upstream developers refuse to accept outside patches. In that case, there’s one “original” and then if you don’t like it, build your fork.
Alternatively, a game could be developed entirely in-house under proprietary licenses, and then only made FOSS upon commercial release. Contributor patches could improve the project, but conception of the game would be entirely the domain of its original developers.
How about writing a script to automate the deletion, thus minimizing the chance of human error being a factor? It could include checks like “Is this a folder with .git contents? Am I being invoked from /home/username/my_dev_workspace?”
In a real aviation design scenario, they want to minimize the bullshit tasks that take up cognitive load on a pilot so they can focus on actually flying. Your ejector seat example would probably be replaced with an automatic ejection system that’s managed by the flight computer.
I use a fuckload of soap and hope it keeps the grease from re-forming. Is that still bad?
Yeah, I believe there’s some kind of bridge mode you must enable on the host’s interface.
As others have said, a reverse proxy is what you need.
However I will also mention that another tool called macvlan exists, if you’re using containers like podman or docker. Setting up a macvlan network for your containers will trick your server into thinking that the ports exposed by your services belong to a different machine, thus letting them use the same ports at the same time. As far as your LAN is concerned, a container on a macvlan network has its own IP, independent of the host’s IP.
Macvlan is worth setting up if you plan to expose some of your services outside your local network, or if you want to run a service on a port that your host is already using (eg: you want a container to act as DNS on port 53, but systemd-resolved is already using it on the host).
You can set up port forwarding at your router to the containers that you want to publicly expose, and any other containers will be inaccessible. Meanwhile with just a reverse proxy, someone could try to send requests to any domain behind it, even if you don’t want to expose it.
My network is set up such that:
Did you mean source-available?
I guess? Always thought there was some pedantic Stallman-esque argument for the differentiation between FOSS and OSS, independent of the Open Source vs Source Available distinction.
Not sure if you’re able to edit the title, but this doesn’t look like FOSS, just open source.
I know this is a joke, but I couldn’t be a programmer without some pedantry. LUnix is actually a real OS! I booted it on my Commodore 64 once.
It would have to iterate over all saved keys, which sounds rather inefficient to me and potentially unsafe (timing attacks etc.)
sshd only checks for matches in the user’s authorized_keys
file, not system wide.
HR Giger is happily dead after seeing this
They would not even need to open source the servers. Just making the server available for users to run (even under a proprietary license) would be enough.
Ooh! Thanks for the tip! Been looking for some affordable drives for my next system.
I bought a LFF Dell Poweredge back in the fall, and have been waiting on a good deal for 3.5" disks. My current machine is a SFF HP Proliant, and I hate how much a 2.5" drive with good capacity costs.
A bridge in America collapsed after a cargo ship crashed into it.
make up
is my build command for pushing to prod
Haven’t used it yet, but I’ve been researching authentik for my own SSO.