Hi guys,

We have several proxy servers in US, EU and AU and now we use comit/fetch/reload strategy and git as config storage.
This method ok for little changes, but for now we are reloading nginx every 5 minutes, it's not good for my opinion.

I want to minimize reloading count, seems distributed storage is good solution for that.
Do you support any distributed storage (Zookeeper, DFS, etc.d or riak) for config files?

Do you have any out of the box solution for this case?

What does distributed storage solve in matters of reloading nginx'config ?
Here's a topic that deals with frequent loading of a config portion:
https://groups.google.com/forum/#!topic/openresty-en/G916sAMSOPY

---
nginx for Windows http://nginx-win.ecsds.eu/

Sorry, my fault. There are 2 problem we want to resolve:
1) All proxy in all DC are the same. For now we use git repo and cronjob which pull configs. Seems distributed fs much better solution in this case
2) After moving or creating account we need to change nginx config or add new one. Do nginx have subscriptions to fs or smthng like this to avoid reloading?

sladdi Wrote:
-------------------------------------------------------
> 2) After moving or creating account we need to change nginx config or
> add new one. Do nginx have subscriptions to fs or smthng like this to
> avoid reloading?

You can't avoid reloading config unless you use Lua and something like memcache from where stuff is 'reloaded', which is fine for generic stuff but not for adding a domain. If you're referring to (auth)access accounts, that can be dynamic without reloading config since a passwd file can be changed while running.
Also try this query https://www.google.nl/#q=nginx%20configuration%20management

---
nginx for Windows http://nginx-win.ecsds.eu/