Persist Fasten Database using volume mount

[Cookie-Monster-Coder]

Have the option to store the data persistently by mapping it in the volume section in docker.

  Fasten:
    image: ghcr.io/fastenhealth/fasten-onprem:main
    container_name: Fasten
    environment:
      - TZ=America/Chicago
    volumes:
      - /volume1/docker/Fasten:/opt/fasten
    ports:
      - 8080:8080
    restart: unless-stopped

[OhHeyAlan]

I tried to submit a PR yesterday to add a docker-compose file with a volume but I shouldn’t submit it w/o merging lots of other changes. I’ll submit one that’s simple for anyone to use later.

[OhHeyAlan]

Maybe its better to just post in a comment for now....

'docker-compose up -d'

http://localhost:9090

version: '3.4'
services:
fasten:
image: ghcr.io/fastenhealth/fasten-onprem:main
container_name: fasten
restart: unless-stopped
ports:
- 9090:8080
volumes:
- ./fasten:/opt/fasten/db/ #Creates '/fasten/fasten.db' within the folder containing the docker-compose.yml file.

[AnalogJ]

Hey @Cookie-Monster-Coder

This is actually intentional.
Fasten is early beta software and I expect the application functionality and database structure to change significantly as we iterate on the software.
Until we implement a database migration tool, I can't guarantee that the database structure will work between versions, and so I've attempted to side-step this problem by not explicitly documenting how to persist the Fasten database outside of the container (yet).

Once that database migration tool is written, and we release a v1 of Fasten (which is guaranteed to be backwards compatible), these instructions will be baked into the README.

I hope that makes sense?

[AnalogJ]

closing this issue, since volume mount instructions have been included in the Readme for a while.