Add support for placing additional static files into release directory

[gtkramer]

A static files repository should be a variable in the config repo. This repository is expected to have the following directory structure:

• toplevel
• releases

That controls which files get placed in the toplevel directory and which files get places in the directory for each release.

[mbelluzzo]

I think we can go a bit further here and say that static content can be part of a config repo just like images/ . We can have a static/ folder that, if exists, distro-factory knows that there is static content to be added. Than we need to figure out how that folder needs to be organized so we know where to add static content.

…

On Tue, Oct 15, 2019 at 9:20 PM George T Kramer ***@***.***> wrote: A static files repository should be a variable in the config repo. This repository is expected to have the following directory structure: - toplevel - releases That controls which files get placed in the toplevel directory and which files get places in the directory for each release. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#42?email_source=notifications&email_token=AAMCYZOUENNUZOINDHHZDMLQO2JBJA5CNFSM4JBF573KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HSBNOUQ>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMCYZIR2CZU5LWNRTGSJMLQO2JBJANCNFSM4JBF573A> .

[vinaypotluri]

We can have a static folder inside config repo and read from there. We won't need a different repo unless the repo has to be updated frequently.