3 ms·

Maybe their hobby is not tinkering with Nextcloud and they would rather put that limited time/energy into setting up k8s clusters or developing a web app. Who k

Maybe their hobby is not tinkering with Nextcloud and they would rather put that limited time/energy into setting up k8s clusters or developing a web app. Who knows? The point is with limited time one has to pick their battles and maybe setting up zpools and a full next cloud docker compose isn't what they want to spend their time on.

rfoo 6y ago
> The point is with limited time one has to pick their battles Yeah, that's why I pay for a managed K8s instance for my toy projects but do my own sysadmin work on various self-hosted things. The former is not my hobby so I'd rather pay someone else to do it. This is an inherent limitation of our current tech stack, and unfortunately the cheapest mitigation we have is "take full system snapshot a.k.a. do your sysadmin work". The alternative (LTS release etc) all cost much more money.
- nickthemagicman 6y ago
  Numerous pieces of software do LTS with no additional cost or supported via other avenues. It's literally just branching at one release and fixing bugs in that release for a few years, which also benefits upstream branches. That way people may lose new features but gain stability.
  - rfoo 6y ago
    > It's literally just branching at one release and fixing bugs in that release for a few years This takes engineering time, i.e. money. It may also benefit upstream branches, but again porting patch between branches takes time, especially after massive refactoring happened on latest branch.
znpy 6y ago
Again, I see your point, because I've been there :) But you're missing an important point of view: do you rely on that data? If it's a toy project, don't even bother, just ignore all my replies. If you do rely on nextcloud and the data stored there, having a backup procedure and safeguards for the upgrade process helps a lot. Next time you perform an upgrade you can proceed without fears and stress, and way faster (if you run on docker) and that frees up time to play with kubernetes clusters and webapp development :)
- nickthemagicman 6y ago
  Right but I think the original point was that it would be nice not to have to do that. An LTS connected to a NAS would avoid all of that. Lol.
  - znpy 6y ago
    Except it's not your call to make, or OP's call to make. You're already getting quite a piece of software for free, demanding extended long-term support isn't really fair, expecially if you consider that they offer a simple update procedure.
    - nickthemagicman 6y ago
      There was a wish. Not a demand. Many software has it so it's not unreasonable to simply discuss something that would be nice

rfoo 6y ago

> The point is with limited time one has to pick their battles Yeah, that's why I pay for a managed K8s instance for my toy projects but do my own sysadmin work on various self-hosted things. The former is not my hobby so I'd rather pay someone else to do it. This is an inherent limitation of our current tech stack, and unfortunately the cheapest mitigation we have is "take full system snapshot a.k.a. do your sysadmin work". The alternative (LTS release etc) all cost much more money.

nickthemagicman 6y ago
Numerous pieces of software do LTS with no additional cost or supported via other avenues. It's literally just branching at one release and fixing bugs in that release for a few years, which also benefits upstream branches. That way people may lose new features but gain stability.
- rfoo 6y ago
  > It's literally just branching at one release and fixing bugs in that release for a few years This takes engineering time, i.e. money. It may also benefit upstream branches, but again porting patch between branches takes time, especially after massive refactoring happened on latest branch.

znpy 6y ago

Again, I see your point, because I've been there :) But you're missing an important point of view: do you rely on that data? If it's a toy project, don't even bother, just ignore all my replies. If you do rely on nextcloud and the data stored there, having a backup procedure and safeguards for the upgrade process helps a lot. Next time you perform an upgrade you can proceed without fears and stress, and way faster (if you run on docker) and that frees up time to play with kubernetes clusters and webapp development :)

nickthemagicman 6y ago
Right but I think the original point was that it would be nice not to have to do that. An LTS connected to a NAS would avoid all of that. Lol.
- znpy 6y ago
  Except it's not your call to make, or OP's call to make. You're already getting quite a piece of software for free, demanding extended long-term support isn't really fair, expecially if you consider that they offer a simple update procedure.
  - nickthemagicman 6y ago
    There was a wish. Not a demand. Many software has it so it's not unreasonable to simply discuss something that would be nice