DBDelve
Dive deep into your data. A fast, native, multi-engine database client written in Rust. Free and open source, no telemetry.
翻訳待ち
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗emuhealth is a fork of emulate focused on healthcare and life science APIs. It includes every emulate service today, and health emulators are on the roadmap.
Local drop-in replacement services for CI and no-network sandboxes. Fully stateful, production-fidelity API emulation. Not mocks.
Synthetic data only. emuhealth is a development and testing tool. Never load real patient data or other protected health information (PHI) into it. Emulators keep data in memory or local files with no access controls, audit logging, or encryption.
npx emuhealth
Or run the container image, published to GitHub Container Registry with every release:
docker run --rm -p 4100:4100 ghcr.io/emuhealth/emuhealth start --service fhir --host 0.0.0.0
docker run --rm -p 4100-4130:4100-4130 -v "$PWD/emuhealth.config.yaml:/app/emuhealth.config.yaml" ghcr.io/emuhealth/emuhealth
All services listen on IPv4 loopback (127.0.0.1) by default. No config file needed:
http://localhost:4000http://localhost:4001http://localhost:4002http://localhost:4003http://localhost:4004http://localhost:4005http://localhost:4006http://localhost:4007http://localhost:4008http://localhost:4009http://localhost:4010http://localhost:4011http://localhost:4012http://localhost:4013Health and life science services use a fixed range starting at http://localhost:4100. Each health service keeps its port no matter which other services run or how many upstream services exist.
This is the beginning of the README. Read the rest at the original. Read the full README ↗