Open jgallen23 opened 9 years ago
I think /work
will be managed separately and be specific to remote work mounts... not sure yet. I wasn't planning on anything like /env/work, but I suppose that makes sense too.
any thoughts on this for 0.1.0? I've been using this for awhile now and I like that /work is persisted for that specific environment. It keeps each env light weight - just needing the files required for that project
yeah i think something like this'll be in there
Sorry butI'm probably missing something here. What is the difference of this and manually taking care of that under
/env/work
? Is the reason to avoid sending it as a context to the docker build when building environments?