Downloads:
17,232
Downloads of v 1.14.1:
559
Last Update:
22 Nov 2018
Package Maintainer(s):
Software Author(s):
- Igor Sysoev
Tags:
nginx service nssm- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
nginx service
This is not the latest version of nginx service available.
- 1
- 2
- 3
1.14.1 | Updated: 22 Nov 2018
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
17,232
Downloads of v 1.14.1:
559
Software Author(s):
- Igor Sysoev
nginx service 1.14.1
This is not the latest version of nginx service available.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
To install nginx service, run the following command from the command line or from PowerShell:
To upgrade nginx service, run the following command from the command line or from PowerShell:
To uninstall nginx service, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download nginx-service --internalize --version=1.14.1 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade nginx-service -y --source="'INTERNAL REPO URL'" --version="'1.14.1'" [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade nginx-service -y --source="'INTERNAL REPO URL'" --version="'1.14.1'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install nginx-service
win_chocolatey:
name: nginx-service
version: '1.14.1'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'nginx-service' do
action :install
source 'INTERNAL REPO URL'
version '1.14.1'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller nginx-service
{
Name = "nginx-service"
Version = "1.14.1"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'nginx-service':
ensure => '1.14.1',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package was approved by moderator gep13 on 23 Nov 2018.
nginx [engine x] is an HTTP and reverse proxy server, a mail proxy server, and a generic TCP/UDP proxy server, originally written by Igor Sysoev.
This package provides an nssm
Windows service wrapper for it which creates a standard Windows
service named nginx
to manage the server.
N!B! Upgrading from nginx-service 1.6.2.1 and below it will have new default configuration location.
It may be disappointing, but here's few reasons why:
- Writing inside previous
C:/ProgramData/nginx
requires editor to be opened with Administrator privileges - Changing to new directory allow for optimistic migration from 1.6.2.1 to 1.14.1
- 1.6.2.1 is a quite old and I believe most of users have already found another way for newer nginx. Those who dont, probably also wont bother updating to newer
C:/tools/nginx
is on par with other web-related choco packages
During installation nginx-service
will create following directory structure:
C:/tools/nginx/
├── conf
│ ├── nginx.conf
│ └── ...
├── conf.d
│ ├── server.default.conf
│ └── server.d0n3.ws.conf.sample {Bonus file, read content}
├── html
│ └── index.html
├── logs
│ └── {Required}
└── temp
└── {Required}
- Place your custom config files inside
conf.d
- Conf to be included must follow naming pattern
server*.conf
where*
is a wildcard - Above allows config pattern where extra
.conf
files are included (and reused) manually fromserver*.conf
, i.e. PHP location directive - It is safe to edit/rename/remove default config files. They will be restored during upgrade only if
conf.d
is empty
See the nginx.org for more detailed documentation.
$ErrorActionPreference = 'SilentlyContinue'
nssm stop nginx 2>&1 | Out-Null
nssm remove nginx confirm 2>&1 | Out-Null
$ErrorActionPreference = 'Stop'
server {
listen 80;
server_name localhost;
#charset koi8-r;
#access_log logs/host.access.log main;
location / {
root html;
index index.html index.htm;
}
#error_page 404 /404.html;
# redirect server error pages to the static page /50x.html
#
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root html;
}
# proxy the PHP scripts to Apache listening on 127.0.0.1:80
#
#location ~ \.php$ {
# proxy_pass http://127.0.0.1;
#}
# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
#
#location ~ \.php$ {
# root html;
# fastcgi_pass 127.0.0.1:9000;
# fastcgi_index index.php;
# fastcgi_param SCRIPT_FILENAME /scripts$fastcgi_script_name;
# include fastcgi_params;
#}
# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
#location ~ /\.ht {
# deny all;
#}
}
#
# DURING UPDATE THIS FILE WILL BE OVERWRITTEN
# IF YOU HAVE IMPORTANT IMPROVEMENTS, CONTACT
# ME ON chocolatey.org/packages/nginx-service
#
#user nobody;
worker_processes 1;
#error_log logs/error.log;
#error_log logs/error.log notice;
#error_log logs/error.log info;
#pid logs/nginx.pid;
events {
worker_connections 1024;
}
http {
include mime.types;
default_type application/octet-stream;
#log_format main '$remote_addr - $remote_user [$time_local] "$request" '
# '$status $body_bytes_sent "$http_referer" '
# '"$http_user_agent" "$http_x_forwarded_for"';
#access_log logs/access.log main;
sendfile on;
#tcp_nopush on;
#keepalive_timeout 0;
keepalive_timeout 65;
#gzip on;
# PLACE YOUR CUSTOM {server}.conf FILES INSIDE
# C:/tools/nginx/conf.d/
include ../conf.d/server*.conf;
}
/*
* Copyright (C) 2002-2018 Igor Sysoev
* Copyright (C) 2011-2018 Nginx, Inc.
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
*
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*/
Log in or click on link to see number of positives.
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
nginx service 1.24.0 | 1045 | Wednesday, April 12, 2023 | Approved | |
nginx service 1.23.4-mainline | 26 | Wednesday, April 12, 2023 | Approved | |
nginx service 1.23.2-mainline | 81 | Thursday, October 20, 2022 | Approved | |
nginx service 1.22.1 | 521 | Thursday, October 20, 2022 | Approved | |
nginx service 1.21.6-mainline | 89 | Wednesday, May 25, 2022 | Approved | |
nginx service 1.21.4-mainline | 135 | Thursday, November 18, 2021 | Approved | |
nginx service 1.21.0-mainline | 123 | Wednesday, May 26, 2021 | Approved | |
nginx service 1.20.2 | 878 | Thursday, November 18, 2021 | Approved | |
nginx service 1.20.1 | 1065 | Wednesday, May 26, 2021 | Approved | |
nginx service 1.20.0 | 389 | Wednesday, April 21, 2021 | Approved | |
nginx service 1.19.10-mainline | 95 | Wednesday, April 21, 2021 | Approved | |
nginx service 1.18.0 | 1648 | Wednesday, April 22, 2020 | Approved | |
nginx service 1.17.10-mainline | 167 | Wednesday, April 22, 2020 | Approved | |
nginx service 1.17.3-mainline | 261 | Wednesday, August 14, 2019 | Exempted | |
nginx service 1.16.1 | 1613 | Wednesday, August 14, 2019 | Approved | |
nginx service 1.16.0 | 677 | Wednesday, April 24, 2019 | Approved | |
nginx service 1.15.12-mainline | 186 | Wednesday, April 24, 2019 | Exempted | |
nginx service 1.15.8-mainline | 246 | Wednesday, January 16, 2019 | Exempted | |
nginx service 1.14.2 | 606 | Friday, January 18, 2019 | Approved | |
nginx service 1.14.1 | 559 | Thursday, November 22, 2018 | Approved | |
nginx-service (Install) 1.12.2 | 2829 | Tuesday, February 27, 2018 | Approved | |
nginx-service (Install) 1.12.2-beta | 153 | Friday, February 16, 2018 | Exempted | |
nginx-service 1.6.2.1 | 3247 | Thursday, April 2, 2015 | Approved | |
nginx-service 1.6.2 | 457 | Monday, February 9, 2015 | Approved |
2018 © Nginx, Inc.
*) Security: when using HTTP/2 a client might cause excessive memory
consumption (CVE-2018-16843) and CPU usage (CVE-2018-16844).
*) Security: processing of a specially crafted mp4 file with the
ngx_http_mp4_module might result in worker process memory disclosure
(CVE-2018-16845).
*) Bugfix: working with gRPC backends might result in excessive memory
consumption.
Ground Rules:
- This discussion is only about nginx service and the nginx service package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or nginx service, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.