hi Team,
I have a quick question to this . I am currently on version 102.0.2 and was running "Current" and thus could not change server back to "Stable" as I wish to change and leave all servers on stable.
So I edited the nano /etc/cpupdate.conf to this:
CPANEL=stable
RPMUP=daily
SARULESUP=daily
STAGING_DIR=/usr/local/cpanel
UPDATES=daily
And it now looks like this in the WHM Gui (see screen shot below).
Confirming to my understanding this will now keep server on version 102.0.2 until a new "Stable" version is released and it will only update when the latest Stable version is released? correct?
Will I cause any issues "hard coding" this change and doing it this way? Is this ok. My end goal is I want to put all servers on "Stable" release to minimise updates. I do not need all feature upgrades and want reliability and less changes to schedule upgrade less often. Would this be a good way to achieve this?
Or would any one recommend a more official cpanel way of doing this as of such?
Can
I have a quick question to this . I am currently on version 102.0.2 and was running "Current" and thus could not change server back to "Stable" as I wish to change and leave all servers on stable.
So I edited the nano /etc/cpupdate.conf to this:
CPANEL=stable
RPMUP=daily
SARULESUP=daily
STAGING_DIR=/usr/local/cpanel
UPDATES=daily
And it now looks like this in the WHM Gui (see screen shot below).
Confirming to my understanding this will now keep server on version 102.0.2 until a new "Stable" version is released and it will only update when the latest Stable version is released? correct?
Will I cause any issues "hard coding" this change and doing it this way? Is this ok. My end goal is I want to put all servers on "Stable" release to minimise updates. I do not need all feature upgrades and want reliability and less changes to schedule upgrade less often. Would this be a good way to achieve this?
Or would any one recommend a more official cpanel way of doing this as of such?

Last edited by a moderator: