Marios Andreopoulos

Try to set `KAFKA_REST_LISTENERS` to `http://proxy:8082`, and accordingly `KAFKA_REST_PROXY_URL` to the same value. Btw, exposing the broker port at 59092 won't work for your host. Clients will want to connect...

Please change `PROXY=True` to `PROXY=true` or `PROXY=1` as it is case sensitive.

I want to point out that this only serves to provide a false sense of security. Anyone who has access to Connect UI, can also hit the connect worker endpoint...

Unfortunately this is how Kafka Connect is coded. The ideal solution would be for this to be handled at the Connect level —so a kafka patch (connect is part of...

Hi @gunnarmorling, great work on Debezium! Just to add on what @Antwnis wrote, fast-data-dev essentially is kafka in a container. We package kafka, connect, schema registry, our kafka UIs etc...

Probably InfluxDB isn't at `127.0.0.1`. Each docker container has its own network, so `127.0.0.1` for Lenses Box refers to itself. If you run both Influx and Lenses Box as docker...

Hi. This is actually possible now, please have a look here: https://github.com/Landoop/fast-data-dev#configure-kafka-components As an example, to set `auto.create.topics.enable=true` (though this is the default setting anyway), you would add the env...

Thanks! I'll leave this to our web dev team, but I think it will be of lower priority for now.

Try to use the playground image: docker run landoop/fast-data-dev:playground It has two brokers and by default always running sample data (configurable via environment variables). We do not plan to support...

Hi @gihanpasindu, it's not possible anymore.