Can you do letsencrypt dns challenges against the free tier now? This was one reason I moved to duckdns. Plus I kept forgetting to login to keep the account alive so it would just stop working until I logged in and reactivated. Duckdns do emulate that experience with their random downtime though 😂
That’s because you had somone elses servers doing that part for you.
Worse they often report issues that affect them but still don’t commit resources to resolving those issues.
You can run a separate db server using local storage and use NFS only for the data volumes for the applications themselves.
IMO these kinds of poor man’s automation scripts are only useful to novice sysadmins but those are exactly the kind of people who shouldn’t be running scripts they piped from the internet for both the fact that it’s risky behaviour and the fact they don’t then get the experience doing this manually for themselves to move on from being novice.
That said, let’s not gate keep. If novices don’t want to gain experience actually doing sysadmin work and level up their abilities and just want stuff that will probably work but that they’ll not be able to fix easily if it doesn’t, at least it’s a starting point and when things break some of them will look deeper.
I personally manage my services using ansible, I only set up the actual infrastructure, the virtual machines that run the services, with terraform/opentofu. Docker is one of those in the middle tech between infrastructure and software distribution and it makes more sense to me to treat a service as a role in ansible do I can deploy it (docker, podman package install or whatever), sort it’s networking and handle it’s configuration all in one place. I’m not saying the way you do it is wrong, but this is just a step down the automation rabbit hole.
It doesn’t appear your setup provisions the actual hosts for docker so I guess you are provisioning manually for that layer? That is another area you might want to leverage opentofu for?
Also congrats on actually documenting it in a consumable way for others to learn from.
There is more than one type of water, but unless your IoT device is a fusion reactor it’s probably just running off the normal blend.
Hence the term “sunk cost fallacy”.
But once you have it’s output, unless you already know enough to judge if it’s correct or not you have to fall back to doing all those things you used the AI to avoid in order to verify what it told you.
All a NAS is is a separation of concerns, if you build a system who’s only job is to provide networked storage, then that system is a NAS. If you buy an off the shelf “NAS” and proceed to run a bunch of services on it, that is a home server, not a NAS. Build your own NAS and most of your concerns go away.
If you are going to worry about archival then when reencode it at all? Just remux the content from the dvd into a suitable container and be done with it.
Rocky now is what Centos used to be, a downstream rebuild of Redhat Enterprise. Cento Stream is now a rolling release and is pretty much RHEL unstable.
Technicality of usage rights is very relevant, framing as a purchase where it actually isn’t is dishonest and the fact that they make more money being dishonest doesn’t make it right. Other than that you used an awful lot of words to basically agree with me.
No, no ownership is being conferred except to a number, the supporters club key let’s call it. That is what you are buying, it’s like an NFT. And just like NFTs it’s being marketed as though you are purchasing the work itself which you absolutely are not doing. You are paying for the right to say you paid.
If you don’t pay you are in exactly the same state as if you paid regarding your license to use the software, it’s licensed to you under the terms of the agplv3. If they were selling a support contract that would be fine too, but again, no, you get no extra support over what anyone posting a issue on the tracker will get. Even if it were a support contract then it should be made clear that is what you buy.
Buying confers ownership of something even if it’s just a legal agreement like a software license. No ownership over immich is being conferred, nothing is being conveyed to anyone so it’s incorrect to term it a purchase, much less a purchase of immich.
None of those things are true. Paying money is in no way guaranteeing the current developers will wake up wanting to maintain it tomorrow, nor am I purchasing access to an update service. It isn’t a purchase of anything and shouldn’t be framed as one. It’s a Contribution or a donation that gives nothing in return and saying it’s something else is dishonest.
Except it’s misleading as you aren’t really buying it, you are buying a supporters badge key as I understand it. Might as well be selling an immich NFT. I still don’t think this is being upfront and it’s still a dark pattern it’s just slightly less misleading than the blatantly false buy a license wording.
The wording is still misleading because you aren’t purchasing immich and if you were, what exactly would you be purchasing? Control of the project? The immich name? You aren’t purchasing a license to use it as you already have that. A supporters badge key? Okay well be upfront that that is what you are selling because you aren’t selling immich itself.
He’s being a dick and suggesting you fix this in immich rather than provide this stop gap workaround. I for one appreciate your diligence in pointing this out as I’d seen no mention of it prior to your first post.
I’d argue that it’s self managed but not self hosted, it’s still running on somone elses computer and they ultimately control what you can and cant do with it. The distinction is murky though because a lot of the discussion here is about managing services rather than the hosting infrastructure (though of course there is some of that too).