Sentora v2.0.2 released!

[TGates]

Great news gang! Sentora v2.0.2 is released!

Notice:

As we work on PHP 8 updates CentOS support will be discontinued and Debian will be added.
We suggest you start to migrate your CentOS servers to Ubuntu before this next major update happens.
(Sorry, we do not have an estimated time for this update/change.)

Basic changes:
Many visual and functionality enhancements.
Some requested enhancements from GitHub.
Bug fix with Snuffleupagus logging.
Fixed/Added some missing module translations.
A couple bug fixes.

Things fixed/changed in this version:
0000024: [Installer] Snuffleupagus php 7.4 old_php_warning (Anthony)
0000029: [Modules] Move PHP Info module to Advanced menu item (TGates)
0000028: [Modules] Move shadowing module to Reseller menu item (TGates)
0000059: [Core] Make a dev update link (TGates)
0000014: [Modules] Update SenCrypt Translations (TGates)
0000069: [Installer] Update script stops if Sentora version is 2.0.1 (Anthony)
0000063: [Modules] Add max available characters to DB Name input field on the front-end (TGates)
0000062: [Modules] Add username prefix to FTP front-end (TGates)
0000054: [Installer] Make a Dev installer.sh (TGates)
0000056: [Modules] Fix translations in Client Manager Module (TGates)
0000036: [Modules] Add reseller name to Shadowing module "Reseller ID' column (TGates)
0000041: [Installer] vacation.conf hardcoded vacation_domain (TGates)
0000048: [Core] Add vmail folder size to clients total disk space used (TGates)
0000047: [Modules] Add Shadow button in Client Manager (TGates)
0000031: [Core] Show the account user name in the Shadowing bar (TGates)
0000015: [Apps] SenCrypt front-end appearance update (TGates)
0000023: [Modules] Update MySql username text length (TGates)
0000016: [Apps] Add SSL port checks to Services module (TGates)
0000027: [Core] Add user name prefix to MySQL User Manager module (TGates)
0000022: [Modules] Add MySql username prefix (TGates)

To install or upgrade, visit the installer docs HERE

Enjoy gang!

[franmm25]

Is working ? go to the link but i don´t know where see for upgrade, etc, thanks for all your job, regards

[TGates]

Is working ? go to the link but i don´t know where see for upgrade, etc, thanks for all your job, regards

Yes, select which ever link you want in the docs, install or upgrade, and the info is there.

[franmm25]

Sorry, but I don't understand.

If I go to: https://docs.sentora.org/?node=22

I see the same installer that installs Sentora 2.01. I thought there was another installer or a way to upgrade from 2.01 to 2.02. Currently, I am using version 2.01. If you can tell me how to do this upgrade, that would be perfect.

Thanks

[TGates]

Sorry, but I don't understand.

If I go to: https://docs.sentora.org/?node=22

I see the same installer that installs Sentora 2.01. I thought there was another installer or a way to upgrade from 2.01 to 2.02. Currently, I am using version 2.01. If you can tell me how to do this upgrade, that would be perfect.

Thanks

Correct, the install/update links have been updated to redirect to the 2.0.2 GiutHub repositories.

We use the same install/update links to keep things easier. We just change 2 lines in the site's .htaccess instead of changing all of the links site-wide.

If you need to install an older version like v2.0.1 for example, you would use https://sentora.org/install_2.0.1 or https://sentora.org/update_2.0.1
I plan on updating the docs to show the links for past versions for development purposes.

[TGates]

As of this post, We have made some last minute fixes to Sentora v2.0.2

You can get these fixes just by running the update script again (as ROOT).

It will updated your Sentora install with these new revisions.

We decided it would be easier to add them this way versus making an entirely new release so soon in case people haven't had a chance to update their servers yet.

We have also found a SenCrypt SSL module front-end update that was not included in this release that we will add to the v2.0.2 repo in the next few days. We will notify you when it has been updated. (Simply running the update script from the command line as ROOT will update your files accordingly.)

We do understand that this is an 'odd' way of doing these fixes versus creating and releasing a new update. We decided to do it this way since they should have been in this release.

We could have done a v2.0.2.1 release, but the time involved for us to make a new GitHub repo for it and update the installers to accommodate these minor changes is much more complicated than having Server admins running the update script again to get the new changes.