Looks good. I think the https connector will take a little more work, though! M. .
On 17 June 2018 at 15:12, Nick Couchman <[email protected]> wrote: > This was changed recently in the master branch: > > https://github.com/apache/guacamole-client/pull/300 > > It isn't in scope for the upcoming 1.0.0 release, but maybe for a quick > minor release after that. > > -Nick > > On Sun, Jun 17, 2018 at 09:49 Mark Nolan <[email protected]> wrote: > > > On a slightly different tack, but still relevant to keeping images up to > > date, we always have to customize the image to declare the https > connector > > and because we want to serve guacamole from the root context. > > > > Is there a preferred approach to this? Is it something that would be > useful > > to others? > > > > M. > > . > > > > > > On 17 June 2018 at 01:13, Nick Couchman <[email protected]> wrote: > > > > > On Fri, Jun 15, 2018 at 11:36 AM Tezarin <[email protected]> > > > wrote: > > > > > > > > > > > Hi, > > > > > > > > What would be a good practice for having these docker pull commands? > > Can > > > > we have a Dockerfile that does that? If so, can you please point me > to > > > some > > > > of your examples? > > > > > > > > > > > The Dockerfile is used to build the images, so you don't need this for > a > > > "docker pull" command. You'd just run the "docker pull" command after > a > > > new update of Guacamole is released, and it will pull the latest images > > > down for your containers. You'd then stop your Guacamole-related > > > containers and restart them, and it should use the latest-available > > image. > > > > > > -Nick > > > > > >
