Rerun redis install on update script about vm

[enoch85]

Wow! Forgot about that. Can you please create a PR?

Let's go with just upgrade instead of dist-upgrade

[enoch85]

Okay, just tested and it works as expected even after upgrade. I guess you chose to use the new file, never do that in case you really must. Always keep current config.

This is not an issue --> closing.

[Ark74]

If you run the update script right after the production_install you won't see any behaviour since the packages are up to date.
But if you do dist-upgrade, right after ubuntu pushed php7 updates (this week they moved from 7.0.8 to 7.0.13) it will brake the redis support since the script it builds it from git.
I've had the same config file for over a year now.
My two cents.

[enoch85]

@Ark74 I hear you.

Though, my test was on my own server (1.5 years with the same config) and also on another server that is about 6 months (with a Nextcloud VM) and both performed well. No errors and I could login to redis-cli without any issues. both servers are in production.

[enoch85]

Ok, I just tried again, but this time I chose to install the package maintaners version, and yes, redis fails to load. But it's really easy to fix.

echo extension=redis.so >> /etc/php/7.0/apache2/php.ini

So as I said, always keep the local version and there will be no issues. :)