openimis/openimis-be_py — reverse-engineered prompt

Build me a working openIMIS backend that I can run locally first and then deploy later. I want it to feel like a real backend assembly, not just a skeleton. It should start cleanly with Docker, read its settings from environment variables, support development and production modes, and let me use Postgres by default with the option for MSSQL or a simple no database fallback for local testing.

Please wire up the main API layer, including the GraphQL side that this repo hints at, expose everything under a configurable site root, and make sure migrations, demo data loading, logging, caching, email settings, scheduled jobs, async processing, and OpenSearch support are all hooked up in a sensible way. If Sentry and remote user auth are enabled in env settings, those should work too.

I also want a simple setup flow with an example env file, sane defaults, and a clear README so someone lightly technical can get it running without guessing. Look up current docs online if you need to.