chgl

+1 for the proxy chart approach. Two more benefits are that it allows for updating the dependency chart version automatically using tools like renovate (see https://github.com/renovatebot/renovate/issues/5450#issuecomment-663185810 ;) and any additional...

I ran into the same situation as well, but this isn't a recent change but a bug in either your proxy server or the ApacheAddressStrategy implementation (whichever you prefer). It...

I tend to agree. I think a better place for the issue would then be https://github.com/hapifhir/hapi-fhir. I guess the fix would be if the `X-Forwarded-Host` already contains a port, then...

Thank you for the feedback and the confirmation that HAPI should generally work in such a scenario! >Just to confirm- Are you on the latest version of HAPI FHIR and...

Hi @psavva, not really, the issue is quite hard to reproduce. The best solution is to implement some logic in your client code which will retry failed requests. I have...

hi @keerthivasan-r unfortuntely I haven't had the time to further benchmark the hapi fhir server and test its scalability. I am currently doing some load testing using IBM's FHIR Server...

@tevariou unfortunately nothing yet :/ The hand-wavy response I can give for now is that none of the servers seem particularly fast, but there's constant work on improving it. I've...

Hm, it should build arm64 as well (https://github.com/hapifhir/hapi-fhir-jpaserver-starter/blob/master/.github/workflows/build-images.yaml#L15) it's also listed in the os/arch: https://hub.docker.com/layers/hapiproject/hapi/latest/images/sha256-4ce79b31a47b2be211405357ef433d2486aaf3e174fff3969172c5bf4b836400?context=explore You could try replacing the 'build' part of the docket compose file by instead directly...

Thank you for noticing, you are of course completely right and I think your solution is great - although eventually having the initContainer also check connectivity to any external db...

I commented on https://github.com/hapifhir/hapi-fhir-jpaserver-starter/pull/367 - which does the same but targets the master branch which will then trigger a chart release an will run the CI