LLNG is able to use different web servers to provide its services. Here is a resume of all possibilities. We recommend:
Since 2.0, both portal and manager are native FastCGI / PSGI Plack based applications. They can be powered by any FastCGI / PSGI compatible web servers. Some examples:
Apache | Nginx | Plack servers family | ||
---|---|---|---|---|
Engines | mod_fcgid or mod_fastcgi | FastCGI/uWSGI server | Any Plack HTTP server (see our doc) | |
Link with webserver process | External processes managed by webserver (default) | External LLNG server | External LLNG server | Inside |
Applications can be protected:
To protect applications with handler, LLNG can be used in two mode:
LLNG handlers can be installed on the following web servers:
Apache | Nginx | Plack servers family | Node.js | |
---|---|---|---|---|
Addon needed | ModPerl | Express | ||
LLNG integration in webserver | Inside | Separate process: External LLNG FastCGI/uWSGI servers (auth_request) | Inside | Inside |
Apache | Nginx | |
---|---|---|
LLNG integration in ReverseProxy webserver | Inside | Separate process: External LLNG FastCGI/uWSGI servers |
Nginx supportes natively FastCGI and uWSGI protocoles.
Therefore, LLNG services can be provided by compatible external servers.
By default, LLNG provides a Plack based FastCGI server able to afford all LLNG services using FCGI engine.
However, you can use some other FastCGI server engines: