Is your feature request related to a problem? Please describe.
Я предлагаю добавить опциональный env с путем к docker-compose.yml или путями к нескольким docker-compose.ym (сейчас используются из deep-foundation/hasura и deep-foundation/deeplinks). Если путь не указан, то оставить текущуюю логику.
I propose adding an optional env with a path to docker-compose.yml or paths to multiple docker-compose.yml files (currently used from deep-foundation/hasura and deep-foundation/deeplinks). If the path is not specified, then leave the current logic as is.
Is your feature request related to a problem? Please describe.
Я предлагаю добавить опциональный env с путем к docker-compose.yml или путями к нескольким docker-compose.ym (сейчас используются из deep-foundation/hasura и deep-foundation/deeplinks). Если путь не указан, то оставить текущуюю логику.
Также можно просто использовать https://github.com/deep-foundation/deeplinks/blob/main/docker-prod/deep/docker-compose.yml для серверной установке. В этом случае, нужно править скрипты, вызываемые командой deeplinks, чтобы они брали https://github.com/deep-foundation/deeplinks/blob/main/docker-prod/deep/docker-compose.yml
I propose adding an optional env with a path to docker-compose.yml or paths to multiple docker-compose.yml files (currently used from deep-foundation/hasura and deep-foundation/deeplinks). If the path is not specified, then leave the current logic as is.
Alternatively, we can simply use https://github.com/deep-foundation/deeplinks/blob/main/docker-prod/deep/docker-compose.yml for server installation. In this case, scripts invoked by the deeplinks command should be modified to fetch from https://github.com/deep-foundation/deeplinks/blob/main/docker-prod/deep/docker-compose.yml.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response