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
When using this module with simply running yarn run dev everything works perfectly, but as soon as we start using it within docker ( dev environment ), we get the wrong path on the generated files.
For example, for an app that is running inside a docker container and the whole app is mounted on this path /usr/src/app but the actually code on the machine is on this path /home/***/workspace/project, the generated files will use the docker mounted path /usr/src/app.
So maybe the solution is to use the relative path instead of the absolute path ?
Reproduction
Any simple project with the server-fn module running inside a docker container
Describe the bug
When using this module with simply running
yarn run dev
everything works perfectly, but as soon as we start using it within docker ( dev environment ), we get the wrong path on the generated files.For example, for an app that is running inside a docker container and the whole app is mounted on this path
/usr/src/app
but the actually code on the machine is on this path/home/***/workspace/project
, the generated files will use the docker mounted path/usr/src/app
.So maybe the solution is to use the relative path instead of the absolute path ?
Reproduction
Any simple project with the server-fn module running inside a docker container
System Info
Used Package Manager
yarn
Validations
The text was updated successfully, but these errors were encountered: