As part of my GrowthBook POC, we set it up growthbook instance on a EC2 instance, with little to no modification of the

docker-compose.yml

that came with the git repo. And we defined data sources and metrics using the web UI forms. I am guessing that all the meta data is being stored in mongoDB. However, when we restarted the docker container using the following commands , I lost all the metrics, exposure and other definitions. I also lost users who registered. I am sure there is a better way to stand it up so as to persist across restarts? Any suggestion is appreciated

docker compose down 
docker compose up

You want to mount a persistent volume for the MongoDB container. Or, switch to using a hosted service like MongoDB Atlas instead.

got it. can i use s3 as a persistent volume? will this work?

depends_on:
      - mongo
    environment:
      - MONGODB_URI=<mongodb://root:password@mongo:27017/>
      - APP_ORIGIN=${APP_ORIGIN}
      - API_HOST=${API_HOST}
    volumes:
      # - uploads:/usr/local/src/app/packages/back-end/uploads
      - uploads:
          S3_BUCKET:${S3_BUCKET}
          S3_REGION:${S3_REGION}
volumes:
  uploads:

You can use that for file uploads, but not for MongoDB.

Okay. Thanks.

There are 2 directories to persist. uploads is only for file uploads (e.g. adding screenshots of experiments). The other directory you need is on the

mongo

container and not the growthbook one. In the mongo container, data is stored at

/data/db

so that needs to be persisted

Thanks for your help.