Eric Kidd

Ah, that's an interesting idea! Unfortunately, my backlog of critical issues on other projects is fairly large, and there's not much chance I'll be able to add this particular feature...

I am not aware of any PRs for this issue, though I would still be happy to accept and review one. As noted above, I'm not currently doing any new...

@khuey OK, if `docker-compose` supports it, we can certainly implement it. But please keep in mind my comments on https://github.com/faradayio/cage/issues/87#issuecomment-354767603. We don't have any kind of coherent, principled model for...

This is a very good question, but I don't know the answer! You might try using a `build.rs` script to download the images at build time, and include them directly...

Hmm, now that I've had a change to think about this more, this might be something we want to consider supporting directly somehow. But I mostly use `wasm-bindgen` instead of...

@camjackson We can certainly just disable this warning. The lack of valico means that we probably have worse error messages, and we don't validate inputs and outputs as well as...

A `debug!` would be silent unless logging were manually elevated. Or, actually, we could look at this line [here](https://github.com/faradayio/cage/blob/master/src/main.rs#L413), and add another rule for `compose_yml::v2::validate`, setting it to `log::LogLevelFilter::Error`. On...

Thank you for this patch! Normally, this buildpack is supposed to be used with an explicit `Procfile`, as described near the end of [this section](https://github.com/emk/heroku-buildpack-rust#using-this-buildpack). This is done for several...

Honestly, I don't know why `cargo run` even works. In theory, we should _never_ include `cargo` or `rustc` in the compiled slug, and so attempting to use it should simply...

I would be interested in PR using this technique, yes! (Sorry for the slow replies; I'm maintaining too many open source projects and GitHub hasn't let me into Notifications Beta...