unit-docs
unit-docs copied to clipboard
nginx
NGINX Unit's official website and documentation
This issue serves as a place discuss and create tasks related to improving the first touch experience. Recent on-the-ground experiences at Wasm I/O with @tippexs and @danielledeleo have highlighted the...
Part of improving the first touch experience. (See #137) The NGINX Unit home page should prominently feature an easy way to get started with Unit. **Summary: we need a script...
Throughout the docs site and several other places we lack precise definitions for what kind of WebAssembly support Unit offers. There is also extra confusion because our two incompatible Wasm...
> There should also be a note on the docs (https://unit.nginx.org/installation/#node-js) > that the unit & unit-http module need matching version numbers. Indeed, that vital bit of information does seem...
The steps in the HOW-TO > App Samples > WebAssembly [doc](https://unit.nginx.org/howto/samples/#webassembly-wasm) ([source ](https://github.com/nginx/unit-docs/blob/master/source/howto/samples.rst)) include cloning a [3rd party repo](https://github.com/sunfishcode/hello-wasi-http) that we have no control over (potential security risk if a...
In our docs, we are using brand names for reference. Some of them are outdated or incorrect. Examples: ARM is Arm. This issue will be the base for a PR...
Add `$uri` to `share` for Unit version >1.26, as noted in https://unit.nginx.org/configuration/#static-files Perhaps more aclaration is needed about the matter.
We have switched from internally hosted mercurial repositories to GitHub hosted git repositories as our source of truth.
On https://unit.nginx.org/controlapi/#control-api there is a list of Objects available in the Control-API. The NJS Module can be uploaded to `js_modules` . This endpoint is missing. ```text /js_modules Responsible for [...