Make it possible to add generic config blocks in sites and configs

[NBZ4live]

Sometimes you have to deal with configuration blocks like:

http {
...
upstream default {
server 127.0.0.1:8080 weight=10;
server 127.0.0.1:9090 weight=20;
...
}
...
server {
...
if ( condition ) {
...
}
...
location / {
...
}
...
}
}

This commits make it possible to add such blocks to the /etc/nginx/conf.d/.conf files generated by this role and to the /etc/nginx/sites-enabled/.conf

[jdauphant]

We could simplify and use syntax like :
https://gist.github.com/jdauphant/8777228

What do you think ?

[NBZ4live]

It will work if you wrap it with quotation marks like

nginx_sites:
...
     - "location / {
          try_files $uri $uri/ /index.html;
       }"

but than the line breaks will be ignored and if you have multiple lines inside the block you will get something like:

geo $geo { default 0; 127.0.0.1/32 0; 192.168.178.121/32 0; };

If you have huge blocks, this will be not very good to read.

But I agree that the blocks solution is not the best. It can't handle block hierarchies and looks not the best way in the config. I'm thinking about utilizing macros in the future, but we still should find a way to separate simple lines and blocks in the var files for better consistency.

[jdauphant]

It's works without wrap in "" for me.
For the syntax you can cheat like in your template :

{% for v in item.server.vars %}
   {{ v.replace(";",";\n   ").replace("{","{\n      ") }}{% if v.find('{') == -1%} ;{% endif %} 
{% endfor %}

Now you have a beautiful output.

[NBZ4live]

Ok done. Works pretty well now.

I squashed the previous commits.

[jdauphant]

Perfect :)