Peter Kazazes

Been struggling getting a (huge) sync to complete for days as it kept starting from scratch on network failure. Confirming that this bug is still present as of bc38c2a879305ffd3cdd4f025f4161b430e79150.

[The way s3cmd handles paths in a sync](https://github.com/s3tools/s3cmd/blob/bc38c2a879305ffd3cdd4f025f4161b430e79150/s3cmd#L1088-L1131) isn't really intuitive and doesn't seem to be documented anywhere. Perhaps something like `rsync`'s trailing slash implementation would be better?

My 2¢ deployment, multistage, alpine DF: ```Dockerfile FROM node:13 as base RUN yarn global add node-gyp typescript@3 lerna ENV SERVER_PKG=packages/server ########################################################## FROM base as monorepo-base WORKDIR /app COPY yarn.lock package.json...

@jasonkuhrt How much would it differ from what's posted above? Besides fixing nexus version? @iherger make sure your package paths are correctly defined in the `ENV` statements.

It's private. Is yours public? Happy to have a look.

Sure. Give me an hour.

@blazestudios23 [here you go](https://github.com/kazazes/nexus-prisma-docker).

Could you provide a repro? Did it work in the example repo above?

Typescript was building to `.nexus/build`. You can specify the output location in your tsconfig and adjust your start script to match. ```diff diff --git a/package.json b/package.json index efa4067..90615bd 100644 ---...

`node_modules/.nexus` should contain the ts build cache. `$PROJECT_ROOT/.nexus/build/api` would contain the build output in a project that doesn't specify an outDir, not the node_module directory.