Skip to content
This repository has been archived by the owner on Oct 11, 2024. It is now read-only.

Lost order in db when restart container #64

Closed
alessiofx opened this issue Jun 12, 2019 · 3 comments
Closed

Lost order in db when restart container #64

alessiofx opened this issue Jun 12, 2019 · 3 comments

Comments

@alessiofx
Copy link

When you restart the container all the orders on the database are lost.
You can fix this problem.

@fabioberger
Copy link
Contributor

You can do this by mounting a volume to the Docker container where the database.sql file is stored so that it persists across container re-starts. We can add instructions to the README on how to do this. Thanks for the suggestion.

@dekz
Copy link
Member

dekz commented Jun 28, 2019

This will be possible once #65 is merged. Currently you can mount from local but not allocate a persistent volume.

@dekz
Copy link
Member

dekz commented Jun 29, 2019

A Docker volume can now be attached to the backend to allow for persistent orders through restarts

backend:
    ...
    volumes:
      - backend-database:/usr/app/src/db

@dekz dekz closed this as completed Jun 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants