Upgrade advice for upgrading centminmod?

you can as they're not tied to your server if you used paid ssl certificates.

Upgrades don't really make changes to other files needlessly. You really need to try and keep the code/routines that Centmin Mod uses up to date.

You can try the following by backing up the main files first and then do a fresh Centmin Mod code replacement by backing up and moving /usr/local/src/centminmod.

Replace branchname with branch you want either 123.08stable or 123.09beta01. The cp copy commands backup the key files/vhost/ssl etc first

Code (Text):

branchname=123.09beta01
cp -a /etc/my.cnf /etc/my.cnf-old
cp -a /usr/local/etc/php-fpm.conf /usr/local/etc/php-fpm.conf-old
cp -a /etc/centminmod /etc/centminmod-old
cp -a /usr/local/nginx/conf /usr/local/nginx/conf-old
cd /usr/local/src
mv centminmod centminmod-old
git clone -b ${branchname} --depth=1 https://github.com/centminmod/centminmod.git centminmod
cd centminmod
./centmin.sh

the last run for centmin.sh syncs any needed changes

then you can compare all the new and old directory and files and transfer them back manually if needed

Code (Text):

sdiff /etc/my.cnf /etc/my.cnf-old
sdiff /usr/local/etc/php-fpm.conf /usr/local/etc/php-fpm.conf-old
diff -qr /etc/centminmod /etc/centminmod-old
diff -qr /usr/local/nginx/conf /usr/local/nginx/conf-old
diff -qr /usr/local/src/centminmod /usr/local/src/centminmod-old

example if file differs

Code (Text):

diff -qr /etc/centminmod /etc/centminmod-old
Files /etc/centminmod/email-primary.ini and /etc/centminmod-old/email-primary.ini differ

then use sdiff to see what the actual difference is

sdiff side by side view

Code (Text):

sdiff /etc/centminmod/email-primary.ini /etc/centminmod-old/email-primary.ini

sdiff side by side view only differences flag -s

Code (Text):

sdiff -s /etc/centminmod/email-primary.ini /etc/centminmod-old/email-primary.ini

Code (Text):

sdiff /etc/centminmod/email-primary.ini /etc/centminmod-old/email-primary.ini
3                                                             | 1

These steps ensure you're running the latest routines that power Centmin Mod.

If you can post the output of the diff -qr commands, I can tell whether or not there's a better way to ensure some changes persist after Centminn Mod updates i.e. if you can use persistent config file method via /etc/centminmod/custom_config.inc etc

There's also a list of other file comparison tools you can use within SSH or locally on own PC listed at List of file comparison tools | Centmin Mod Community For windows I use BeyondCompare

 

Upgrading Centmin Mod involves 2 parts.

1. Upgrading the actual Centmin Mod code outlined at Upgrade Centmin Mod. This is heart of Centmin Mod where the code is the engine that runs centmin.sh shell based menu and all the automation you're accustomed to. You can easily update within a Centmin Mod version branch or switch version branches via centmin.sh menu option 23 outlined here.
2. Upgrade software that Centmin Mod installed or manages. For this part following outline at How to upgrade Centmin Mod software installed on your server.

So essentially, you can upgrade from .07 to .08 in place, but not everything is upgraded as some things like server initial environment setup isn't changed i.e. how swap, tmp setup and allocation are created etc. The main parts from part 2 above are what in place upgrades do i.e. Nginx and PHP-FPM compilation and config/settings parameters and MariaDB version from 5.5 to 10.0.x. If you want the full environment changed including tmp and swap setup to .08's configuration, then you would need a fresh OS install and fresh .08 initial install. You can think of it like upgrading Windows 7 to Windows 8. An in place upgrade will upgrade code but won't change your computer environment from when you installed Windows 7 i.e. disk configuration and partition sizes won't change from when you initially installed Windows 7. Only way to change that would be fresh Windows 8 install.

So if you want full 123.08stable or my preferred 123.09beta01 experience (change log), a fresh install on new vps and data transfer might be more idea. Once on 123.08stable, updates get easier due to centmin.sh menu option 23. Getting Started Guide step 19 outlines also how to keep Centmin Mod code updated or how to switch version branches.

With Centmin Mod 1.2.3-eva2000.08) (123.08stable) and higher releases, a newly added centmin.sh menu option 23 allows much easier code updates and version branch swicthing via Git backed environment you can setup. For full details read the following links:

• New centmin.sh menu option 23 updating
• Centmin Mod Upgrades
• Cronjob Auto Updating Centmin Mod Code Guide
• How to upgrade Centmin Mod + backing up customisations

 

nice

no leave nologin set for nginx user

see FAQ item 2, Getting Started Guide step 2's mention of uploading files and Pureftp virtual ftp user for for older users see thread 1st post on how to setup Pureftp user on old installs at Beta Branch - Centmin Mod .08 beta + pure-ftpd virtual FTP user support | Centmin Mod Community

but if you did fresh install and new centmin.sh menu option 2 setup for site vhost, you would of generated the pure-ftpd virtual ftp user for uploading files too

 

yeah i touched on security and ssh keys in reply to @hitman's thread at protect root user over ssh | Centmin Mod Community and similarly applies to using root user i.e. using console in DigitalOcean if you loose access to your server via SSH