5 ms·

it's really not much to manage assuming you are already doing backups. you ~ pay the energy cost either way.

BeetleB 3mo ago
Lessons from using self hosted image services years ago: - Upgrade breaks things. Need to restore from DB, install previous version, etc. - Need to update frequently (i.e. if I wait 2 years, the upgrade script doesn't work). - Discovering a corruption months/years later. Some data just lost by that point. - Backward incompatible changes Of course, if you need the features, by all means use it. I just want to back up my photos and use FolderSync daily. I have a separate workflow for pruning. As long as FolderSync (or some similar app) exists, I know this flow will work 10 years from now (heck, I've been using it for almost as long). No time spent worrying about upgrading, etc.
- hamdingers 3mo ago
  > Lessons from using self hosted image services years ago: Alternate title: "Outdated lessons I haven't re-evaluated"
  - BeetleB 3mo ago
    Are you saying there are never backward incompatible changes? Are you saying there's no need to back up the underlying DB? Are you saying I can keep an insurance running for, say, three years and it'll be trivial to upgrade after that?
    - hamdingers 3mo ago
      I'm saying your contribution is outdated and irrelevant, and my primary intention in commenting is to label it as such for any passers-by who might think you're talking about the current state Immich. That sad, I'm happy to answer your questions. I've run Immich in docker for 3 years with automatic updates through watchtower. Updates are frequent but require no effort from me and have never broken anything, nor is there an "update script" to fail. Nor have I encountered "corruption" at any point. I do back up the database and my photo library. I'm glad you're happy with your solution, you can share it without disparaging other solutions you're unfamiliar with.
      - BeetleB 3mo ago
        I'm glad you're happy with it, and perhaps Immich will continue to remain secure. 3 years is comforting. I will note that the last solution I used was fine for over a decade before it broke (and eventually the project died). For much of the time I was using it, it was the primary open source self hosting solution. So one of my criteria is: "If the project dies, can I maintain it?" Obviously, I can't use that approach for everything (limited skills and time) - I do use NextCloud, for instance (which, BTW, is fairly painful for some of the reasons I listed above). But wherever I can (and wherever it's important), it's best to develop your own stack. Best to think in the long term. But yes, for sure, there are down sides to my approach.

Lessons from using self hosted image services years ago: - Upgrade breaks things. Need to restore from DB, install previous version, etc. - Need to update frequently (i.e. if I wait 2 years, the upgrade script doesn't work). - Discovering a corruption months/years later. Some data just lost by that point. - Backward incompatible changes Of course, if you need the features, by all means use it. I just want to back up my photos and use FolderSync daily. I have a separate workflow for pruning. As long as FolderSync (or some similar app) exists, I know this flow will work 10 years from now (heck, I've been using it for almost as long). No time spent worrying about upgrading, etc.

hamdingers 3mo ago
> Lessons from using self hosted image services years ago: Alternate title: "Outdated lessons I haven't re-evaluated"
- BeetleB 3mo ago
  Are you saying there are never backward incompatible changes? Are you saying there's no need to back up the underlying DB? Are you saying I can keep an insurance running for, say, three years and it'll be trivial to upgrade after that?
  - hamdingers 3mo ago
    I'm saying your contribution is outdated and irrelevant, and my primary intention in commenting is to label it as such for any passers-by who might think you're talking about the current state Immich. That sad, I'm happy to answer your questions. I've run Immich in docker for 3 years with automatic updates through watchtower. Updates are frequent but require no effort from me and have never broken anything, nor is there an "update script" to fail. Nor have I encountered "corruption" at any point. I do back up the database and my photo library. I'm glad you're happy with your solution, you can share it without disparaging other solutions you're unfamiliar with.
    - BeetleB 3mo ago
      I'm glad you're happy with it, and perhaps Immich will continue to remain secure. 3 years is comforting. I will note that the last solution I used was fine for over a decade before it broke (and eventually the project died). For much of the time I was using it, it was the primary open source self hosting solution. So one of my criteria is: "If the project dies, can I maintain it?" Obviously, I can't use that approach for everything (limited skills and time) - I do use NextCloud, for instance (which, BTW, is fairly painful for some of the reasons I listed above). But wherever I can (and wherever it's important), it's best to develop your own stack. Best to think in the long term. But yes, for sure, there are down sides to my approach.