Hendrik Kunert

Maybe a better solution for the PortMapping would look like this: ``` enum Protocol { Tcp, Udp, Sctp } struct Ports { host, container } struct PortMapping { protocol: Protocol,...

I ok, now this makes sense. I could imagine two interface to get the mapped host port. Either something like: ``` rust enum Port { Tcp(u16), Udp(u16), Sctp (u16) }...

> What I am trying to say is: Can we maybe just leave the mapping API as is and simply search for the mapped port in the `PortMapping` response and...

Hi, the current solution should be fully backward compatible. I think it still needs some refactoring and some test, but then it should be ready to go. Would like to...

Now, only additional documentation and some test are missing.

I have tried it with my original use case and it seems to work as expected. But, I think the `RunArgs::with_mapped_port()` needs to be more ergonomic to use.

I think wrapping port in an Enum like below could work: ``` enum PortMapping { Tcp(Port), Udp(Port), Sctp(Port) } ``` After looking up the [Docker docs](https://docs.docker.com/engine/reference/commandline/run/#publish-or-expose-port--p---expose) I realized that the...

Seems to work now, but I can't really tell what fixed it. Either changed compiler flags, or the overall build system was messed up. We had a hard time to...

I don't know, maybe throw an error or ignore functions completely, but the patch output should comply with the RFC.

I have a similar issue. Does calling `cap production unicorn:stop` and then `cap production unicorn:start` is working for you?