SIGHUP support

[bls]

The proxy should reload configuration without restarting when SIGHUP is recieved.

[nhoughto]

How would that play into remote config sources like s3? would you have to signal it to reload remote sources too?

[bls]

Have not scoped out the interaction at this point, expect it would trigger a reload of local config, with either regular polling or (ideally) notifications used to reload from s3. In particular reloading S3 config it's not clear when you can assume it's in a consistent state for read. Any ideas appreciated.

…

On Wed, Jul 15, 2020 at 11:46 AM nhoughto ***@***.***> wrote: How would that play into remote config sources like s3? would you have to signal it to reload remote sources too? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#22 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABRXWVD6YCUCBAQPZ5EGQ3R3UDBFANCNFSM4O2BQYKQ> .

[nhoughto]

ah yeah good point, users / rules files being separate. obv s3 is atomic but the interaction between diff files isn't.

Rejig config to make 1 file self contained? 😬

Would what strat with notfications be? Reload 1 min after last notification? So a flurry of changes would all be picked up consistently? You could do the same with a s3 reload polling, look at mtime of file?