Oh, right. I remember that discussion thread too. @ztraboo: Just a heads up that this might be another source of issues for you folks, since you’ve been looking into production performance lately. @Alecar’s fix for this was in the Olive release, though it’s a very small patch if you want to try to use it as well.
I can see the appeal of that. I guess the alternative would be to have each service build its production assets out to a shared volume, and have a separate static asset serving container running Caddy serving it out? It’s a little more cumbersome, but I think that could have a lot of upsides–a different domain would mean that we wouldn’t have to send cookies to it, for one.
@kmccormick pointed out to me that Tutor will be moving to gunicorn at some point, and it looks like that will force the issue since gunicorn doesn’t offer a file-serve option like uWSGI does.
Edit: Nginx-Unit is mentioned as another alternative in the ticket above.