klfjoat/docker-flexget repository overview

⁠docker-flexget

Another (3rd) attempt at making a FlexGet container.

I'm no coder, I'm no GitHub expert, and I'm not release wizard.

What I am is pretty good at plugging one Lego brick into another... Meaning, I see how different pieces that stand on their own can be put together to make a larger thing, with a bit of glue in the right places.

⁠A BIG Problem

You likely expect that, if you write your FlexGet config file today, and it works today, it will keep on working into the future without problems. I have that same expectation, too.

You also would like to automatically receive bug fixes and other updates to FlexGet. I would like that, too.

The problem is, when FlexGet increases its minor version number, that's when they make changes to how config files are processed. Those changes can cause an existing config file to stop working.

To deal with this, the only thing I can think of is to create branches for each FlexGet minor version, and upgrade FlexGet in the container within that constraint.

That means that you very likely do (NOT want to follow the :latest Docker tag for this project.

You should specify the version of FlexGet you want to use, like 2.10. That will lock you in to that minor version of FlexGet. To upgrade out of it, like to 2.11, you will need to consciously and manually make a change.

That's the only way I can think of to keep this container from screwing you over silently while also updating it somewhat.

⁠Goals

Most of these are based on the user stories. Look at that file for info.

• Auto-updating container, but only within minor version number, because upgrades past minor version tend to break compatibility with config file.
• Automatically pick up changes in the config file.
• I am supporting this primarily for my own use. I welcome help, but as I said above, I'm no coder. I abhor feature creep. If I don't accept a PR, it's nothing personal.
• Lightweight container, with as few add-ons and duplication as necessary.
• Environmental variable usage from inside and outside the container.
• Solve the FlexGet SIGTERM problem.
• Access various host directories from within the container for flexibility in FlexGet config writing.
• Clear branch names and structures due to the way the FlexGet project works.