William Estlow

My feedback

  1. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    William Estlow shared this idea  · 
  2. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Service Improvement » Applications  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    William Estlow commented  · 

    Ok so i have successfully updated a stock version of Moodle to version 3.4.1+.

    The process i used is below:

    Make sure to take a snapshot and back up all important data before you upgrade

    Place the server in maintenance mode.
    Log in using SSH (Putty) and SFTP (Filezilla)
    Navagate to ~ directory (cd ~)
    Make a new directory for the upgrade (jan2018upgrade "or what ever you want to name it)
    Download the newest stable version of moodle and use FTP to send the .tgz file to the jan2018upgrade folder. (or wget)
    Go to the jan2018upgrade folder (~/jan2018upgrade) and extract the file using the following command.
    Tar xzf moodle.34.tgz (or whatever the name of the file is)
    Use the command LS to list the folders, you should see a folder called (Moodle)
    Make a new directory for the backup file of (Public_HTML) called (jan2018back) in the ~ directory.
    Copy the public_html contents to the jan2018back using the following.
    Navagate to ~/applications/(Server hfalhuhu~~ or what ever your server name is)/public_html/
    Send the command ( LS ) to list the files in the folder.
    Use the command mv ./* ~/jan2018back/ to move the files to the backup location.
    Use LS to make sure the folder is empty
    Next copy the new moodle files to the current public_html folder using the following command
    First go to the server public_html folder ( cd ~/applications/hgfayufihrayfa/public_html)
    To copy the files enter the following command.
    Cp -R .rf ~/jan2018upgrade/moodle/* ./
    Now copy the config.php file back to the public_html folder using the following command.
    Cp ~/jan2018back/config.php . (make sure you are in the current public_html folder)
    Now use the command ls blocks/ to view the files in the folders and compare them with the backup folder files, copy any that are missing in the new installation from the backup folder.
    Take the server out of maintenance mode and login to moodle. This will let you complete the update process and update the database.

    I hope this helps someone.
    Please contact me if you have any questions and i will do my best to answer you.

    Also this is a very helpful video: https://www.youtube.com/watch?v=racjmJGMGz8

    Thanks,
    Will

    An error occurred while saving the comment
    William Estlow commented  · 

    There are several ways to process this update that i have found. I am going to be testing the Git using CLI in the console using a test server and a copy of my production site.
    I am going to use the following information to attempt the update:
    https://docs.moodle.org/33/en/Upgrading
    https://docs.moodle.org/33/en/Administration_via_command_line#Running_CLI_scripts

    Once i attempt the update to 3.3 I will give you an update on how it goes.

    I have found that Cloudways will process the update for you using a cloning server method but at $700 (i think that's what the price was) i will try myself first.

    Will

Feedback and Knowledge Base