On Sat, Jan 25, 2020 at 04:59:42PM +0000, William Dauchy wrote: > On Fri, Jan 24, 2020 at 4:40 PM William Lallemand > <[email protected]> wrote: > > What we are trying to do with the certificates and the CLI, is to be able > > to do > > a 'reload' of the filesystem, but without reloading haproxy. You could > > imagine > > an haproxy helper (let's say `haproxyctl cert reload`) that will scan the > > changes on the filesystem and apply the changes without launching a new > > process, so it could be a file removed, updated or added. > > just being curious here, do we assume this will not be compatible with > chroot usage? >
There is no limitation with the chroot since the file is uploaded over the CLI. If you use the "set ssl cert" and "commit ssl cert" commands over the CLI the chroot option is not suppose to affect these. Do you have an example that might be a problem? I don't see how it could but I can be wrong. -- William Lallemand
