Opened 4 years ago

Closed 4 years ago

#2077 closed enhancement (wontfix)

rename conf files with ".sample" extension for windows package

Reported by: long76@… Owned by:
Priority: trivial Milestone: nginx-1.19
Component: nginx-package Version: 1.19.x
Keywords: conf windows package Cc: long76@…
uname -a:
nginx -V: nginx version: nginx/1.19.4
built by cl 16.00.40219.01 for 80x86
built with OpenSSL 1.1.1h 22 Sep 2020
TLS SNI support enabled
configure arguments: --with-cc=cl --builddir=objs.msvc8 --with-debug --prefix= -
-conf-path=conf/nginx.conf --pid-path=logs/ --http-log-path=logs/access
.log --error-log-path=logs/error.log --sbin-path=nginx.exe --http-client-body-te
mp-path=temp/client_body_temp --http-proxy-temp-path=temp/proxy_temp --http-fast
cgi-temp-path=temp/fastcgi_temp --http-scgi-temp-path=temp/scgi_temp --http-uwsg
i-temp-path=temp/uwsgi_temp --with-cc-opt=-DFD_SETSIZE=1024 --with-pcre=objs.msv
c8/lib/pcre-8.44 --with-zlib=objs.msvc8/lib/zlib-1.2.11 --with-http_v2_module --
with-http_realip_module --with-http_addition_module --with-http_sub_module --wit
h-http_dav_module --with-http_stub_status_module --with-http_flv_module --with-h
ttp_mp4_module --with-http_gunzip_module --with-http_gzip_static_module --with-h
ttp_auth_request_module --with-http_random_index_module --with-http_secure_link_
module --with-http_slice_module --with-mail --with-stream
vc8/lib/openssl-1.1.1h --with-openssl-opt='no-asm no-tests -D_WIN32_WINNT=0x0501
' --with-http_ssl_module --with-mail_ssl_module --with-stream_ssl_module


when i update nginx i just replace all files and forgot about config file.

it's like in php:

  • php.ini-development
  • php.ini-production


it's change don't make any trouble because users always need configure nginx after first install.

Change History (1)

comment:1 by Maxim Dounin, 4 years ago

Resolution: wontfix
Status: newclosed

Thank you for your suggestion. The directory structure of nginx/Windows archive is expected to be working, so users can start nginx without editing configuration at all, or with minor editing. Providing instead a non-working directory structure with configuration files renamed to some arbitrary names is going to be much harder even for experienced users, not to mention new users who don't know how configuration files are expected to be named.

Instead, consider re-thinking the update procedure you use. For example, nginx's own 'make install', as available when making nginx from sources on UNIX systems, only installs configuration files when they do not exist in destination directory (and always installs the same files with the suffix ".default", so there is always a reference copy which matches currently installed nginx).

Note: See TracTickets for help on using tickets.