From defan at nginx.com Mon Apr 1 12:33:00 2019 From: defan at nginx.com (Andrei Belov) Date: Mon, 1 Apr 2019 15:33:00 +0300 Subject: debian packages In-Reply-To: <4010ff79-8bfc-bec2-6885-aee262f166f3@outerface.net> References: <4010ff79-8bfc-bec2-6885-aee262f166f3@outerface.net> Message-ID: <23067A64-231F-4E3B-AD27-10D992A2FA5C@nginx.com> Hi Sergio, > On 30 Mar 2019, at 12:48, sergio wrote: > > > Two questions about debian packages: > > 1. When debs for buster will be available? Most likely shortly after buster will be released. > 2. What about inclusion into the main debian repository? It's up to debian package maintainers to decide whether they would like to have unit in the "main" repo. We do not maintain any packages (neither unit nor nginx) in repos other than our own one. From vbart at nginx.com Wed Apr 17 12:47:30 2019 From: vbart at nginx.com (=?utf-8?B?0JLQsNC70LXQvdGC0LjQvSDQkdCw0YDRgtC10L3QtdCy?=) Date: Wed, 17 Apr 2019 15:47:30 +0300 Subject: =?UTF-8?B?SVBDINC80LXQttC00YMg0LzQsNGA0YjRgNGD0YLQuNC30LDRgtC+0YDQvtC8INC4?= =?UTF-8?B?INC/0YDQvtGG0LXRgdGB0LDQvNC4INC/0YDQuNC70L7QttC10L3QuNC5?= Message-ID: <20743468.eHWfZYBKul@vbart-workstation> ??????? ??????????? ??????? ? ?????????: https://docs.google.com/document/d/134qzqIP5UXjr8Ct8rDl18pva7S5YT7106H3zkgbgK4Y/edit?usp=sharing ???????? ????????????: - ????????/?????? ????????? ??????? ?? ????? ??????? ?? ???? ????????????; ??? ???? ??? ???????? ?????????? ? ?????????? ?? ????? CAS ????????, ? ??? ???????? ???????????? ???????. - ??????? ???????? ??????, ??????? ???????? ?????????? ?????????? ? ????????????? ??????????? ????????? ?????? ?? ???? ????????. ???? ??????????? ????? ??? ????????????? ?????? ?????? ???????? ??? ???????? ???? ??????? ? ??????. ???? ????????? ???? ?? ??? ????, ?? ?? ???? ???? ?? ?????????? ?????????. -- ???????? From vbart at nginx.com Wed Apr 17 12:58:03 2019 From: vbart at nginx.com (Valentin V. Bartenev) Date: Wed, 17 Apr 2019 15:58:03 +0300 Subject: =?UTF-8?B?UmU6IElQQyDQvNC10LbQtNGDINC80LDRgNGI0YDRg9GC0LjQt9Cw0YLQvtGA0L4=?= =?UTF-8?B?0Lwg0Lgg0L/RgNC+0YbQtdGB0YHQsNC80Lgg0L/RgNC40LvQvtC20LXQvdC4?= =?UTF-8?B?0Lk=?= In-Reply-To: <20743468.eHWfZYBKul@vbart-workstation> References: <20743468.eHWfZYBKul@vbart-workstation> Message-ID: <28809062.6QINZUo5uQ@vbart-workstation> Sorry. This has been sent to unit at nginx.org mailing list by mistake. Please disregard. wbr, Valentin V. Bartenev From peter at bimp.fr Thu Apr 18 12:44:32 2019 From: peter at bimp.fr (Peter TKATCHENKO) Date: Thu, 18 Apr 2019 14:44:32 +0200 Subject: NextCloud using NGINX and UNIT Message-ID: <2279a50a-aba1-4c10-084c-103d7d9659f1@bimp.fr> Hi, I'm trying to install NextCloud 15 using NGINX and UNIT. I have a working instance of NextCloud 13 on NGINX and PHP-FPM, so the idea is to use the NGINX configuration from the working instance and slightly modify it to use UNIT and not PHP-FPM. I have already installed WordPress with the same configuration (with UNIT), using the document from https://unit.nginx.org/howto/wordpress/ The problem is that there is no the ONE file (like in WordPress) that should process the requests not ending with *.php, there are SEVERAL files like this. So in PHP-FPM config we use the following NGINX configuration to correctly route the traffic to PHP-FPM service: location ~ ^/nextcloud/(?:index|remote|public|cron|core/ajax/update|status|ocs/v[12]|updater/.+|ocs-provider/.+)\.php(?:$|/) { *fastcgi_split_path_info ^(.+\.php)(/.*)$;* ??? include fastcgi_params; *fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;* ??? fastcgi_param PATH_INFO $fastcgi_path_info; ??? fastcgi_param HTTPS on; ??? fastcgi_param modHeadersAvailable true; ??? fastcgi_param front_controller_active true; ??? fastcgi_pass php-handler; ??? fastcgi_intercept_errors on; ??? fastcgi_request_buffering off; ??? fastcgi_send_timeout 120s; ??? fastcgi_read_timeout 120s; } So, for example, the file /nextcloud/remote.php is used to process the requests like /nextcloud/remote.php/webdav/ and the requests like /nextcloud/ocs/v2.php/core/navigation/apps?absolute=true&format=json - are processed by /nextcloud/ocs/v2.php. The requests without script name (like /nextcloud/css/core/afde0962-server.css?v=152fab14-6) are still processed by /nextcloud/index.php The configuration of UNIT is the following (inspired by your WordPress configuration): { ??? "listeners": { ??????? "*:8300": { ??????????? "application": "nc_index" ??????? }, ??????? "*:8301": { ??????????? "application": "nc_direct" ??????? } ??? }, ??? "applications": { ??????? "nc_index": { ??????????? "type": "php", ??????????? "processes": 20, ??????????? "root": "/usr/local/www", ??????????? "script": "nextcloud/index.php", ??????????? "user": "www", ??????????? "group": "www", ??????????? "options": { ??????????????? "file": "/usr/local/etc/php.ini", ??????????????? "admin": { ??????????????????? "memory_limit": "1024M", ??????????????????? "upload_max_filesize": "4095M", ??????????????????? "max_input_vars": "2000", ??????????????????? "post_max_size": "4095M", ??????????????????? "max_execution_time": "600", ??????????????????? "variables_order": "EGPCS", ??????????????????? "expose_php": "0" ??????????????? }, ??????????????? "user": { ??????????????????? "display_errors": "0" ??????????????? } ??????????? } ??????? }, ??????? "nc_direct": { ??????????? "type": "php", ??????????? "processes": 20, ??????????? "root": "/usr/local/www", ??????????? "index": "nextcloud/index.php", ??????????? "user": "www", ??????????? "group": "www", ??????????? "options": { ??????????????? "file": "/usr/local/etc/php.ini", ??????????????? "admin": { ??????????????????? "memory_limit": "1024M", ??????????????????? "upload_max_filesize": "4095M", ??????????????????? "max_input_vars": "2000", ??????????????????? "post_max_size": "4095M", ??????????????????? "max_execution_time": "600", ??????????????????? "variables_order": "EGPCS", ??????????????????? "expose_php": "0" ??????????????? }, ??????????????? "user": { ??????????????????? "display_errors": "0" ??????????????? } ??????????? } ??????? } ??? } } Could someone advise me in such configuration, please? Best regards, *Peter TKATCHENKO* -------------- next part -------------- An HTML attachment was scrubbed... URL: From vbart at nginx.com Thu Apr 18 15:23:53 2019 From: vbart at nginx.com (Valentin V. Bartenev) Date: Thu, 18 Apr 2019 18:23:53 +0300 Subject: NextCloud using NGINX and UNIT In-Reply-To: <2279a50a-aba1-4c10-084c-103d7d9659f1@bimp.fr> References: <2279a50a-aba1-4c10-084c-103d7d9659f1@bimp.fr> Message-ID: <12548630.HI6hrkEjxq@vbart-workstation> On Thursday 18 April 2019 14:44:32 Peter TKATCHENKO wrote: > Hi, > > I'm trying to install NextCloud 15 using NGINX and UNIT. > > I have a working instance of NextCloud 13 on NGINX and PHP-FPM, so the > idea is to use the NGINX configuration from the working instance and > slightly modify it to use UNIT and not PHP-FPM. > > I have already installed WordPress with the same configuration (with > UNIT), using the document from https://unit.nginx.org/howto/wordpress/ > > The problem is that there is no the ONE file (like in WordPress) that > should process the requests not ending with *.php, there are SEVERAL > files like this. > > So in PHP-FPM config we use the following NGINX configuration to > correctly route the traffic to PHP-FPM service: > > location ~ > ^/nextcloud/(?:index|remote|public|cron|core/ajax/update|status|ocs/v[12]|updater/.+|ocs-provider/.+)\.php(?:$|/) > { > *fastcgi_split_path_info ^(.+\.php)(/.*)$;* > include fastcgi_params; > *fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;* > fastcgi_param PATH_INFO $fastcgi_path_info; > fastcgi_param HTTPS on; > fastcgi_param modHeadersAvailable true; > fastcgi_param front_controller_active true; > fastcgi_pass php-handler; > fastcgi_intercept_errors on; > fastcgi_request_buffering off; > fastcgi_send_timeout 120s; > fastcgi_read_timeout 120s; > } > > So, for example, the file /nextcloud/remote.php is used to process the > requests like /nextcloud/remote.php/webdav/ and the requests like > /nextcloud/ocs/v2.php/core/navigation/apps?absolute=true&format=json - > are processed by /nextcloud/ocs/v2.php. The requests without script name > (like /nextcloud/css/core/afde0962-server.css?v=152fab14-6) are still > processed by /nextcloud/index.php > [..] Hi, I suggest the following configuration: { "listeners": { "127.0.0.1:8888": { "pass": "applications/nextcloud" } }, "applications": { "nextcloud": { "type": "php", "script": "nextcloud.php", "root": "/path/to/root" } } } with the "nextcloud.php" script (in the attachement). You should put it into the document root directory (above the "nextcloud" one). It will do all the magic required by Nextcloud (although not tested). Note that it requires PHP version 7 or above. wbr, Valentin V. Bartenev -------------- next part -------------- A non-text attachment was scrubbed... Name: nextcloud.php Type: application/x-php Size: 458 bytes Desc: not available URL: From peter at bimp.fr Thu Apr 18 20:04:00 2019 From: peter at bimp.fr (Peter TKATCHENKO) Date: Thu, 18 Apr 2019 22:04:00 +0200 Subject: NextCloud using NGINX and UNIT In-Reply-To: <12548630.HI6hrkEjxq@vbart-workstation> References: <2279a50a-aba1-4c10-084c-103d7d9659f1@bimp.fr> <12548630.HI6hrkEjxq@vbart-workstation> Message-ID: <3D279980-82A2-4F1B-B5E9-9870F9A754EB@bimp.fr> Thank you, it?s really interesting approach! I?ll test it shortly. It would be nice to be able to use only nginx features for such decoding though ;) Do you think it is impossible? Peter > Le 18 avr. 2019 ? 17:23, Valentin V. Bartenev a ?crit : > > From vbart at nginx.com Fri Apr 19 11:54:44 2019 From: vbart at nginx.com (Valentin V. Bartenev) Date: Fri, 19 Apr 2019 14:54:44 +0300 Subject: NextCloud using NGINX and UNIT In-Reply-To: <3D279980-82A2-4F1B-B5E9-9870F9A754EB@bimp.fr> References: <2279a50a-aba1-4c10-084c-103d7d9659f1@bimp.fr> <12548630.HI6hrkEjxq@vbart-workstation> <3D279980-82A2-4F1B-B5E9-9870F9A754EB@bimp.fr> Message-ID: <3100121.y7pOe8vkor@vbart-laptop> On Thursday, 18 April 2019 23:04:00 MSK Peter TKATCHENKO wrote: > Thank you, it?s really interesting approach! I?ll test it shortly. > It would be nice to be able to use only nginx features for such decoding though ;) Do you think it is impossible? > These transformations should be done while populating PHP environment variables. It would be nice to have in Unit configuration, but currently there seems almost no way to achieve that. It requires URI rewriting with regular expression and multiple entry points. Another approach, where everything is done on the nginx side requires from Unit some sophisticated way of how to set PHP environment out of HTTP header fields. On the other hand, using one php script as a single entry point is quite easy and should not introduce any problems or performance drawbacks. I don't know why some php programmers so used to rely on URI rewriting inside the web server and don't do everything out of the box. But anyway, we're looking to introducing corresponding abilities in Unit. wbr, Valentin V. Bartenev From freddycoronado63 at gmail.com Mon Apr 22 18:29:04 2019 From: freddycoronado63 at gmail.com (Freddy Coronado) Date: Mon, 22 Apr 2019 13:29:04 -0500 Subject: No subject Message-ID: -------------- next part -------------- An HTML attachment was scrubbed... URL: