This is based on http://www.versioncontrolblog.com/2007/08/02/upgrading-drupal-52-with-git/
This is a work in progress/idea dump right now - any suggestions/improvements - please do leave a comment ;)
I have quite a few sites that are using drupal. I know I could go the route of a multisite install (I've done it before) - but I found that the requirement of upgrading all sites simultaneously was a bit too hard. However - upgrading everything by hand for each site is also poor.
The track module seems to have woken up ;)
Work on a 6.x version is progressing here: http://drupal.org/node/367448
And once that is up we may also get waypoints: http://drupal.org/node/135725
So - rather than working on a replacement of the geocaching module - perhaps track can take over.
Mollom stats: click for full size This site (being a drupal site) uses mollom to prevent comment spam. This works extremely well - but looking at the latest graph I am intrigued as to who/what/why in november/december:
Using git for handling CVS checkouts for drupal contrib:
Details are on Maintaining a Drupal module using Git
For Mac OSX users you will need cvsps (fink install cvsps for example).
Useful alias for your .gitconfig:
drupalcontribcvs = !sh -c 'git cvsimport -p x -v -d:pserver:anonymous@cvs.drupal.org:/cvs/drupal-contrib contributions/modules/$0'
This allows you to call
git drupalcontribcvs <modulename>
Normally you can call the drupal cron page (/cron.php) as the anonymous user - but - to work around an issue with the simplenews module and taxonomy access control I need to run the cron script as a logged in user.
You need to do three things (for drupal 5 - I used to be able to start at step 2 for drupal 4).
I wanted to be able to link to the geocaching.com website for caches automatically depending on the categorization of a post.
Each post that has to do with geocaching already had the geocache names (e.g. GCHZVF or GCRHWQ) associated with them in the Geocaching category.
So - I decided to create a module to do the work for me.
An extra protection can be added to drupal update function by restricting which machines can access it.
Add this to the .htaccess
<FilesMatch "update.php">
Order deny,allow
Deny from all
Allow from 192.168.3.1
Allow from 192.168.3.*
Allow from .host.tld
Allow from hostname.host.tld
</FilesMatch>
To avoid having to set up multiple cron lines - here's a script that will read your drupal install(s) and call cron on each one found.
Not sure where I saw the code (rss feed) - but the comment was present in the downloaded code - so thats a pointer to where it starts.
Changes I've made - the dir match is changed from ** to * so that it will follow symlinks. It also handles multiple drupal installs. Timeout wrapping added - one of my sites takes a long while to return.
To upgrade a site from drupal 4.7 to 5.0:
I have several sites running drupal 4.7 that will want to be upgraded to 5.0 - here's how I'm thinking of approaching it. Mostly culled from a Lullabot video.
Current status of modules for various drupal sites. Last updated 2007-01-07 apart from intern which was updated on 2007-02-05