ngineer is a node automation later for nginx that assists with the following:
The following example shows how the
ngineer module can be used to scaffold and start nginx within an application.
var async = ;var nginx = __dirname + '/nginx'port: 8080;async;
The above example proxies a request from http://localhost:8080/ngineer through to https://github.com/DamonOehlman/ngineer. A more practical example is shown below where we proxy a local express application through nginx.
var async = ;var express = ;var nginx = __dirname + '/nginx'port: 8080;var proxy = nginxlocation'/express-test';// create our simple express app;
Ngineer expects that it will have a nginx configuration folder that it s responsible for managing (see the
-p commandline argument). While ngineer doesn't require that it is reponsible for running the nginx process, it is happy to do this. If you do decide to use this option then ensure that you upstart (or similar) the node process running nginx.
When using ngineer it's important to note that you are probably accepting a few levels of HTTP proxying to make the magic happen. In the case of new version of steelmesh that is under development, we are using an archictecture similar to what is displayed below:
+----------------+ +----------------+ +----------------+ | |+---->| |+---->| | | HAproxy | | nginx | | node | | |<----+| |<----+| | +----------------+ +----------------+ +----------------+
Ngineer communicates with the
nginx process and sends the
to flag the the nginx configuration should be reloaded and nginx gracefully restarted.
Why do you want this? Well, because
nginx does a kick arse job of serving
static files and also proxying services so it makes sense you use it over
pure node alternatives such as node-http-proxy.
No offense is meant to the awesome nodejitsu team here, but
I feel much more comfortable using nginx over node to be the first line in
serving both node applications and static content.
ngineer you should consider also consider the following
projects (in addition to those listed in Prior Art):
Create a new location directive for the nginx configuration
The reload method sends the reload configuration (HUP) signal to the nginx process.
The reset function cleans out the config directory and stops the nginx running if is running.
Scaffold an nginx configuration directory based on a known default configuration.
Attempt to start nginx by using a few well known nginx binary locations.
Stop the nginx process
Create a location section for the nginx configuraton.
Include a proxy_pass directive into the location
Copyright (c) 2017 Damon Oehlman firstname.lastname@example.org
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.