Flavio Stutz
Flavio Stutz
HTTP routes could be got from https://raw.githubusercontent.com/ispysoftware/iSpy/master/XML/Sources.xml (https://www.ispyconnect.com)
Ok. I’ll take a look. Thanks! Sent from my iPhone > On 23 Feb 2020, at 15:05, Brendan Le Glaunec wrote: > > > I would indeed appreciate a...
@mikesir87 I had the same sensation when going from Swarm to Kubernetes or pure ECS. Swarm really nailed this problem in a seamless way :) Maybe we can use AppMesh...
> `routing` might indeed be a more generic noon for this purpose, and we could then have nested attribute to define if those are actually exposed externaly (aka ingress) or...
> ```yaml > services: > mytest: > image: mytest:1.0.0 > ports: > - target: 5000 > ingress: > # string syntax > - http://mytest.org > # struct syntaxt with `url`...
> On the flip side, this could be crossing into the area of service discovery - which (arguably) is better left to a specialised service discovery container 🙈 AppMesh services...
Using compose ["deploy" configuration](https://github.com/compose-spec/compose-spec/blob/d1a1bfdf64ae9500fd30b7412fc3e851ae6857f8/deploy.md) is surely the way for automatic rollout scenarios. And this is the most common/simpler way to update a container. But in production in various cases we...
@ndeloof extending your proposal, we could add a "weight" param that could be used to disambiguate routes and handle some A/B load scenarios. For example: ```yaml services: foo1: ... routes:...
+1 here! I am configuring a Ceph cluster to run exclusively on Swarm. It has a recent feature for searching for monitor nodes using SRV records and I did miss...
We created a RTSP relay (https://github.com/flaviostutz/rtsp-relay) that could be used as a reference based on FFMPEG. The problem with this is that it recodes the stream, consuming 50% CPU for...