Erica Kastner
Erica Kastner
@seamusabshere ``` dkastner@arrakis:~/cage/examples/rails_hello$ cage source ls coffee-rails https://github.com/rails/coffee-rails.git Available at src/coffee-rails (mounted) rails_hello https://github.com/faradayio/rails_hello.git ``` The "mounted" note is hard to see at a glance. Also, the multiline format makes...
This is the same kind of format `docker ps` uses
I threw together a way to customize what happens when a consumer fails. By default a nack is always sent. https://github.com/dkastner/hutch/commit/e9e3a1fb7ed038b88cab47197fd7824b5fb46558
No I found another way to set up routes
+1 on this, I've been using this branch for several months because I like to store developer ssh keys in my user data bags.
One catch I just found is that compose 2.1 didn't have the `start_period` option for `healthcheck`. So we may want to: a) go straight to 2.3, or b) start working...
I mean, ultimately, my sense of perfectionism would like to see this crate intelligently handle all compose versions.
I think doing a full datamine is something a CI system would be good at - the rest of the test can just test logic of specific things, and hopefully...
At this point I fear we start venturing into the realm of basically reinventing `docker-compose` (what's next, parsing email? 😉 ). This is how docker-compose implements its `ps` command -...
I guess what I'm saying is, is a global `ps` important enough to start digging into raw docker land, or can we get by with per-pod `ps` that just outputs...