There is a real skill in reading the errors and troubleshooting those errors. If it does not go well, in your Ubuntu you will see the error or errors and it will explain what went wrong. If all goes well, you will get an "Exit: 0" and the local version of the site on your machine is now up-to-date. Composer will go out to each module's "website" and pull the latest version of the module and dependencies. In this phase you will use Ahoy commands in Ubuntu to execute Composer commands to update the modules in this site on your local machine/repository. Review admin>reports>status report to see the status of the site and if there are currently any major issues being reported. Review admin>reports>recent log messages to see what the current errors are on the site. Review admin>reports>available updates to see what modules need to be updated. Step 6. Once in the site, to see the modules that need to be update go to admin>Extend>Update and you will see a list of modules that need to be updated and if core needs to be updated. Copy the URL that ubuntu gave you and paste it into a new tab. For WaTech websites, ULI into the dev site using terminus drush. Go to the DEV website admin and visually review to see how they are functioning and appearing prior to updating. You should always do this prior to working on your local repository code. Once in the specific website folder you want, enter the command git pull to make sure your local repository is current. If you do not know the name of the website enter in your Ubuntu command line " ls" and it will list out all the folders/websites in your websites folder. If you are already in your watech/websites folder, enter the command cd (enter the name of the website you want to enter between the ). In Ubuntu go to the website's folder you want to update. The click "Clone Database and files from LIVE to DEV". Then select the drop down and change TEST to LIVE and check "Run update.php" and "clear cache". If it is clear to do so, go to the DEV tab and then on the left nav click on "Database/Files". If the site you are updating is color coded in orange and says "dev only" DO NOT pull down the LIVE database to DEV and just skip this step. Check on the " Drupal Updates" excel spreadsheet before you proceed with this step. On the Pantheon dashboard go to the DEV tab and click the "Backups" in the left nav. If it is in SFTP and there are changes waiting to be committed talk to Sam to make sure it is ok to proceed. Set the site to "Git" and commit pending changes on DEV. It means pushing any of the pending commits to the website, backing the DEV environment up, reviewing the modules to update, and pulling the code back to your local repository. The purpose of this phase is to get the website and all its environments ready to update. Then press "Enter" and you will clone all of the files from the master repository to your local repository. Right click your mouse in the command line and your git clone command will be pasted into that line. Click the "Copy" button.Ĭ) In Ubuntu, make sure you are in the websites folder as you see in the example below. You should only have to do this once per site.Ī) In your Pantheon dashboard go to DEV tab and click the "Code" tab on the left navigation.ī) Make sure the site is set to "Git" and then click the drop down "Clone with Git". In Ubuntu, in your websites folder, enter the git clone command from the Pantheon dashboard to pull site locally, if you don't already have it. Clone the website files from the master repository to your local machine's repository. Guide to Updating the Sites Cloning the Site's Code to your Machine
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |