What you’re talking about is a software solution, but the solutions you mention are not standalone software in the way you’re thinking.
Honestly, it sounds like you don’t want a NAS, you just want shared network storage. If that’s the case, make a Fat partition, share it windows, then go configure samba under the Linux side similarly, paying attention to map a user with a matching uid. There will be some wonk happening here and there with file permissions perhaps, but it will work for the most part.
The other options you mentioned are meant to control the entire host, but you may be ready to make that leap yet.
For minimal money, you could also try and get your hands on an older RPi (possibly for free, people just have them laying around), and attach your disks via USB to that, and then you have a basic, but dedicated NAS you can setup the way you like.
I don’t think there is anything wildly wrong with it, but it seems like you’re doing all of this at the router, unless you have dedicated switches for each VLAN?
VLAN is not a security feature, it’s a logical separation of IP segments. Maybe I’m missing your intention here, but just setting different IP spaces on VLANs and then bridging them doesn’t help your security, it just complicates your network.
Unless you’re watching the videos directly on the Synology, I don’t see this affecting too much unless you’re strictly relying on transcoding for other devices you’re positive don’t support it. Even then, you could always just default to rendering on the remote device directly which isn’t a huge deal. If you’re using Dolphin, it shouldn’t be an issue. You could always use VLC as well and it shouldn’t be a problem.
Maybe I’m missing something else?
Well the services would have to speak the same event or messaging system, whatever it may be. Then you’d just need to bridge the networks of the containers, or have them speak to endpoints in each side.
There is no universal messaging system between all pieces of software though. Maybe figure out what you’re sending to first, then work back from there. There’s nothing blocking you from sending data between two containers in a variety of ways though.
Looking through some of the notes there, some things to consider:
The biggest question mark there is kernel driver compatibility if you’re running a Linux distro. I’d check around. There are also other vendors with similar form factors and price that DO have hot swappable drives. Maybe something to consider.
Can you make it work? Yes
Should you make it work? No
It’s going to flakey beyond belief for a number of reasons, and you’ll need some pretty complex routing to make it work how I think you’re describing. I would look at using a clustered setup for your auth instead so you never get locked out due to network issues.
Gotta say, I love the idea behind this project, and it’s great you’re reaching out to this community here. I haven’t run it myself yet, but it looks great, and the feature list is massive.
Couple questions really stopping somebody like myself from setting up an instance though.
It’s not “just” a launcher, and it’s not quite a distribution platform. Is this mostly geared towards people playing the same game on multiple machines?
It seems like this is setup as a Steam replacement, but only for a DRM-Free games, so why would you (as a creator) suggest I use this instead?
This also seems like there’s a world in which this is set to be a decent game hosting platform. Plans?
Thanks for showing up.
BitWarden already has lots of clients. There’s also VaultWarden for the server if you want.
This is being blown a bit out of proportion though. All they are saying is the official SDK may have some non-free components going forward. So what? It’s a private company, they can do what they want. Or the community can just fork it and move forward with a free one if they want, but it’s just not going to be in the official BitWarden clients. Hardly news or a big deal.
Well, apologies for being bluntly critical. I can offer a few constructive tips to help with writing about technical topics:
Anytime you see anyone post something like “THIS Is How You Do The Thing”, it should automatically be ignored. This article is no exception.
The author is making a big deal about a team of 40 people and “millions of customers”…k.
Not sure if anyone is supposed to be impressed by that, but the titular argument here isn’t a position for a small team and product, it’s making the case that “ALL THINGS EVERYWHERE ARE TOO COMPLICATED IN PRODUCTION ENVIRONMENTS”, which is just an ignorant position to take.
If this had come with some sort of metrics, tools, or workflow to back up the claim, then it would be worth reading. Nothing like that here. This is just an inexperienced person’s boasting rant with zero elaboration about what actually works for them, why, or suggestions for others facing some sort of similar situation.
There is no content here, just time wasted.
You might be looking for Nocodb
Okay, so two really big things:
You’re confused a bit on how network routing works. If you’re building something that bridges multiple networks (local + VPN + VPS), you need to know about how to route things to different places. You’re dealing with 3 networks at this point.
You might be misunderstanding how “zero-trust” and local networking fit together. Right now you have some local machines at least, AND a router. You don’t need all of your local machines to individually bridge a gap to your VPS, you want it the other way around.
If the majority of your machines are local, then make that your hub. Everything else should be a client. Adding all these individual nodes to routes in a mesh network makes absolutely no sense, and will definitely cause routing problems, if not something like ARP poisoning (we can’t see your config).
Just make the remote machine clients to your local network and be done with it.
MONTHLY?? That’s a bit much, don’t you think?
If you’re regenerating certa that fast, I can’t think of anything that’s going to secure AND easy enough to satisfy automating this.
Whatever tool you want to use to secure the contents of the cert from its initial creation, to distribution, is fine enough. If you want super easy, use an SSH/SCP script. If you want something more elegant, think Hashicorp Vault or etcd.
Ansible is probably more effort than it’s worth (plus securing the secrets of the cert), and any other config mgmt tool won’t deal with the distribution portion simply, so I’d skip all of that.
Tons. Go look for refurb units from any of the big manufacturers, but I doubt you’ll get them at steal prices. Have a look at the Minisforum larger format models that are more updated and $250-400. They can fit that and more. The MS-01 is a gem.