Hi!

The current nixery-based containers lack clarity around ldconfig specifics in Nix, which breaks software tooling expectations, that are usually met within conventional Linux distributions.

For instance, consider the Haskell Stack

[nix-shell:~]$ docker pull nixery.dev/shell/which/stack
Using default tag: latest
latest: Pulling from shell/which/stack
30c2bb75530a: Already exis

We get regular questions about how to deal with not having allowed values on the this of the TestContext (e.g. here). We should document an example of how to set up the test context!

If this is for public use, kindly show the user how to use it.

I'm wondering if I could create a web app with glimmer components, emberjs templates and routing and a model written in Rust. Is this the way?

Readme says inputFiles is an array:

options = options || {};
// options.inputFiles === array of globs, to consider for the cache key

However looking into the code, the default is an empty hash:

this._inputFiles = options.inputFiles || {};

At the least these two don't agree with each other - which one is correct?

Implement a public page which can be used to report bad documents.
The user must enter (document.id or document.barcode) and a reason for the report.
The page should explain where the user can find document.id or document.barcode.
The page may show the metadata of the document to verify the input.

Reported documents must be shown on the "DB-Admin".
There may be a special page to review repo

If I implemented a feature to apply the ESLint fixes to the output directory, would that be accepted? Just want to get some confirmation that that would be desirable before starting work on it.

Adding fix: true to the options passed on to the ESLint Node API isn't quite enough to actually makes the changes; you also have to invoke [outputFixes](http://eslint.org/docs/developer-guide/nodejs-a

Which options are supported ? There is no documentation about that.
I want to pass an option to uglify to not remove comments. How can I do it ?

Regards