I can bring up webhooks.site if that all I do in docker.
I have another docker-compose that has a customized redis which I want to run at the same time.
Once I bring up the second docker-compose there must be a redis conflict that causes webhooks.site to terminate.
I tried to configure the webhooks.site docker-compose to use a different port, telling redis that it is to use some other port . i.e. 6803.
However, I can't seem to configure the other service to use the new port. The logs still think it 6379
Anyway,
this docker-compose would be nice to be self contained, with a private redis instance and easy to configure if other folks have a conflict with the port that this new one would have.
I can bring up webhooks.site if that all I do in docker. I have another docker-compose that has a customized redis which I want to run at the same time.
Once I bring up the second docker-compose there must be a redis conflict that causes webhooks.site to terminate.
I tried to configure the webhooks.site docker-compose to use a different port, telling redis that it is to use some other port . i.e. 6803.
However, I can't seem to configure the other service to use the new port. The logs still think it 6379
Anyway, this docker-compose would be nice to be self contained, with a private redis instance and easy to configure if other folks have a conflict with the port that this new one would have.
I think I have a working version here