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
I've still been chatting to Tutum support about getting this deployed in Docker (because I WON'T LET IT GO), and they suggested using the Tutum API, which was a real 'why didn't I think of this sooner' moment. This would get around the issue with volumes when we deploy this with Docker, and also would mean we don't need to mount the docker socket as a volume too.
This isn't necessary for the end of this sprint, but would be a nice improvement for the future, and would make things MUCH neater.
The text was updated successfully, but these errors were encountered:
I've still been chatting to Tutum support about getting this deployed in Docker (because I WON'T LET IT GO), and they suggested using the Tutum API, which was a real 'why didn't I think of this sooner' moment. This would get around the issue with volumes when we deploy this with Docker, and also would mean we don't need to mount the docker socket as a volume too.
This isn't necessary for the end of this sprint, but would be a nice improvement for the future, and would make things MUCH neater.
The text was updated successfully, but these errors were encountered: