Stream: inferno
Topic: IG persistence
sean zitello (Nov 12 2020 at 21:57):
Using the 'app' disto with docker-compose build, start, stop. POST igs works well and I can GET igs-by-profile. After restart however, they are not there and I do not see where they may be n written to disk. Is there a way to make them persist across restarts?
Reece Adamson (Nov 13 2020 at 18:06):
By "'app' distro" I'm assuming you mean this library which is infernocommunity/fhir-validator-service on DockerHub. This is the container referenced and used by inferno in its own docker-compose. It's similarly used by the fhir-validator-app.
I haven't tried it myself, but you should be able to achieve that using Docker volumes and mounting it at the default cache location in the container (~/.fhir IIRC, but might be worth poking around in the container to be sure).
I'd be curious to hear if you have any success with this and we'd happily take a documentation update if you do. Otherwise, we'll keep it in mind to check out ourselves at some point.
Some (potentially) help links to Docker docs:
sean zitello (Nov 17 2020 at 17:12):
Reece Adamson said:
I haven't tried it myself, but you should be able to achieve that using Docker volumes and mounting it at the default cache location in the container (
~/.fhirIIRC, but might be worth poking around in the container to be sure).
I don't see the package.tgz file or any of its profiles drop into /root/.fhir. The only new files I find after the POST are in /sys/kernel and /proc. All in memory then?
Reece Adamson (Nov 20 2020 at 16:21):
Yup all in memory then. I think the only ones that might be cached are those selected from the dropdown which come from the FHIR NPM package server. Something that we could look into at a later date or talk to the developers of the FHIR core libraries about (I know they've been doing a lot of work developing similar capabilities into the core).
Last updated: Apr 12 2022 at 19:14 UTC
