Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
Added docker command to force the Docker container to rebuild the db with any modifications.
  • Loading branch information
sah0017 authored Feb 14, 2025
1 parent e55edcb commit 8d722c8
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -149,6 +149,13 @@ _Note_: if changes are required for the database, you can reset the database wit
```
docker compose down -v
```
If ```docker compose build --no-cache``` still creates the same db despite changing how the database gets created, try
```sudo docker-compose down --rmi all --volumes``` (and then rebuild it all). The difference is that the first one
recreates the images, but that does not mean the volumes (location of persistent data that docker manages for the images)
are cleaned up. The second command frees up all the resources including volumes (yes even the downloaded packages for
the image are gone); that way the db is forced to run through whatever code you made instead of using something old.
The second command takes a bit since it wipes everything then you have to run ```docker compose build``` to make it all again.


When the front end is finished compiling, it should show a link, namely: `http://localhost:3000`.
Simply open this link in your browser and use an appropriate login.
Expand Down

0 comments on commit 8d722c8

Please sign in to comment.