You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @nktnet1, just a quick thanks for making this setup openly available. I stumbled here with the question "how to run migrations in a Docker/Turbo repo setup". Using a dedicated migrations service in the database package was the key for me. 👍
P.S: The current Dockerfile setup also included the non-purged directories. Maybe this is important for your use-case. For me introducing a last layer made the Image shrink from 1.7GB to 500MB ;)
Something like this:
FROM base AS runner
COPY --from=builder /app/out/full/ .
RUN npm install
CMD ["/bin/sh"]
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hey @nktnet1, just a quick thanks for making this setup openly available. I stumbled here with the question "how to run migrations in a Docker/Turbo repo setup". Using a dedicated migrations service in the database package was the key for me. 👍
P.S: The current Dockerfile setup also included the non-purged directories. Maybe this is important for your use-case. For me introducing a last layer made the Image shrink from 1.7GB to 500MB ;)
Something like this:
All reactions