streamlined configuration options

[cukal]

Excellent tool, it really provides good insights, we're using it on several production environments because it's such a great addition to our Kafka setup. When we deploy it we first spin up the h2 db in server mode and use a Python script to execute SQL updates to set all the environment specific values (clusters, views, users, ...) before starting kafka-webview. This approach runs as part of our automated deploy chain and updating h2 this way just takes a few seconds to complete but it's only valid for the 1.0.5 specific h2 backend. A more streamlined approach would be welcome to guard against future updates or model changes.

Once again, thanks for this really great application!

[elliots]

I would also appreciate simpler configuration.

I use this in docker-compose as part of a development environment that constantly goes up and down. I'd like to be able to

• Disable users completely, or failing that set a user/password
• Add a cluster
• Add views all using environment variables, or with a config file if thats not possible. Which it probably isn't :)

(and again also, this application really is great! 👍 )

[cukal]

@elliots you could create a bootstrapper/wrapper that you start up instead of webview that grabs environment values, mounts the h2 db, executes sql with the env vars as variables and sets up users, cluster, views, ... in the h2 backend and next start webview itself?

[Crim]

Any ideas how to handle custom kafka deserializers that require jars to be included in the class path as part of some configuration file?

[Crim]

If the environment is generally static after your initial configuration (IE you don't need to create dynamic users, views, etc.. on container start). Could you boot the container once, set it up how you need it, and then snapshot it using the commit command? https://docs.docker.com/engine/reference/commandline/commit/

And then just run from that saved state?

[Crim]

@elliots I've just released a new version (2.0.0) that allows for disabling user authentication entirely. It's not a complete solution for your needs, but may help some :)