Comment 1 for bug 2045468

Hi Christoph and thanks for this report!

We're aware of this and some other current limitations of this setup and are currently designing some related improvements. We will likely remove the current related documentation until this is addressed.

It should be possible to work around the db credentials issue. See:

    sudo snap get snap-store-proxy internal.snaprevs.db

and

    sudo snap get snap-store-proxy internal.snapauth.db

`sudo snap set ...` can be used to set the same connections string in all instances of the snap-store-proxy.

As for the registration. Only one proxy has to be registered. But others' config will have to be set based on the config of the registered one. `snap-proxy config` command can be used to both get and set all non-internal config options of the snap-store-proxy.

snap-store-proxy can be fronted with an external load balancer / reverse-proxy. However currently for it to function properly the scheme used between the end clients (devices) and the external LB has to be the same as the scheme exposed by the snap-store-proxy - meaning either http or https on both sides.