Is this a bug??? I had to do something unusual with my Dockerfile.dev and docker-compose.yaml to get v2 working in Docker and it feels off #17825
Unanswered
ohmeow
asked this question in
General - Components / Directives / etc
Replies: 2 comments
This comment has been hidden.
This comment has been hidden.
-
Vite requires index.html as an entrypoint. Why do you want to run the dev server in Docker? Also, the easiest way is just to copy the project and install/run it:
If building for production, you need to look into multi-stage builds. I can give you a simple example if you'd like. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What happened?
So its been awhile since i've spun up quasar within docker for local development. After battling things for a few hours ... this is what I came up with. But I'm wondering ... is there a better way (and why in the hell do i have to include index.html for things to work :))?
Dockerfile.dev:
docker-compose.dev.yaml
If anyone has any thoughts on how to improve this I'd love to hear. Thanks much!
What did you expect to happen?
I expect this to be sufficient in my Dockerfile.dev:
Reproduction URL
NA
How to reproduce?
N/A
Flavour
Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)
Areas
Quasar CLI Commands/Configuration (@quasar/cli | @quasar/app-webpack | @quasar/app-vite)
Platforms/Browsers
Chrome
Quasar info output
Relevant log output
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions