Docker: Blink won't initialize if OIDC provider is still starting up. about blink

[JaneJeon]

Well, Blink expects everything to be "up" by the time it's connected. Connect/retry of OIDC really shouldn't be part of the application, and I suggest putting a short little script (e.g. wait-on, wait-for, wait-for-it) listening to the keycloak endpoint to make sure it is up BEFORE you start Blink.

Making sure "X" is started before "Y" and making sure it satisfies $condition_Z and the like starts to encroach on the boundaries of "orchestration" (e.g. with docker swarm or kubernetes), which is out of scope for this project.

Do look into the "waiting scripts" I pointed out above. They are the standard way ("best practices") of solving this problem, not just across link shorteners, but across cloud-native applications in general.