I have been working with this particular book now for a couple of months now and I have to say that it is one of my favorites.
Sam’s Teach Yourself PHP, MySQL and Apache. – this link goes to Amazon.
This book is perfect for where I want to go with Drupal. xAMP is the Drupal backbone and this book covers everything that I need from the last three letters of this acronym. There code sample are well documented and helpful. Check it out if you plan to be able to develop for Drupal and not just implement the modules and themes that are on Drupal.org.
This is one area of change management that is really backwards. because my hosting company is responsible for updating the OS on my server I don’t get a notification. so, i want to make sand/quality/prod the same so the patches are installed on prod first. but i am still going to follow the BPs and document the change. at least I don’t have to go in front of the Change committee anymore and have them pick it apart. Change Management in the corporate world can be such a pain….
so, here’s the proc:
confirm the new files
rpm -q centos-release
that last command must be run on sand and prod to ensure that the level is consistent.
Please note that this procedure has been written for my specific situation. I believe that it is applicable to others and may provide insight to your situation but it will most likely not match what you have exactly so please be cautious. Back things up and test in a dev/qual environment first! I have just finished it in Quality and it works fine.
- Back up everything
- Download the new core file
- Put site into maintenance mode
- Place it on the server and extract all the contents to /var/www/719/drupal-7.19
- In the newly extracted files delete the sites directory and all its subs.This is done because the upgrade is not going to replace anything in this directory
- Rrom a terminal window type: yes | cp -r /var/www/719/drupal-7.19/* /var/www/html
- Note that the destination folder of html is my doc root and all the drupal folders/files are located right underneath this. the yes | cp…. prefix is to let the system know to overwrite everything in the destination. since sites is the only directory that we want to keep and we have removed it from the source, this will be fine.
- Run update.php by navigating to http://…yourdrupalsitename/update.php
- Follow the instructions for this closely
- navigate to reports, available updates and check the version of your core
- take the site off of maintenance mode
- check different things on the site to ensure a smooth upgrade has occurred.
- that should just about do it.
Well, I have finally gotten my dev server up and running. now my dev matches prod. CentOS 6.3 is the choice by my provider, Blackmesh.com and now it is my choice as well.
there were some challenges getting centos to work with drupal but nothing too bad and it ended up taking about half a day.
I’m learning Drupal. And as I started taking notes on the things that I need to think about as I choose a theme, I thought, why do this in notepad.exe? I mean, i like notepad, but why not blog about it anyway? this way, I can have a place to sort out my thoughts on what i need to do and have a nice record of it for reference. Plus, I can write yet another blog, honing my skills at SEO in the process. this is gonna be bare bones. i’m not gonna worry much about images or punctuation too much. so here we go.