From leon.blade at gmail.com Sun Sep 8 06:02:03 2019 From: leon.blade at gmail.com (James Stine) Date: Sun, 8 Sep 2019 02:02:03 -0400 Subject: Is this possible with NGINX Unit with PHP? Message-ID: Hello everyone, This is my first time using one of these mailing lists, I apologize if I'm doing something wrong ahead of time. Thank you for understanding. My question is about NGINX Unit with PHP for a specific server configuration, namely with routing. My environment is something like this: I have a wordpress path in "/var/www/wordpress" that I want to be setup on the root of my domain like this "http://example.com/". Along with that, I want another app such as "phpMyAdmin" which is located at "/var/www/phpMyAdmin". I want this to be off the same server configuration, but to be ran from the domain like this " http://example.com/pma". The server just tries to request a path like this: "/var/www/phpMyAdmin/pma" where the "pma" is coming from the URI. Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: From vbart at nginx.com Mon Sep 9 14:03:34 2019 From: vbart at nginx.com (Valentin V. Bartenev) Date: Mon, 09 Sep 2019 17:03:34 +0300 Subject: Is this possible with NGINX Unit with PHP? In-Reply-To: References: Message-ID: <1897167.bXZghV8laf@vbart-workstation> On Sunday 08 September 2019 02:02:03 James Stine wrote: > Hello everyone, > > This is my first time using one of these mailing lists, I apologize if I'm > doing something wrong ahead of time. Thank you for understanding. > Hi James, You did all right. > My question is about NGINX Unit with PHP for a specific server > configuration, namely with routing. My environment is something like this: > > I have a wordpress path in "/var/www/wordpress" that I want to be setup on > the root of my domain like this "http://example.com/". Along with that, I > want another app such as "phpMyAdmin" which is located at > "/var/www/phpMyAdmin". I want this to be off the same server > configuration, but to be ran from the domain like this " > http://example.com/pma". > > The server just tries to request a path like this: > "/var/www/phpMyAdmin/pma" where the "pma" is coming from the URI. > > Thanks! Unfortunatly there's no URI rewriting functinality in Unit. It's planned for the future releases. Currently, you should either put your phpMyAdmin sources into the "pma" subdirectory or just create a symlink (pma -> ..). If you're using nginx in front of Unit, then you can also do such rewriting inside nginx like this: location /pma/ { proxy_pass http://:/; } wbr, Valentin V. Bartenev From vbart at nginx.com Thu Sep 19 19:01:18 2019 From: vbart at nginx.com (Valentin V. Bartenev) Date: Thu, 19 Sep 2019 22:01:18 +0300 Subject: Unit 1.11.0 release Message-ID: <7233454.a0GeFpuvnW@vbart-workstation> Hi, I'm glad to announce a new release of NGINX Unit. This release improves the stability of Go applications and introduces three major features: 1. Ability to Serve Static Media Assets With this feature, we're only at the beginning of a long road to transform Unit into a full-fledged web server, capable of acting as a building block for web services of any kind. In this release, the support for static files is very simple; you can only specify the document root directory for Unit to handle: { "share": "/data/www/example.com" } Also, you can fine-tune MIME types: { "mime_types": { "text/plain": [ "readme", ".c", ".h" ], "application/msword": ".doc" } } Use encoding to access object members with names that contain "/" characters directly by their URI: GET /config/settings/http/static/mime_types/text%2Fplain/ See the documentation for details: - https://unit.nginx.org/configuration/#static-files In the upcoming releases, we'll extend this area of functionality to handle more use cases in the most performant manner. Unfortunately, basic proxying support did not make it to this release, as tests have revealed that it needs more work. There are excellent chances that the feature will be included in the next release in a month or so. 2. Application Isolation This capability increases the security of running applications, allowing to run them in isolated environments based on Linux namespaces. This is very similar to how Docker containers work. The configuration is pretty straightforward: you can customize the isolation level and configure UID/GID mapping between the host and the container: { "namespaces": { "credential": true, "pid": true, "network": true, "mount": false, "uname": true, "cgroup": false }, "uidmap": [ { "container": 1000, "host": 812, "size": 1 } ], "gidmap": [ { "container": 1000, "host": 812, "size": 1 } ] } See the documentation for details: - https://unit.nginx.org/configuration/#process-isolation This feature was implemented by Tiago de Bem Natel de Moura, who has joined our team recently; he will continue working on security features hardening and container support of Unit. 3. WebSockets in Java Servlet Containers WebSocket connection offloading was first introduced in the previous release for Node.js only; now it's extended to JSC as well. We will continue advancing application language support further to provide equally broad opportunities, whichever language you may prefer. Changes with Unit 1.11.0 19 Sep 2019 *) Feature: basic support for serving static files. *) Feature: isolation of application processes with Linux namespaces. *) Feature: built-in WebSocket server implementation for Java Servlet Containers. *) Feature: direct addressing of API configuration options containing slashes "/" using URI encoding (%2F). *) Bugfix: segmentation fault might have occurred in Go applications under high load. *) Bugfix: WebSocket support was broken if Unit was built with some linkers other than GNU ld (e.g. gold or LLD). That's all for this release. Try, test, leave feedback, and stay tuned! wbr, Valentin V. Bartenev From rauchristian at hotmail.com Mon Sep 23 07:50:28 2019 From: rauchristian at hotmail.com (Christian Rau) Date: Mon, 23 Sep 2019 07:50:28 +0000 Subject: Hello: v.1.11 basic support of serving static files. Message-ID: Hello, I am planning to set up a multi-domain system with python as the primary back-end language, and just very recently discovered Unit. So as I am reading about how to install and configure a Unit/Nginx server, I noticed this: ".. Install NGINX. Currently, NGINX is required to serve static files." I guess this is not valid anymore after 1.11: https://unit.nginx.org/howto/nextcloud/#nginx-and-unit Or is it still necessary? Best Regards Christian Rau -------------- next part -------------- An HTML attachment was scrubbed... URL: From rauchristian at hotmail.com Mon Sep 23 08:32:46 2019 From: rauchristian at hotmail.com (Christian Rau) Date: Mon, 23 Sep 2019 08:32:46 +0000 Subject: Any recommendations for Centos/Unit Saas multi-domain server? Message-ID: Hello, Server administration is far from my core skills, so bare with me, if I am not asking the right questions! However when I watched the presentation of Unit I was exhilarated over the simplicity.. Not sure if I am missing something here. So I wonder what it requires to setup a Centos/Unit only server, what else do you need to install besides the OS and Unit server? (I have a little experience with apache - apache/nginx) * Is there a web-panel you can use with unit/centos. (I am visual oriented) * Any recommendations, for a decent basic setup? * Is there any libraries, plugins out there currently being developed? * Any inputs on what to research, tutorials to read/watch or where to look is most appreciated. Hardware: VPS Xeon E5-2630 v4 @ 2.20GHz, 4 cores, 8Gb * What are the max processes per app, I can define in Unit? * How does Unit handle Ram? Best regards Christian Rau -------------- next part -------------- An HTML attachment was scrubbed... URL: From artem.konev at nginx.com Mon Sep 23 09:36:19 2019 From: artem.konev at nginx.com (Artem Konev) Date: Mon, 23 Sep 2019 12:36:19 +0300 Subject: Hello: v.1.11 basic support of serving static files. In-Reply-To: References: Message-ID: Christian Rau wrote: > Hello, > > I am planning to set up a multi-domain system with python as the primary back-end language, and just very recently discovered Unit. > > So as I am reading about how to install and configure a Unit/Nginx server, I noticed this: > ".. Install NGINX. Currently, NGINX is required to serve static files." > > I guess this is not valid anymore after 1.11: > https://unit.nginx.org/howto/nextcloud/#nginx-and-unit Hello, Christian, Yes, you're right. Updates to this and similar howtos are coming this week. > > Or is it still necessary? > > Best Regards > > Christian Rau > _______________________________________________ > unit mailing list > unit at nginx.org > https://mailman.nginx.org/mailman/listinfo/unit ? Artem Konev Sr. Technical Writer From rauchristian at hotmail.com Mon Sep 23 09:56:31 2019 From: rauchristian at hotmail.com (Christian Rau) Date: Mon, 23 Sep 2019 09:56:31 +0000 Subject: Hello: v.1.11 basic support of serving static files. In-Reply-To: References: , Message-ID: Great! Thank you! ________________________________ From: unit on behalf of Artem Konev Sent: Monday, September 23, 2019 11:36 AM To: unit at nginx.org Subject: Re: Hello: v.1.11 basic support of serving static files. Christian Rau wrote: > Hello, > > I am planning to set up a multi-domain system with python as the primary back-end language, and just very recently discovered Unit. > > So as I am reading about how to install and configure a Unit/Nginx server, I noticed this: > ".. Install NGINX. Currently, NGINX is required to serve static files." > > I guess this is not valid anymore after 1.11: > https://unit.nginx.org/howto/nextcloud/#nginx-and-unit Hello, Christian, Yes, you're right. Updates to this and similar howtos are coming this week. > > Or is it still necessary? > > Best Regards > > Christian Rau > _______________________________________________ > unit mailing list > unit at nginx.org > https://mailman.nginx.org/mailman/listinfo/unit ? Artem Konev Sr. Technical Writer _______________________________________________ unit mailing list unit at nginx.org https://mailman.nginx.org/mailman/listinfo/unit -------------- next part -------------- An HTML attachment was scrubbed... URL: