ToddGee.commie

Today I renamed the drupalManageFCKEditor.sh script to drupalManageLibraries.sh.

drupalManageFCKEditor.sh was a script I had written to help with the installation and maintenance of the FCKEditor library that is required to make the Drupal fckeditor module work.  It allowed downloading the latest version of the file and looking inside the installed directory for modifications to the original files.

This is a follow-up to my last post on integrating Drush with my Drupal Scripts Library.

This is a discussion on how to integrate drush into a Drupal environment set up with my Drupal Scripts Library.

Here I'll discuss the setup of a pair of Drupal websites, one a development ('dev') site and one a production ('prod'), and a system allowing the migration of state between them (promotion).  This discussion, and the procedures described assume the presence of my Drupal Script Library.

Motivation

In many cases, especially those of high-visibility, high-importance sites, it is desirable to see how changes will affect a site before releasing the change to the public.  A new module, new content, or even updates need to be tested in a development environment before being effected on the production site.

Having a development environment on which changes can be staged allows assurance that a change doesn't have any negative effects as well as giving stake-holders an opportunity to sign off on the change before it goes live.

I've been having getting my normal editor working (a Winders editor that I run under wine) and thought I'd give eclipse a shot.

Today, for a site I maintain, I did some work on how anonymous comment posts work.  The goal was to support anonymous commentst that would be published and to send an admin a notification email.  In addition to this, I did some setup so that anon comment posting would work w/ the the 'Filtered HTML' input format even tho 'Full HTML' was the sitewide default to support the use of the FCKEditor.  This was all done w/ contrib modules and configuration.

I'm in the process of setting up Fedora 11 on my new Dell Latitude D630.  This post will document the process.

Going thru the optional packages in Fedora is always a pain, but after the required 30 minutes or so, I finished.  I reboot the machine and it came right up in Fedora, no problems.  I connected it to my local wifi network, installed the fastestmirror package, then began the 200M+ update.

I just got a new (to me) laptop -- my brother's old hand-me-down Dell Latitude D630.  (He went to the dark side and started using a proprietary operating system.)  I'm currently in the process of wiping off the XP install and installing Fedora 11 (12 doesn't come out for another month).  One of the first steps in any install is to choose a name for the new machine.  (For a fun aside be sure to see the now-crufty

I just helped to found a Drupal development company: Chicago Drupal Authority

Go check 'em out.

now.

I have completed what I think is a good start to a suite of bash shell scripts that aid in the management of DreamHost customer accounts.

For now, the scripts mainly focus on the creation of backups of important (mainly Drupal) files in the host environment.

See the scripts at http://svn.toddgee.com/dhScripts
See the README at http://svn.toddgee.com/dhScripts/README