IlyaCredo
IlyaCredo
> [@Forceres](https://github.com/Forceres) if you are trying to connect to this service from another compose, you need to connect both to the same docker network > > so either define your...
> [@Forceres](https://github.com/Forceres) the only thing it does, is connect the container to coolify network, nothing more > > if it's there then the issue is elsewhere, what is the contents...
> [@Forceres](https://github.com/Forceres) the only thing it does, is connect the container to coolify network, nothing more > > if it's there then the issue is elsewhere, what is the contents...
> I think you have mis understood what the option means. Maybe it is poor wording, but it means connect to docker network named coolify > > So if all...
> @Forceres it does work on services as well. At least on the latest version beta409. > > If you have multiple destinations defined in coolify, it will ask you...
I think the problem with DNS names (my prometheus.yml has cadvisor:8081), but DNS name of the predefined network doesn't contain cadvisor. But it has 'prometheus' as DNS name in my...
That's not a lib problem, that's a dev problem like webhook validation, etc. It can be verified with that flow: ```python onWebhook(update): if update.pre_checkout_query: answerPreCheckoutQuery(ok=True) if update.successful_payment: // server-side verification...
any updates?
any updates on this?
I don't think that mechanism is so complicated and would lead to real performance degradation. The lib already has lots of checks, so one more or one less, it doesn't...