3 ms·
Logging in to machines to update configs doesn't scale well. You often end up building your own framework/api "only" to edit the config file. Or paying $2500/i
by jbergstroem 10y ago
Logging in to machines to update configs doesn't scale well. You often end up building your own framework/api "only" to edit the config file.
Or paying $2500/instance/year for nginx plus.
- ploxiln 10y agoExecuting a template, writing it to a file, and sending SIGHUP, is not that hugely different from composing a request and writing it to a control socket. Maybe nginx isn't better than haproxy for many purposes. But updating configuration isn't the reason :)
- deckiedan 10y agoAnsible is working great for me.
- vacri 10y agoIf that's a problem for you, then use a pull-style config management tool (eg puppet) over a push-style one (eg ansible). If you're at a scale where logging into each server from your control node 'hurts', then you're still going to hurt with all the config other than nginx anyway.
- deleted 10y ago[deleted]