At least by me a drink before although I appreciate the direct approach ;)
On a serious note, thank you! Looks a bit too text heavy for me (I prefer symbols) but still looks like an awesome project!
Scipitie
joined 10 months ago
That link is a Minecraft launcher, not sure that's the correct project? Or am I missing something? :)
OK now I have to escape to really smart assery and assume that's what I meant the whole time ;)
Edit code 2 describes something that went wrong - but that something telling you that it went wrong was the tar binary which therefor most have been valid to evaluate that!
Under no circumstances did I assume that the hint towards help itself would've been an exit code 0, no sir!
To be honest: if I'd designed that bomb it would've exploded in my face for trying to be too clever.
tar
Done. That's a valid command, no error code, nothing. KISS!
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 :)
Makes sense, thanks for pointing it out!
I have to make this nitpick:
"you" are the one keeping you on windows. You decide that those features are more important than any disadvantages.
Which I think is absolutely OK - that's your choice. Many many people took this choice for a myriad of reasons and are the sum of "windows majority" - and no "I would change if" will perpetuate either feature development on Linux programs nor pressure on Microsoft.