uradibou, y a pas besoin de dire plus
| src | ||
| .dockerignore | ||
| Dockerfile | ||
| DockerfileDev | ||
| readme.md | ||
| run.sh | ||
| rundev.sh | ||
archi
we use docker
I will try to make a clean setup, so 2 docker files, one for quick tests during dev the other for production
the dev docker uses vite live update feature. to do that, it has a volume bind to it containing the code (src). this allows to be able to modify live without rebuilding the image nore re launching the container.
note on package-lock.json: package lock contains the exact versions of all the dependencie tree, it is generated by npm, but it is important to not regenarate it every time otherwise a dependency update could fuck the project. The package lock file in src/ comes from the dev docker, since src is used for bind volume, so when package.json is updated, it is necessary to run the dev docker to update package lock.