Are you using the CLI importer tool?

Depends, on how critical something is…since we deal with servers / customers at work that often are purposely not adjusted for years…because introducing a different behaviour (even if better) would grind production to a halt, I take a not careful approach.

I was using OpenSUSE Leap, and with zypper you can review which patches are available, whether they are critical or run recommended or not needed. You can then apply which specific patch you want be CVE if necessary.

But with Leap’s path seaming messy at the moment, I moved to Tumbleweed, since you have snapshotying built in. If an update did mess something up you just rollback to the previous snapshot and in less than a minute it is fixed

Volumio is a great tool for Pi or PC and has phone app to control music selection remotely. You can add music to the volumio player, or access dlna shares, as well as add on music services and internet radio

After trying a bunch I settled on trillium, it seemed the best of the bunch. My only complaint would be the cloning note wasn’t working like I expected. I think I expected the Clone to make a copy, but it was more of a symlink duplicate

I thought that was how pull requests worked, its a branch if you’veade a departure to edit code, you have the pull request and ask them to merge into the main branch. It should be visible to everyone so everyone can review the change.

They can try to argue that latency issue and the stale state were an unknown / unanticipated problem. Like when half of Canadas Rogers network went down affecting most debit payment systems. Testing of routing showed it OK, realworld flip went haywire.

Most services have a clause that they are not liable for unforseen issues… Depends how good the lawyers were when formalizing the contracts.

Oh shit, that’s terrible.

Port forwarding is done at the router/firewall, so if ports can’t be transferred its a cgnat thing they are doing. Like a Non CGNAT IP on the internet can be sent a packet on any port.

It’s an Intel i5-7700 cpu in a Gigabyte Z270N mobo. Those were chosen as a form factor fit for the Monsterlabo fanless case. (Only a select set of boards, and in this case 1151 brackets, fit the case)

I have been looking for something new.

Last week was moving Immich up to the new release I was on an old version, which meant migrating to an intermediate version to allow a database rebuild. It worked well.

I was bored this week so just ran some wattage testing.

• 15w at idle (800MHz)
• 20w active (3.4GHz)
• 30w peak at boot

I upgraded from a pre 1.32 server, and needs an update to a 1.33 to 1.36 server version and opening app once before moving to server 2.0. So it could definitely be the server database end. It does an auto migrate of server database with the proper steps.

Snapper and BTRFS. Its only adjusts changes in data, so time travel is just pointing to what blocks changed and when, and not building a duplicate of the entire file or filesystem. A snapshot is instant, and new block changes belong to the current default.

Pretty sure you can set the options to leave permissions alone per app. At least on Graphene OS you have control of it.

Grsync is great. Having a GUI can be helpful

I understand people want ease of use, I prefer selfhosting and no cloud intervention just to be safe. But, to be pedantic, we should say cloud or external server, because SAAS just means software as a service, and there are lots of SAAS products that have no cloud aspect and are fully local.

Yeah, Plex makes it easy…other than dealing with their cloud data breach.

Just use wireguard between the two devices

The firewall on your server may need masquerading set and IP forwarding set.

Yep a 2TB 2010 NAS drive still holding data, the spin up time is getting a bit slow and some SMART numbers show it is getting older, so moved my data to a new drive to avoid catastrophic failure.

However watch out for bit rot on old drives. I had a few images fail to load because bits had become corrupted.

A ZFS system would alert you or fix these problems