Deis Bot
Deis Bot
_From @renegare on December 6, 2014 14:49_ @PierreKircher the hackyway I described above, is by creating a direct connection to the deis-registry (and has nothing to do with a load...
_From @mboersma on December 6, 2014 15:38_ @renegare we did actually have a PR at one point to add `deis push` to the mix: https://github.com/deis/deis/pull/1412. I can see how it...
_From @renegare on December 9, 2014 12:36_ @mboersma, am I right in assuming that if we had a `deis push` command, all requests will need to go through the `lbl...
_From @bacongobbler on December 9, 2014 16:6_ http://docs.deis.io/en/latest/understanding_deis/concepts/#build-release-run `git push` goes from `lbl > router > builder`, which builds the image, pushes it to the registry and notifies the controller...
_From @wenzowski on March 11, 2015 8:15_ /bump to join this thread
_From @carmstrong on June 7, 2015 19:55_ This feature is on our open roadmap: http://docs.deis.io/en/latest/roadmap/roadmap/
_From @renegare on June 8, 2015 13:46_ Nice one guys. Been AWOL, but great to see this.
_From @bacongobbler on June 26, 2015 22:24_ So to think about this feature, there are a few things I can think of. If this is good, then I'll move to...
_From @aledbf on June 26, 2015 23:32_ @bacongobbler please do not remove `deis pull`. I use a remote registry to deploy to production, not something from a local docker graph
_From @bacongobbler on June 26, 2015 23:38_ I guess there's no true need to remove it. The motivation to remove `deis pull` is that it's a giant hack to pull...