Hmm dealing with an issue, anyone have ideas?

Essentially, turborepo has a “prune” command to create an “out” folder that you gen/use in your Dockerfile, which works fine, but a caveat here is you have to run your dockerfile from the root turborepo dir, rather than running it from inside the package (1/?)

aspiring shrimp farmer ~ living life ~ prev // intern @ Bloom (YC W21)

- push entire monorepo then somehow use a different Dockerfile based on app/env

- somehow get the neccesary files for a standard Dockerfile (I.e. pnpm-lock.yaml) w/o using the prune command/relying on turborepo, then just pushing that as a standard dockerized app to EBS

No clue how to go about either though :)

Should probably preface this with the fact that it’s 1am and I’ve gotten dogshit sleep all week. Perhaps I’m being stupid about this all, I guess we shall see tomorrow

Goal here is to deploy each package/app to its own elastic beanstalk app/environment, however, to deploy on EBS, you upload a ZIP/artifact w/ your package (and the Dockerfile within), if it’s just the ZIP’d package, it doesn’t have any of the turborepo context.

My two ideas thus far have been:
(2/?)