A common deployment pattern for the IBM FHIR Server is to run the Application Server behind a reverse proxy (e.g. OpenShift Route, Kubernetes Ingress, NGINX or API Gateway). By default, the IBM FHIR Server runs under the https://localhost:9443/fhir-server/api/v4 context root and URI. With a modest configuration change, one can change to a context root (baseUrl) or use the X-FHIR-FORWARDED-URL to forward the incoming url to the IBM FHIR Server (expected to be from a trusted reverse proxy).
The IBM FHIR Server stores resources in the PostgreSQL database and uses a relational model to store historical FHIR Resource and enable search on the latest FHIR resources. The resource data is spread in a relational model that is occasionally tweaked in order to improve search or optimize the retrieval using the relational model. This article outlines debugging with VACUUM on Postgres.
This article outlines how you should sync tags across repositories.
Determining Function Signatures with Postgres
When I wanted to deploy my key to [openpgp](keys.openpgp.org), I hit the issue where it said `No keyserver available`
If you hit this issue, per the GitHub community it’s a Windows issue that can be worked around with a Pagefile. link
[ERROR] OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000700000000, 553648128, 0) failed; error=’The paging file is too small for this operation to complete’ (DOS error/errno=1455)
My team has been running more workloads on IBM Cloud, more specifically with IBM Db2. Our daily tools are slightly different to work with in the cloud, less administrative access and tools we can access on the host – db2batch, db2advis, db2expln and other native tools. That’s when I ran across some great references that lead me in a direction that works for my team. Create a User (with Password) Catalog the Remote Database Run db2expln Login to the IBM Cloud console Click Open Console Expand Settings Click Manage Users Click Add Click Add User Enter the relevant details for…