Ireneusz Szulc

Yeah, testing can be tricky. Maybe it'll be enough to unit test the SMTP interface with some mocks. I think it should be definitely an optional feature. Not everyone has...

@anders314159 > 1. Is there a failing example for this issue? A sort of. In case of requesting for too many CPU cores, like this: ```yaml resources: cpu_min: 10M #...

# Path rewriting breaks front-end apps Here's a detailed explanation why the problem exists due to path rewriting. It is common to many front-end apps, like Drupal, WordPress or pgAdmin....

In general, to address this issue, we need to find a way of putting additional information to HTTP request that allows Racetrack to distinguish a job, and dispatch the request...

Currently, the best way I see is to go with hostname subdomains. This would be an optional feature for extraordinary apps, working only with the infrastructure targets that supports it...

Formerly, I've run into the issue with Prometheus volume running out of storage, even though there was configured much lower retention size. Maybe that's a result of cardinality explosion.

I'm not sure if I get this idea and I can't imagine how it's going to work. Do you want to use Racetrack as a packager and to transform your...

Good reasoning. Just want to note that in the current design, PUB is the authentication gateway and it's the last place where the auth token is present. So Fatman may...

Good point. Docker registry is the service that Racetrack relies on. Instead, it should be moved to an interface and implemented by infrastructure plugins. However, plugins can only implement logic...

> Has this actually been the case? To be honest, it's just my conjecture. It's been proven that a single request to Racetrack v2 can be slower than v1 due...