issue deploying vue frontend changes about full-stack-fastapi-template HOT 3 CLOSED

Thanks @kurtrottmann !

@vishalhkd if you are running your frontend in the Docker container, you need to build the image first docker-compose build and then you can docker-compose up -d.

But it will take longer than developing locally, and won't do live reloads as with Vue CLI. My suggestion is to install Vue CLI and run the UI vue ui, and run your project from there during development. It's normally a lot more efficient.

from full-stack-fastapi-template.

Hi, I think this behaviour is normal as mentioned in README.md:

For example, the directory with the backend code is mounted as a Docker "host volume" (in the file docker-compose.dev.volumes.yml), mapping the code you change live to the directory inside the container. That allows you to test your changes right away, without having to build the Docker image again.

While for Frontend developement it is recomended to use a live server (npm run serve).

Notice that this live server is not running inside Docker, it is for local development, and that is the recommended workflow. Once you are happy with your frontend, you can build the frontend Docker image and start it, to test it in a production-like environment. But compiling the image at every change will not be as productive as running the local development server.

If you don't want to use the live server and see your changes, you must to destroy the frontend container and recreate it each time (docker stop frontend_container_name, docker rm frontend_container_name, docker-compose up -d).

from full-stack-fastapi-template.

Assuming the original issue was solved, it will be automatically closed now. But feel free to add more comments or create new issues.

from full-stack-fastapi-template.