David Heinemeier Hansson

What can we do to improve the error messages? They're really quite rough right now. Like if I change "servers" to "server", I get: `ERROR (Mrsk::Configuration::Error): The property '#/' did...

If I change builder/args to builder/arguments, it doesn't complain. Is there a way to make a list of properties exhaustive?

Think we might need some more exhaustive testing.

I'd solve that by letting your CDN be the cache of the old assets. Not going to introduce the complication of sharing assets between containers into MRSK. Assets are set...

Actually, I see what you mean. That you serve HTML from a new version of the app, which then triggers a request for a new asset, which hits the CDN,...

I don't think there's an issue in the other direction when you use a CDN that'll cache all old assets, and you ensure that the CDN uses the first-to-restart app...

Yes, that's my view. This is a problem better handled at the CDN. This is how we keep MRSK small and light. Realizing that it's NOT a full-stack deployment framework,...

Feel free to explore it! Like the sound of it.

Feel free to investigate 👍. If something simple could be concocted, I could see it being part of MRSK directly. But please do investigate.

Please do investigate. I think it's going to be rather complicated to have good caching layer dynamics without running a whole docker image repository on the server, and that has...