Sebastian Wilzbach

> Due to caching a next page load is just 4KB. Is that really needed? What are the benefits. I currently don't see any latency issues. Yes, we have an...

Hmm, the exception in the HTTP log is: ``` object.Exception@../../../.dub/packages/vibe-core-1.4.1/vibe-core/source/vibe/core/net.d(72) Failed to lookup host 'is.gd'. ---------------- ??:? [0x89aa9e] ??:? [0x8ba7aa] ??:? [0x8a62bd] exception.d:516 [0x46a5c4] exception.d:436 [0x418d35] net.d:72 [0x7237e6] net.d:32 [0x723231]...

The only PR that we merged within the last days was an update of the release compiler :O https://github.com/dlang-tour/core/pull/686

> Perhaps the tour is being throttled or blocked by is.gd? No I can reach them fine from the host (same IP) and even when ssh-ing into the Docker image....

Manually: https://github.com/vibe-d/eventcore/blob/abdbc91c4bf1159eaed125ad7c7a5a7e613aa8e1/source/eventcore/drivers/posix/dns.d#L60 I opened another PR to deploy the vibe.d version of libevent (https://github.com/dlang-tour/core/pull/710), but if that doesn't work I'm out of ideas.

So switching back to libevent worked, but I'm not sure how to report the issue because I can't reproduce the error locally (hell - I can't even build the release...

Additionally, it could even go one step further: use the defined actions and generate all endpoint routes with dummy implementations for the most popular languages (e.g. Python and Node).

Similarly, it would be helpful if `omg subscribe` could attach to a running container too, s.t. we can easily test multiple subscribe endpoints.

I think for now it's okay to error when the user specified different environment variables in the `omg run publish`command.

Bumping the priority here as there's no (easy) way without this to test OMS events. Even for our templates we had to add fake events to be able to test...