What is there to improve on in the proxy? From what I've seen in the suggested links, we're already following all the best practices as far as the Dockerfile is concerned.

@jamesL92 Im gonna close this and reopen specific features for the @configu/proxy.
teaser:

• Boot @configu/proxy from @configu/cli - configu proxy command
• Enable store hooks at @configu/proxy - POST /hook [updated keys]
• Enable SSE at @configu/proxy - Interval based, Hook based

If you have more ideas I would more then happy to hear them :)

Hmm....I don't want to suggest any ideas just yet as it depends on what direction the eventual goal of @configu/proxy is intended to be. For example, is the idea that it can become a lightweight version of the Configu cloud server (e.g. for experimentation/dev environments) or is it that it eventually becomes a RESTful proxy to all the different config stores that Configu integrates with?

It's something we can discuss in more detail tomorrow, but I very much like the direction this is heading.

There's another OSS product I've used with a similar style of CLI integration called temporal - not sure if you've come across it but might be worth looking into in terms of what's possible.