Emilien Devos

Still missing custom scripts on georchestra gateway

I'm closing this issue in favor of a separate one in https://github.com/georchestra/georchestra-gateway/issues/127

> Issue was witnessed originally on MEL's deployment with the gateway (internal issue GSMEL-223) MEL is using kubernetes not docker compose. The env has been added back in november for...

hello @hpwjnijs did you have time to split the PR :)? thank you

Ha you are using Windows? We have not validated that this docker composition works on Windows. You should use WSL for Linux support, maybe it will work better: https://learn.microsoft.com/en-us/windows/wsl/install

Please try in a Linux environment. In a VM or with WSL (https://learn.microsoft.com/en-us/windows/wsl/install).

@arnaud-morvan you mean that by setting `COMPOSE_PROJECT_NAME=docker` in the .env file, the problem would be solved?

We can't alter the docker compose name, otherwise an existing install will lose all the volumes, as the volumes names are based on the docker compose project name.

Would rather keep the docker compose project name as "docker" in order to have less friction to the existing users. It's not like it's going to matter a lot. If...

Note: we will need to add a check dependency on rabbitmq.