Output Ignore List

[olls]

The ignore list is not really relevant to the repository and it is a bit of a nuisance to change it. It might make more sense to have an ignore file we can put in the output directory with a list of directories we want to keep here, that way the information is kept right next to the directories it is relevant to.

[geraintwhite]

I think the ignore list is also used to cache the node_modules in the
processing directory so they are not re-downloaded every time

Geraint White
Web Developer

mail@geraintwhite.co.uk
geraintwhite.co.uk

On 27 October 2014 11:29, Oliver Faircliff notifications@github.com wrote:

The ignore list is not really relevant to the repository and it is a bit
of a nuisance to change it. It might make more sense to have an ignore file
we can put in the output directory with a list of directories we want to
keep here, that way the information is kept right next to the directories
it is relevant to.

—
Reply to this email directly or view it on GitHub
#5.

[olls]

Yes, but isn't that hard coded into the program? We should leave the
current functionality alone, so we can still ignore things in options.json
(relevant to the repo), but for irrelevant things, like ld30 in
oliverfaircliff.com, it makes no sense to be in the repository, so it could
be specified in an ignore file in the output directory.