← Back to context

Comment by kachapopopow

2 days ago

I use k3s for my home and for dev envs I think it's completely fine especially when it comes to deployment documentation.

I am way more comfortable managing a system that is k3s rather than something that is still using tmux that gets wiped every reboot.

Well... it's what I would have said until bitnami pulled the rug and pretty much ruined the entire ecosystem as now you don't have a way to pull something that you know is trusted with similar configuration and all from a single repository which makes deployments a pain in the ass.

However, on the plus side I've just been creating my own every time I need one with the help of claude using bitnami as reference and honestly it doesn't take that much more time and keeping them up to date is relatively easy as well with ci automations.

6 comments

kachapopopow

Reply
Imustaskforhelp  2 days ago

> I am way more comfortable managing a system that is k3s rather than something that is still using tmux that gets wiped every reboot.

Thoughts on Tmux-resurrect[1] , it can even resurrect programs running inside of it as well. It feels like it can as such reduce complexity from something like k3s back to tmux. What are your thoughts on it?

[1]:https://github.com/tmux-plugins/tmux-resurrect?tab=readme-ov...

  • kachapopopow  2 days ago

    I had it break enough times to where I just don't bother.

    • Imustaskforhelp  2 days ago

      Well firstly I would love to know more about your workflow where it actually broke etc. because I feel like tmux-ressurect team could help or something for sure.

      I haven't used the tool itself so I am curious as I was thinking of a similar workflow as well sometime ago

      Now please answer the above questions but also I am going to assume that you are right about tmux-ressurect, even then there are other ways of doing the same thing as well.

      https://www.baeldung.com/linux/process-save-restore

      This mentions either Criu if you want a process to persist after a shutdown, or the shutdown utility's flags if you want to temporarily do it.

      I have played around with Criu and docker, docker can even use criu with things like docker checkpoint and I have played with that as well (I used it to shutdown mid compression of a large file and recontinue compression exactly from where I left)

      What are your thoughts on using criu+docker/criu + termux, I think that it itself might be an easier thing than k3s for your workflow.

      Plus, I have seen some people mention vps where they are running the processes for 300 days or even more without a single shutdown iirc and I feel like modern VPS providers are insanely good at uptime, even more so than sometimes cloud providers.

      1 reply →