Right, gotcha. I can’t help you there since I don’t use Caddy.
Right, gotcha. I can’t help you there since I don’t use Caddy.
What I think they meant is more “how to achieve X or Y” focused documentation, rather than just explaining how features A or B work. The former approach explains what you should use and how to do it, the latter only documents what each variable does.
To use an analogy: I could probably build a bicycle from the individual parts based on a tutorial with that goal in mind, but not based on the individual technical descriptions of each part.
/u/xkcd__386 is that what you meant?
My thought exactly! Would be cool if this could create transactions in Frirefly III and/or Actual.
IMO they’re currently about as good, but they still serve slightly different purposes; Immich doesn’t fully support existing libraries because they don’t support nested albums, and PhotoPrism doesn’t have a native official app and therefore only supports sync through 3rd party apps.
One thing that is relevant to mention is that Immich uses OpenStreetMap in a way that isn’t kosher, and while they’re receptive to changing that, it clearly isn’t a priority to them. It doesn’t reflect too positively on them that they’d essentially abuse another (far more important) FLOSS project like that, while PhotoPrism has made it a priority to avoid such issues.
You’re aware that apolitical organisations don’t actually exist, right?