Year End Site Status Update

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Year End Site Status Update

    In the next few months there will be some foundation work that needs to be done to the site.
    • The web server software is up to date to the latest release 2.4.54 and our hosting company keeps this up to date automatically so there is nothing for us to do there.
    • Our Database, MariaDB, needs a minor version update from 10.3.x to 10.6.x. Support for 10.3 ends in May. This should be a simple upgrade, but requires downtime to backup the database prior to the upgrade, just in case something goes wrong. 10.6 is supported until July 2026.
    • PHP which is the language vBulletin is written in was updated to the latest stable release 8.1 last week with a hiccup in the graphics processing extension that took a couple of days to clean up. 8.2 was released 3 weeks ago. The PHP versions are supported for a year after each release so these updates are more frequent. We will upgrade to 8.2 as time permits and when our hosting provider supports it.
    • Last, vBulletin is at version 5.7.0 which is one micro release behind. Version 5.7.1 only had foreign language fixes that don't affect us. 5.7.2 will be released in the next few weeks and I'll upgrade that during the same downtime for the Database upgrade. This should occur sometime in January or early February assuming no issues are detected in testing. vBulletin releases occur about every three or four months and we usually apply the latest release after two to three weeks of testing.

  • #2
    What is the latest CentOS or rocky Linux release our current hosting provider will allow? Should we be looking at possibly in AWS ec2 instance or similar hosting platform?
    Please like and subscribe to my YouTube channel. Please check out and subscribe to my Workshop Blog.

    Comment


    • #3
      I'm not sure what A2 Hosting's plan is for the CentOS 7 end of life. Fortunately we have a year and a half before that occurs. I'll reach out to their support and ask.

      Code:
      cat /etc/os-release
      NAME="CentOS Linux"
      VERSION="7 (Core)"
      ID="centos"
      ID_LIKE="rhel fedora"
      VERSION_ID="7"
      PRETTY_NAME="CentOS Linux 7 (Core)"
      ANSI_COLOR="0;31"
      CPE_NAME="cpe:/o:centos:centos:7"
      HOME_URL="https://www.centos.org/"
      BUG_REPORT_URL="https://bugs.centos.org/"
      
      CENTOS_MANTISBT_PROJECT="CentOS-7"
      CENTOS_MANTISBT_PROJECT_VERSION="7"
      REDHAT_SUPPORT_PRODUCT="centos"
      REDHAT_SUPPORT_PRODUCT_VERSION="7"​
      
      cat /etc/centos-release-upstream
      Derived from Red Hat Enterprise Linux 7.9 (Source)​
      Chr's
      __________
      An ethical man knows the right thing to do.
      A moral man does it.

      Comment


      • #4
        I wonder what the cost difference would be between staying put, or going over to EC2 instances. Or if maybe A2 will offer Rocky to replace CentOS...
        Please like and subscribe to my YouTube channel. Please check out and subscribe to my Workshop Blog.

        Comment

        Working...
        X