FORKED TO lawndoc/stack-back

[lawndoc]

PSA that this repo has been forked to https://github.com/lawndoc/stack-back where it is being actively maintained.

I've noticed some people interacting with this repo and hearing nothing back so just wanted to spread awareness that there is a working fork now with continuous enhancements.

[einarf]

Thank you for the poke! I haven't had any time to maintain this repo in the last couple of years so a fork is great. That's the beauty of open source and simple licenses like MIT.

I might get time in the future to revamp this project. It was really put together in a hurry as a prototype, but it has been proven useful at the very least. As far as I remeber the main weakness is that commands always execute in the spawned backup container instead of making this optional/configurable.

We'll see what the future hold.

[lawndoc]

@einarf great to hear from you! If you are considering resuming maintenance on this project, maybe we could collaborate and share the load.

If you're interested, reach out to me at the email listed on my public profile and we can talk about re-merging our forks.

Happy holidays!

[einarf]

I'll definitely poke if I have time to be active again. I'll probably start by looking closer at your fork first.

There's so many things to improve in this project as it was just an ugly prototype. Docker right now is also a lot more mature. More flexible features in labels would be nice. Mentioning in docs that you can use restic in the container directly to do repairs (reindex etc) also helps people out a lot. There's plenty of issues in this repo to look at such as configuring how often a prune should happen. Some tools and info on how to restore data from restic would also be nice. That's the step most people don't think about and having a helping hand in that situation is priceless.

My original plan was to completely rewrite the project for a 1.x release, but that never happened 😅

[lawndoc]

I haven't really done any major refactoring with my changes either. I'm open to the idea of a rewrite. I'm pretty busy through February studying for an exam, and then I should have more time to contribute time to the project again.

I originally forked the project out of necessity since it fit my need perfectly, but wasn't in a working state at the moment.

Like I said in my last comment, I'm open to collaborating if you want. There have been a couple of outside collaborators contributing to my fork already as well.