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
Not sure this is the right place to create the issue but what I'm asking happens on your servers and is related to Docker :).
I use a monorepo with NPM workspaces, and I have issues deploying my actor because of it.
In order to selectively install my actor using npm install --workspace=my-actor, I would need the actor id to be available in the Dockerfile. Is it something you could add?
This change combined to this one apify/apify-cli#277 would basically enable basic support for NPM workspaces monorepo.
Love the project, keep going 👍
The text was updated successfully, but these errors were encountered:
jeanbmar
changed the title
Pass actor id to container when running Docker build
Expose actor id in container when running Docker build
Aug 6, 2022
Hey there,
Not sure this is the right place to create the issue but what I'm asking happens on your servers and is related to Docker :).
I use a monorepo with NPM workspaces, and I have issues deploying my actor because of it.
In order to selectively install my actor using
npm install --workspace=my-actor
, I would need the actor id to be available in the Dockerfile. Is it something you could add?This change combined to this one apify/apify-cli#277 would basically enable basic support for NPM workspaces monorepo.
Love the project, keep going 👍
The text was updated successfully, but these errors were encountered: