Fwd: Does anyone have Fresh Nextcloud Install on PHP-legacy with cache working?
On Fri, 15 Sept 2023, 01:38 David C. Rankin, <drankinatty@gmail.com> wrote:
If I duplicate the complete LAMP setup in docker as well as running my other apps, that will likely make a 4G Celeron roll over a croak?
On Mon, 18 Sept 2023 at 19:33, Dee Moore <dee42moore@gmail.com> wrote:
It's really close, actually. The cost is mostly in storage, a little in RAM due to the libraries not being shared by other processes. In my real life experience with redis, it adds about 1-2% CPU overhead. Well worth it.
Sorry, I missed the original question. Yes, I agree with Dee - even with a second webserver as a frontend proxy (I recommend nginx), it's not like doing twice the work - the heavy lifting will be done in the container. There are some small overheads in CPU, a bit more in RAM, and then maybe storage is the most noticeable, but probably nothing compared to what NextCloud is using anyway. Paul
On 9/19/23 03:07, Paul Dann wrote:
On Fri, 15 Sept 2023, 01:38 David C. Rankin, <drankinatty@gmail.com <mailto:drankinatty@gmail.com>> wrote:
If I duplicate the complete LAMP setup in docker as well as running my other apps, that will likely make a 4G Celeron roll over a croak?
On Mon, 18 Sept 2023 at 19:33, Dee Moore <dee42moore@gmail.com <mailto:dee42moore@gmail.com>> wrote:
It's really close, actually. The cost is mostly in storage, a little in RAM due to the libraries not being shared by other processes. In my real life experience with redis, it adds about 1-2% CPU overhead. Well worth it.
Sorry, I missed the original question. Yes, I agree with Dee - even with a second webserver as a frontend proxy (I recommend nginx), it's not like doing twice the work - the heavy lifting will be done in the container. There are some small overheads in CPU, a bit more in RAM, and then maybe storage is the most noticeable, but probably nothing compared to what NextCloud is using anyway.
The conclusion of the saga... After the bump on my forehead grew sufficiently large from beating my head against the wall going back over and over the wiki instructins and the many config files involved, I hit upon the solution. (actually grep omitting comments did) open_basedir is intentionally not enabled any of my php.ini/php-fpm.ini files on this TEST server. To enable Redis, the wiki instructs you to: "Locate the existing sections where other extensions are enabled and add two additional lines corresponding to igbinary and redis." The wiki mentions open_basedir at this point, but only for the case: "In case you have specified the open_basedir option in the above configuration files..." Which I had not done on this test box. However, it turns out that open_basedir is *enabled by default* in /etc/php-legacy/php-fpm.d/nextcloud.conf. It is located well up above and away from where add or uncomment the igbinary and redis extensions so not something you will be drawn to by following the wiki. (wiki updated to clarify open_basedir is enabled by default in /etc/php-legacy/php-fpm.d/nextcloud.conf) After adding /run/redis to the open_basedir path - I have the full caching config specified by the wiki, APCu and igbinary/redis on the same host through Unix socket working as intended. With thanks to David Runge for suspecting it was a config issue.. indeed it was. -- David C. Rankin, J.D.,P.E.
participants (2)
-
David C. Rankin
-
Paul Dann