LinuxForHealth Connectors for Inbound Data Processing
Type | Link |
---|---|
π¨ Bug Reports | GitHub Issues Tracker |
π Feature Requests & Ideas | GitHub Issues Tracker |
β Questions | LFH Slack Workspace |
π Roadmap | ZenHub Board |
The LinuxForHealth documentation includes architectural overviews, development guidelines, and deployment options.
The LinuxForHealth Connect development environment requires the following:
- git for project version control
- mkcert for local trusted certificates
- Python 3.8 or higher for runtime/coding support
- Pipenv for Python dependency management
- Docker Compose 1.28.6 or higher for a local container runtime
For Windows 10 users, we suggest using Windows Subsystem for Linux.
For s390x users, please read these instructions before beginning.
For arm64 users, please read these instructions before beginning.
git clone https://github.com/LinuxForHealth/connect
cd connect
pip --version
pipenv --version
pip install --upgrade pip
pipenv sync --dev
pipenv run pytest
docker-compose up -d
docker-compose ps
pipenv run connect
For s390x users, please follow these instructions to run connect.
Browse to https://localhost:5000/docs
to view the Open API documentation
Perform this step to create new certificates for connect and connect services. The creation of new certificates is not required, as connect contains a set of default certificates for SSL. If you do create new certificates, you must rebuild the connect docker image, as described in the next section.
./local-config/install-certificates.sh
For more information on connect and HTTPS/TLS support, please refer to the local cert readme.
For s390x users, please read these instructions.
For arm64 users, please read these instructions.
The connect docker image is an "incubating" feature and is subject to change. The image is associated with the "deployment" profile to provide separation from core services.
The connect image build integrates the application's x509 certificate (PEM encoded) into the image.
The APPLICATION_CERT_PATH
build argument is used to specify the location of the certificate on the host machine.
If the APPLICATION_CERT_PATH
build argument is not provided, a default value of ./local-certs/lfh.pem is used.
docker build --build-arg APPLICATION_BUILD_CERT_PATH=./local-config/ -t linuxforhealth/connect:0.42.0 .
The docker-compose command below parses the build context, arguments, and image tag from the docker-compose.yaml file.
docker-compose build connect
docker-compose --profile deployment up -d
LinuxForHealth Connect utilizes the black library to provide standard code formatting. Code formatting and style are validated as part of the LinuxForHealth connect ci process. LinuxForHealth connect provides developers with an option of formatting using pipenv scripts, or a git pre-commit hook.
pipenv run check-format
pipenv run format
pipenv run pre-commit install
black................................................(no files to check)Skipped
[black-formatter 95bb1c6] settings black version to latest release
1 file changed, 1 insertion(+), 1 deletion(-)
black....................................................................Passed
[format-test c3e1b4a] test commit
1 file changed, 1 insertion(+)
black....................................................................Failed
- hook id: black
- files were modified by this hook
reformatted connect/routes/api.py
All done! β¨ π° β¨
1 file reformatted.
LinuxForHealth connect runs on amd64, arm64 & s390x platforms. From the top-level connect directory, use this command to build, tag and push the multi-arch image that supports all these platforms:
docker buildx build --pull --push --platform linux/amd64,linux/arm64,linux/s390x --build-arg APPLICATION_BUILD_CERT_PATH=./local-config/ -t linuxforhealth/connect:0.42.0 .
That's it - you can now run docker pull linuxforhealth/connect:0.42.0
on all 3 LinuxForHealth connect platforms.
Type | Link |
---|---|
π° Documentation | LinuxForHealth Docs Site |
π° Documentation | IPFS |