-
-
Notifications
You must be signed in to change notification settings - Fork 281
New Vite plugin option and behavior #1079
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
Thank you. Could I ask you to elaborate a bit more for the reader who wants to use it in the docker? Do I need to configure docker in any way ... or how to get it running? Just briefly, but it will avoid a lot of questions. I don't use docker, so I'm not familiar with it. |
|
Done, I briefly explained some of the necessary configurations for docker development. I didn't include any steps to run and build containers because it is assumed the user knows how to do that. I included a link to the docker docs on how to expose ports, that is directly related to configuring vite. |
|
I didn't have time to elaborate more on why it's assumed the user already knows how run containers. By the time the user realizes that extra Vite configuration is needed to access the dev server from outside the container, they already have their containers built and running. |
ce58f8e to
e41931c
Compare
f0f730d to
3881b35
Compare
83b7b11 to
4204814
Compare
Update Nette Docs to highlight new Vite Plugin options and behavior.