NDS-339 generated a number of questions about the "file manager" container that also apply to development environments in general: We need to answer the following questions:

• Should there be a special service spec for the file manager (cloud9-fm. for example). If so, is it a normal stack or something special?
• How will the file manager stack be launched (using normal start/stop, or something else)
• Does the file manager and developer environments in general run indefinitely or timeout (pertains to NDS-365)
• Does the file manager show as a running stack or development environment?
• How are we handling authentication?

Ideally, the file manager would map the user's home directory, for example:
docker run -p 8181:8181 -v /Users/willis8:/home/willis8 --rm -it craigwillis/cloud9 bash
nodejs server.js -w /home/willis8
The home directory mapping is done in NDS-350. It looks like we need an environment variable (e.g., HOME or NDSLABS_HOME) as part of NDS-350.