-
Peter Hutterer authored
Having a separate file gives us slightly more flexibility what we can provide in terms of templates from ci-fairy. It also provides the option of updating ci-fairy independently from the base templates in case we don't want to rebuild a project's containers but want to make use of some new ci-fairy feature. We re-use the existing infrastructure for the template generation by calling the ci-fairy template a distribution because there's about 70% overlap anyway. Unfortunately, because there is only 70% the other 30% need to be special-cased now. So we add a few checks for a 'distribution' to provide custom templates and stages. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
6789d7d6