Improve docs so people who would like to work with docker can find the documentation.
Is this really in scope for Svelte documentation?
@pngwn nope, it's got nothing to do with Svelte.
Just start the SSR server inside a node container and copy the assets and you're good to go.
Or if you're not using SSR, just use NGINX or http-server-spa to serve your static files.
OP is just lacking DevOps knowledge.
The one area where this may be applicable is in doing Svelte development in a container (with local volume mapping). Warnings around fsevent, or deprecation messages can really throw you off. I think the fix here would primarily be a Docker Compose example (YML, Dockerfile).
This doesn't have anything to do with Svelte, it is slightly more relevant for Sapper, but even then it's not the goal to document every possible deployment strategy.
I'm going to close this bug and open my mind to the possibility of a PR or the sapper-template project which documents container-based deployments.
Most helpful comment
@pngwn nope, it's got nothing to do with Svelte.
Just start the SSR server inside a node container and copy the assets and you're good to go.
Or if you're not using SSR, just use NGINX or http-server-spa to serve your static files.
OP is just lacking DevOps knowledge.