In our company we have decided to use WikiJS with docker and to have a backup in GitLab also in a container.
The problem is that GitLab take a while to be ready and since that WikiJS is not able to pull from GitLab (which is not yet accessible) all content isn't load in WikiJS (/all is empty) except for the home page which is still accessible.
After checking manually that GitLab is ready, restart the WikiJS container make everything works, but we are looking for a more automatic process.
Currently we use a wait-for-it.sh to restart WikiJS when GitLab is ready, what is not recommended by Docker (see docker-compose doc here).
Expected behavior
According to docker-compose documentation what they recommend is to have a application that is resilient and do not have to wait for other services.
Maybe display what is inside repo directory locally while Git isn't accessible.
Actual behavior
In our company we have decided to use WikiJS with docker and to have a backup in GitLab also in a container.
The problem is that GitLab take a while to be ready and since that WikiJS is not able to pull from GitLab (which is not yet accessible) all content isn't load in WikiJS (/all is empty) except for the home page which is still accessible. After checking manually that GitLab is ready, restart the WikiJS container make everything works, but we are looking for a more automatic process. Currently we use a wait-for-it.sh to restart WikiJS when GitLab is ready, what is not recommended by Docker (see docker-compose doc here).
Expected behavior
According to docker-compose documentation what they recommend is to have a application that is resilient and do not have to wait for other services. Maybe display what is inside repo directory locally while Git isn't accessible.
Steps to reproduce the behavior
This is the docker-compose.yml: