NGINX Unit - universal web app server - a lightweight and versatile open source server that simplifies the application stack by natively executing application code across eight different programming language runtimes.
Find a file
Ava Hahn 6e8f7bbb91 tools/unitctl: Initial Docker Procedures
* move UnitdProcess serialization logic into UnitdProcess
* filter out docker processes from process output on Linux
* initial implementation of a UnitdContainer type
* initial implementation of a docker container search for unitd
* pull out custom openapi future executor and use same tokio
  runtime as docker client
* refactor openapi client to not manage its own tokio runtime
* process mount points per docker container
* correctly output docker container info in relevant unitd
  instances
* create UnitdProcess from UnitdContainer
* UnitdProcess now owns UnitdContainer
* get and parse container details from docker API
* introduce procedure to rewrite file paths based on docker
  container mounts
* test path rewrite facilities
* apply path rewrite to unix socket

Signed-off-by: Ava Hahn <a.hahn@f5.com>
2024-05-08 13:30:08 -07:00
.github Add a GitHub workflow to check for whitespace issues 2024-05-02 14:19:32 +01:00
auto auto, perl: Fix building the Perl language module with clang 2024-05-07 17:36:35 +01:00
docs Docs: njs (lowercase) is more preferred way to mention 2024-04-10 13:30:02 +01:00
go Go: Add missing +build and go:build comments 2024-01-10 11:15:48 -05:00
pkg NJS: loader should be registered using njs_vm_set_module_loader() 2024-03-12 16:56:11 +00:00
src Convert 0-sized arrays to true flexible array members 2024-05-07 02:46:49 +01:00
test Tests: error report corrected for unknown variables in "response_headers" 2024-04-10 17:04:30 +01:00
tools tools/unitctl: Initial Docker Procedures 2024-05-08 13:30:08 -07:00
.gitattributes Packages: Move dist target to git archive 2024-02-16 13:14:35 -08:00
.gitignore Added .gitignore. 2022-05-03 12:41:36 +02:00
.hgignore Added .hgignore file. 2020-09-18 19:37:56 +01:00
.hgtags Unit 1.31.1 release. 2023-10-19 11:47:22 +01:00
.mailmap .mailmap: Map Dylan's 2nd GitHub address 2024-03-07 19:04:40 -05:00
.rustfmt.toml Add a .rustfmt.toml file 2024-02-21 16:20:32 +00:00
CHANGES Docs: njs (lowercase) is more preferred way to mention 2024-04-10 13:30:02 +01:00
CODE_OF_CONDUCT.md Adding the NGINX Code of Conduct to the repo. 2023-03-07 13:05:41 +00:00
configure Added unit pkg-config file. 2023-08-01 10:16:17 -07:00
CONTRIBUTING.md Docs: replaced the slack community links with GitHub Discussions 2024-01-10 17:12:05 +01:00
LICENSE Added LICENSE and NOTICE files. 2017-09-06 18:26:37 +03:00
NOTICE Updated copyright notice. 2024-02-20 16:08:36 +00:00
README.md Fix some trailing whitespace and long lines in the README 2024-04-23 19:33:45 +01:00
SECURITY.txt Updated security.txt 2024-01-11 11:45:20 -05:00
version Version bump 2024-02-27 12:24:44 +00:00

NGINX Unit

Project Status: Active – The project has reached a stable, usable state and is being actively developed. CI

Universal Web App Server

NGINX Unit Logo

NGINX Unit is a lightweight and versatile open-source server that has two primary capabilities:

  • serves static media assets,
  • runs application code in seven languages.

Unit compresses several layers of the modern application stack into a potent, coherent solution with a focus on performance, low latency, and scalability. It is intended as a universal building block for any web architecture regardless of its complexity, from enterprise-scale deployments to your pet's homepage.

Its native RESTful JSON API enables dynamic updates with zero interruptions and flexible configuration, while its out-of-the-box productivity reliably scales to production-grade workloads. We achieve that with a complex, asynchronous, multithreading architecture comprising multiple processes to ensure security and robustness while getting the most out of today's computing platforms.

Quick Installation

macOS

$ brew install nginx/unit/unit

For details and available language packages, see the docs.

Docker

$ docker pull unit:<TAG>
$ mkdir /tmp/unit-control # customize as needed.
$ docker run -d \
      --mount type=bind,src=/tmp/unit-control,dst=/var/run \
      --mount type=bind,src=.,dst=/www \
      --network host \
      unit

For a description of image tags, see the docs.

WARNING: latest image tag may not provide support for specific language modules, do check the available image tags from the link above before pulling your image.

Your current working directory will now be mounted to the Unit image at /www. You can reach its socket at /tmp/unit-control/control.unit.sock assuming no further customizations have been made.

Amazon Linux, Fedora, Red Hat

$ wget https://raw.githubusercontent.com/nginx/unit/master/tools/setup-unit && chmod +x setup-unit
# ./setup-unit repo-config && yum install unit
# ./setup-unit welcome

For details and available language packages, see the docs.

Debian, Ubuntu

$ wget https://raw.githubusercontent.com/nginx/unit/master/tools/setup-unit && chmod +x setup-unit
# ./setup-unit repo-config && apt install unit
# ./setup-unit welcome

For details and available language packages, see the docs.

Configuration

NGINX Unit provides a RESTful API for dynamic configuration. See the control API documentation for more information on what endpoints are available and how to use them.

For full details of configuration management, see the docs.

Running a Hello World App

Unit runs apps in a variety of languages. Let's consider a basic example, choosing PHP for no particular reason.

Suppose you saved a PHP script as /www/helloworld/index.php:

<?php echo "Hello, PHP on Unit!"; ?>

To run it on Unit with the unit-php module installed, first set up an application object. Let's store our first config snippet in a file called config.json:

{
    "helloworld": {
        "type": "php",
        "root": "/www/helloworld/"
    }
}

Saving it as a file isn't necessary, but can come in handy with larger objects.

Now, PUT it into the /config/applications section of Unit's control API, usually available by default via a Unix domain socket:

# curl -X PUT --data-binary @config.json --unix-socket  \
       /path/to/control.unit.sock http://localhost/config/applications

{
	"success": "Reconfiguration done."
}

Next, reference the app from a listener object in the /config/listeners section of the API. This time, we pass the config snippet straight from the command line:

# curl -X PUT -d '{"127.0.0.1:8080": {"pass": "applications/helloworld"}}'  \
       --unix-socket /path/to/control.unit.sock http://localhost/config/listeners
{
    "success": "Reconfiguration done."
}

Now Unit accepts requests at the specified IP and port, passing them to the application process. Your app works!

$ curl 127.0.0.1:8080

      Hello, PHP on Unit!

Finally, query the entire /config section of the control API:

# curl --unix-socket /path/to/control.unit.sock http://localhost/config/

Unit's output should contain both snippets, neatly organized:

{
    "listeners": {
        "127.0.0.1:8080": {
            "pass": "applications/helloworld"
        }
    },

    "applications": {
        "helloworld": {
            "type": "php",
            "root": "/www/helloworld/"
        }
    }
}

WebAssembly

Unit supports running WebAssembly Components (WASI 0.2). For more information see the Unit Configuration Docs.

OpenAPI Specification

Our OpenAPI specification aims to simplify configuring and integrating NGINX Unit deployments and provide an authoritative source of knowledge about the control API.

Although the specification is still in the early beta stage, it is a promising step forward for the NGINX Unit community. While working on it, we kindly ask you to experiment and provide feedback to help improve its functionality and usability.

Community

  • The go-to place to start asking questions and share your thoughts is GitHub Discussions.

  • Our GitHub issues page offers space for a more technical discussion at your own pace.

  • The project map on GitHub sheds some light on our current work and plans for the future.

  • Our official website may provide answers not easily found otherwise.

  • Get involved with the project by contributing! See the contributing guide for details.

  • To reach the team directly, subscribe to the mailing list.

  • For security issues, email us, mentioning NGINX Unit in the subject and following the CVSS v3.1 spec.