This script is designed to install Nginx on modern Ubuntu, other Debian-based systems might also work.
- Many common first-party modules (Check auto-generated
config.yaml
for details) - Dynamic Record Resizing for TLS
- brotli
- headers-more
- geoip2
- fancyindex
- OpenSSL from source
- Zlib-Cloudflare from source
- Substitutions Filter
- Development Kit
- Vanilla
- OpenResty
Go to discussions to request more modules.
pip install -U nginx-install
or
git clone https://github.com/VermiIIi0n/nginx_install.git
cd nginx_install
pip install -U poetry
poetry install
Create a config.yaml
, use any action
as the first argument, it won't actually run if config.yaml
is not found.
nginx-install uninstall --dry ## creates a config.yaml file and quits
Edit your config.yaml
and run the following command to install Nginx:
nginx-install install
To uninstall Nginx, use the following command:
nginx-install uninstall
nginx-install { prepare | build | install | uninstall | clean } [build_dir]
When you first run the script, you will be asked to create a config.yaml
under the current directory. You may not want to run as root when creating the config.yaml
file.
You can also specify the file using the -c
/--config
option.
The first positional argument is the action to be performed.
The second positional argument is optional and is used to specify the build directory. If not specified, the default build directory is used.
When running the script for real business, you will be prompted to run as root, because the script needs to install packages and create directories.
To just build the Nginx binary, use the following command:
nginx-install build ./build # Or any other build directory
To just install without building, use the following command:
nginx-install install --no-build ./build # Or any other build directory
To build and install Nginx, use the following command:
nginx-install install # Here the build directory is in a tmp dir
build
and plain install
both delete the previous build directory and create a new one.
Currently only partial support for cross-compiling. If your target system is the same as the build system, you can copy the build directory to the target system and run install --no-build
there.
Change -march
in config.yaml
if your are installing on systems with different CPU
By default, core
installer will use -march=native
flag, this may cause problems on other systems.
Check your -march
by running gcc -march=native -Q --help=target | grep march
on your target system and change -march
in config.yaml
accordingly.
If you cloned the repository, use the following command to run the script:
poetry run `which python` nginx_install <...>
Use --dry
to run the script in dry-run mode. In this mode, the script will not change anything outside of build_dir
but will print the commands to be executed.
nginx-install --dry build
no root should be required if you have access to the build directory.
The config.yaml
file is used to specify the version of Nginx to be installed, the modules to be included, and the build options.
Use -c
/--config
to specify the path of the config.yaml
file. By default, it is config.yaml
under the current directory.
If not specified, the script will search for the ./config.yaml
file, and if not found, it will ask you to create one.
If -q
/--quiet
is specified, the script will not ask you to create one and will exit with an error if not found.
Useful options in config.yaml
:
version
: The version of Nginx to be installed. Can bestable
,mainline
,latest
, or a simple spec version (e.g.1.21.3
,^1.24.0
,<=1.26.0
).core.flavor
: Can be vanilla and openrestypymodule_paths
: A list of paths to Python modules. Convenient for adding customInstaller
classes.
You can easily add your own modules to modify the installation of Nginx (e.g. add custom modules, change build options, etc.).
All Installer
classes are descendants of the BaseInstaller
class.
Every Installer
class has 5 async
methods corresponding to the 5 stages of the installation process:
prepare
build
install
uninstall
clean
They all accept a special context
parameter, which contains useful information about the installation process. You must override these methods in inherited classes.
During installation running, installers go through prepare
, build
, install
and clean
stages. During uninstallation running, installers go through uninstall
and clean
stages.
A special Installer
called core
represents the core binary installer of Nginx. In every stage, the core installer methods are called first, and then the methods of other installers are called. The order of the other installers is random. This is done to reduce build time.
You can access core
through the context
parameter. Parameters like Nginx configure options
are stored in core
and can be modified.
The context
parameter is a dictionary containing the following attributes:
build_dir
: The build directory.cfg
: TheConfig
object from theconfig.yaml
file.core
: TheNginxInstaller
object.verbose
: A boolean value indicating whether to print verbose information.quiet
: A boolean value indicating whether to print nothing unless an error occurs.dry_run
: A boolean value indicating whether to run the script in dry-run mode. You should respect this value in your custom installers. Don't actually change anything ifdry_run
isTrue
.user
: The user who started the script.client
: Ahttpx.AsyncClient
object. You can use it to download files from the internet.logger
: You can use it to log information.progress
: Arich.progress.Progress
object. You can use it to show a progress bar.run_cmd
: Anasync
function to run shell commands. You should use it to run shell commands in your custom installers. Whendry_run
isTrue
, it will only print the command to be executed.download
: Anasync
function to download files from the internet. You should use it to download files in your custom installers. It automatically shows a progress bar when downloading files.