Hennik Hunsaker

Windows 7 is actually unsupported, so any bugs with using it are unlikely to be addressed, and often even expected.

I suspect the space in the path is interfering with Docker's mounting logic. Try a user account without a space in its name...

No, partly because a compile isn't meant to be used in one exclusive environment, and partly because binaries should never be built with environment values hard coded into the compiled...

Same way. Especially for DB info/credentials, you want to pull those from the environment at runtime – even with only a single deploy environment, that information may change between compile...

I know Elixir supports it. I don't know how. Ask around.

Does Mint use systemd? Also, how long ago did you download/install Nanobox? Have you run `nanobox-update` recently?

It's not wrong, just might be part of the problem. I know the server starts properly with systemd, now, but haven't confirmed with upstart recently. Ok, just wanted to rule...

Appreciate the update! I'll talk to the engineers about supporting upstart as well.

In addition to `nanobox fetch [-r|--recursive] [] . remote/path local/path`, we'd also want the reverse, `nanobox send [-r|--recursive] [] . local/path remote/path`...

To be clear, Bash will probably interpret those list args for us, so it would more acurately be support for listing multiple source files and a single destination. Still. Agreed....