Closed computerlyrik closed 8 years ago
Hi there!
3.0 rewrite is very much the goal - I've had some slowdown in getting around to testing the centos/systemd stuff: https://github.com/miketheman/nginx/pull/384
I'm already using the Ubuntu one in a production environment - and as long as you mentally remember that it's not /var/log/nginx/
- rather /var/log/nginx-
There's still some stuff that needs to be figured out - as in how many more things cannot be placed inside the sites-enabled/ file and must be in the root resource.
Also, the rewrite takes the stance of "this cookbook should not be compiling nginx for you on every target server" - rather you should build & distribute binaries (packages!) out of the scope of running servers.
Piggy backing on @miketheman here, https://github.com/cubicdaiya/nginx-build is a great tool for this.
@scalp42 That's cool, hadn't seen that one. I'm more like to go with fpm-cookery, and modify a recipe with my flags like so: https://github.com/bernd/fpm-recipes/blob/master/nginx/recipe.rb
The resulting package can then be stuffed in a package repo, packagecloud, etc.
BTW I'm using the centos/systemd features of #384 in production as well
Closing this question in favor of the release tracking checklist. Thanks!
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Hey there!
I'd like to join forces. I need a resource setting up proxy hosts for me.
Is your 3.0-rewrite-intention still alive? How can i help out?