You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea of this issue is discuss how to handle the host volumes used only for local development that, also, the absolute path changes across developers and all need to do local development.
I haven't really thought about it, but maybe using a file with all the containers for production, and the one for local dev just adds the volume mounts and a "cat prod dev-volumes > dev" is done and dev is always kept up to date. Probably this is not a good idea and something better can be done, but just to start the discussion :)
The text was updated successfully, but these errors were encountered:
hey @rata, so sorry we missed this issue! since we moved work on localkube over to minikube, I believe dealing with host volumes is on their roadmap, and this issue (kubernetes/minikube#422) has discussion on it!
On Fri, Jul 29, 2016 at 05:14:29PM -0700, Mackenzie Burnett wrote:
hey @rata, so sorry we missed this issue! since we moved work on localkube
over to minikube, I believe dealing with host volumes is on their roadmap, and
this issue (kubernetes/minikube#422) has discussion
on it!
Np! I thought it was on minikube now, no that this issue was missed! :-)
Hi,
The idea of this issue is discuss how to handle the host volumes used only for local development that, also, the absolute path changes across developers and all need to do local development.
I haven't really thought about it, but maybe using a file with all the containers for production, and the one for local dev just adds the volume mounts and a "cat prod dev-volumes > dev" is done and dev is always kept up to date. Probably this is not a good idea and something better can be done, but just to start the discussion :)
The text was updated successfully, but these errors were encountered: