derby database

[bbhoss]

One of the biggest issues I've ever had amongst a bunch of deployed mirth instances was the use of the derby database. Last I checked MirthCorp didn't recommend using it in production, and I've certainly had issues running it there myself (found out the hard way). This has been years ago, and maybe it's gotten better, but for something like this we should probably expose a way to configure the database via ENV, or possibly some other method that uses etcd or something? At the very least it looks like sqlite is supported, which I'd be more apt to trust than derby.

[ForresGeek]

The "official" Mirth Appliances ship with postgres as their message store (i.e NOT DERBY). I'm new to all this docker stuff, but wouldn't it be possible to install a postgres docker, and then make the few (simple) changes to Mirth's config files to point at postgres rather than derby ??

[cancan101]

Correct solution would be docker compose using PostgreSQL and then a docker image for mirth. You can also use existing PostgreSQL rather than starting new. Should be as simple as config change.

[cancan101]

More info on config: https://gist.github.com/jgautsch/9157402#moving-from-derby-to-postgres