Migrate from Multibox to Aidbox
This guide shows you how to migrate from Multibox instance to few Aidbox instances
Let's say you have Multibox deployed locally. And you have a couple of boxes launched there.
fhirr4box
box with FHIR R4 versionfhirr5box
box with FHIR R5 version
To migrate them to Aidbox instance, you need to issue an Aidbox license for each box in multibox.
Stop Multibox instance
Docker compose file
Add two new Aidbox instances to docker compose file
If you use Aidbox configuration project, you should also pass BOX_PROJECT_GIT_TARGET__PATH and AIDBOX_ZEN_ENTRYPOINT.
.env file
As we specified AIDBOX_LICENSE, AIDBOX_FHIR_VERSION and PGDATABASE
for every Aidbox instance, we should remove it from .env file.
Multibox requires AIDBOX_SUPERUSER
env variable to be set. Aidbox instance creates admin user and root client resources at startup, and expects 4 env variables instead of one AIDBOX_SUPERUSER
:
Run Aidbox instances
Now you can run your aidbox instances
fhirr4box
will be accessible on http://localhost:8888
, and fhirr5box
will be accessible on http://localhost:9999
.
Talk to a Health Samurai Engineer
If you'd like to learn more about using Aidbox or have any questions about this guide, connect with us on Telegram. We're happy to help.
Last updated