As you have one opinion of corne too small I’ll join in to the opposite!
First off, yes, layers are something to get used to. As I came from the neo2 layout that was easier but I still recall the utter pain in the beginning.
But once the layers click … So does the board.
I think I spent more one than I’d like to admit building my zmk config but now I’m … Way slower than with a full board but it’s more fun and I feel getting better :D
You got a lot of relevant answers so I want to point out something else:
You’re hosting your own services. By yourself. Fuck everyone with a broom who tries to gatekeep that. And I don’t mean wooden side first.
Seriously, your question is on point here from my perspective and as long as it has a connection to running services by your own I personally would love more diversity in hosting solutions.
Personally, I’d love to see people share more about their provider agnostic opentofu deployment or someone who went all in on AWS lambdas for weird stuff.
And check for each music service their offered music. I’ve checked out tidal actually today with one of those export playlist tools and about 10% of my (honestly: niche) music wasn’t available.
Does that mean that an “all” view is "onl"y all of the subscriptions/places people from my server have?
That’s quite interesting.
And thanks!
No one forces unattended updates. And containerd is already living in the userspace.
If every dev would live on a kernel level stability approach we’d will not have a containerd release at all.
One thing that was only mentioned briefly by someone else is the physical button turning on the computer.
Similar to the paperclip test figure out where the power button goes into the mainboardw and bridge that with a short cable. Is possible that by moving the case the old button lost a cable.
This is just one more thing to test though, it’s really trial and error as you know :)
From what I understand: CasaOS is simply an abstraction layer and takes away a lot of the manual work.
I agree with you that this shows down learning quite a bit.
I see three ways forward for you:
a) switch to a Linux base system, Debian, arch, nixos, whatever resonates and set up everything from scratch. High learning curve but no more hidden things.
b) same as a but as a separate setup. This is what I would recommend if you have the time and cash. Replicate what’s already working and compare.
c) figure out how to do things manually within the CasaOS framework. Can’t help you there though :)
The first link goes into amazing detail on that. In short: all your information concerning location as well as current IP and some other metadata gets send to a basically unknown company with no transparency on how that data is handled.
I highly recommend reading the first, linked post though!
Cups
linux printing server - if you want to share a printer over network or just use one locally on a linux machine.
(not OP but same boat) Doesn’t really matter to me because google knows my servers external IP which is a non-issue: I don’t expect google to try to attack me individually but crawl data about me. There is no automatic link between my server and my personal browsing habits.
In terms of attack vector vs ease of use , self hosting searxng is a nobrainer for me - but I do have an external server available for things like that anyway so no additional overhead needed.
A Dockerfile itself is the instruction set. There is a certain minimum requirement expected from a server admin that differs from end-user requirements.
The ease of docker obfuscates that quite a bit but if you want to go full bare metal (or full AWS or GCS, etc etc) then you need to manage the full admin part as well - including custom deployments.
No worries I phrased that quite weird I think.
A NAS is only more power efficient if the additional power of a full server is not used. If for some reason the server is still needed than the NAS will be additional power consumption and not save anything.
(for example I run some quite RAM and compute heavy things on my server which no stock NAS could handle I think).
That would replace the computer with the NAS though and is not true for a server that you’d want to extend, right?
Is that 370watt across all of them or per fat server? I ask because three m5 sound like a lot of power drain!.
And thanks for sharing!
I didn’t know that about the immich app, thanks for pointing it out!
Then you need a third application (e.g. syncthing) to replicate the auto upload functionality of Nextcloud.
Personally I don’t want to have same functionality in a different stack because of pipeline issues. Doesn’t solve OPs issue I just wanted to point out that your solution might have drawbacks OP didn’t see at first glance :)
Thank you! That’s really interesting, the performance with a pi 3 was way worse - even more than the pure spec difference would’ve lead me to believe.
The OCR devs have made a really awesome job!
Thanks for sharing! The only thing I’m surprised to see in your list is paperless - how long does OCR take on a pi?
“Being a router” is what they are good for! Even needed.
Edit to be more specific: two switches in each of the 10gbit and redundant uplink would be a setup I can see, depending on your line.
No overkill there :)
If you do don’t trust em then don’t update syncthing - it’ll work for quite a while I assume.
And in addition the keepass safe default encryption of AES-256 and is even secure against theoretically existing quantum computer attacks to our current knowledge. It is designed to be not trusted by the storage owner :)