𝚓𝚊𝚎(六六六) on Nostr: :ipv4: Alex > and setting up nginx was three as a permanent hotfix fit better, as ...
:ipv4: (nprofile…66f2) Alex (nprofile…uf7k)
> and setting up nginx was three as a permanent hotfix fit better, as alex had changed the nginx config a couple of times between updates breaking the deployment
that'll do it. sometimes it's hard to track upstream changes.
> that caddy adapter is more of a proof of concept than a real thing you can rely on
it's been working for me for a while, until i moved all my proxy setup to caddy and compiled in some other stuff and went all caddy syntax
> most times you can skip terraform too in self host scenarios, migrating the proxmox provider to ansible playbooks saved us from having to fix it every other month between version incompatibilities and fork switches
i've found that using terraform/tofu in a self-hosted environment was a flex more than anything. for proxmox targeting i'm doing similar with all ansible. everything is executed via pipeline, although i'm experimenting with gitops pattern lately so we'll see.
> mutable state is always a bitch one way or another though
there's no way around it really, it's just part of the pain of life i think.
> and setting up nginx was three as a permanent hotfix fit better, as alex had changed the nginx config a couple of times between updates breaking the deployment
that'll do it. sometimes it's hard to track upstream changes.
> that caddy adapter is more of a proof of concept than a real thing you can rely on
it's been working for me for a while, until i moved all my proxy setup to caddy and compiled in some other stuff and went all caddy syntax
> most times you can skip terraform too in self host scenarios, migrating the proxmox provider to ansible playbooks saved us from having to fix it every other month between version incompatibilities and fork switches
i've found that using terraform/tofu in a self-hosted environment was a flex more than anything. for proxmox targeting i'm doing similar with all ansible. everything is executed via pipeline, although i'm experimenting with gitops pattern lately so we'll see.
> mutable state is always a bitch one way or another though
there's no way around it really, it's just part of the pain of life i think.