OK 80 GB is for sure an edge case. Nextcloud won’t even work for that due to PHP memory limits, I think.
Interesting problem. FTP is an option, with careful instructions to an untutored user. Maybe rsync over a VPN connection if it is always the same sender.
Not even sure what else would reliably work, except Tannenbaum’s Adage.
Just looking through the features, things like their own VPN.
Lot of reinventing the wheel going on there. I will be interested to see how it matures.
Sending is someone else’s problem. They have all sorts of different understandings and tools and I can’t deal with them all. So the only alternative is to set them up with an account in (e.g.) Nexcloud or just accept whatever Google service they use to send you a large file.
Sending other people files is easy in Nextcloud, just create a shared link and unshare when done. Set a password on the file itself.
Got any links for howtos on this?
I dealt with a lot of time sinks like this running on consumer hardware. I got a Dell R720 and those problems all went away. Now I have a power and cooling problem. :D
Interested in this too - immich gets so much viral hype I’m a little suspicious of it
That’s such a nice feeling
I run it on BSD and just use the pkg and never have any trouble. Clients are all in the Tumbleweed repos so are the latest which I think helps. Update, run occ update and it always works fine.
Don’t forget that “may you live in interesting times” is a curse
Ive been using exim, hardly a change to my config in many years.so there is almost no point in having a webui to config. Works great. Front end with pfsense and pfblocker, add spamassassin, it is very, very, very solid once you get over the initial configuration hump. Migrate by copying the config file to the new server.
Fsil2ban piped to pfblocker works great. Plus snort
Thst seems like a good option. Ive got some test beds to try it out on
Yes of course. So BSD Truenas is dead? That is a True shame, as BSD is rock steady reliable and runs on truly ancient hardware just fine.
Even if the virtualized router is down, I’ll still have access to the physical server over the network until the DHCP lease expires. The switch does the work of delivering my packets on the LAN, not the router.
Yes, of course it depends on your network topology. If you have a link in the same subnet you’re good (and can configure a static IP if need be). But if you’re using vlans you can get in a pickle if the router is down. In my setup everything on the user side is segregated so if the router goes down I have to take a dedicated management laptop and plug into the host management network directly on the management switch where i keep a port empty. This maintains segregation and in practices means I take my ancient Acer Aspire One used for nothing else into the server room that looks strangely like a laundry room and plug it in.
It works great as long as you have a method to access the server directly when the router machine is down. A laptop set to a static IP on the same subnet will let you access the host when you b0rk something. Keep a backup config on that machine It’s pretty great though. Just remember pfsense won’t support more than 7 external interfaces when you start getting crazy with vlans
Super lame. BSD is very preferable for core systems like this.
Core is still getting updates?i got one last week.
You’re describing the world wide web, except giving others write access