Making the library standalone

[simenandre]

IMHO, this library is very close to useless in it's current configuration.

Initially, Kopier was made to make it easier to deploy pipelines and other common stuff for all the private repositories. After just a few days, it changed form into having template functionality (adding template/text to the mix). We have made these weird service configuration files that doesn't serve much, only future hope to be used. Regardless, I think Kopier can serve good as a CLI and CI/CD tool.

• Pushing changes to a configured set of repositories is a good idea (potentially).
• Adding a Dockerfile / Github Action that can be configured seems better.

Q: How can it serve as a Github Action?
It can take templates from a centralized repository and push it to others, based on information in each of them.

Q: What information?
Such things as, name of a package for build steps.

Q: How can it serve as a CLI tool?
... TBA?

Improvements that we need(?)
-... TBA

[simenandre]

Not thinking of this issue, I added #6 . This might be way more relevant than #6, tbh.