Complete

I have never liked Trac. I just don't like the user interface, the inability to use HTML if one wishes, some problems I encountered with cross-posting comments causing the slower writer (me) to lose their comment, and unquantifiable prejudice.

But everyone else at Agaric is for it, so for now we may try Trac+Git (a separate trac and a separate git repository for each client) for new projects rather than our Project module plus Organic Groups approach (which we will continue for most existing projects).

dan@mini9:~$ sudo git clone http://git.agaricdesign.com/git/drupal-6-agaric-core.git leftysbrew
Initialized empty Git repository in /home/dan/leftysbrew/.git/
Cannot get remote repository information.
Perhaps git-update-server-info needs to be run there?
dan@mini9:~$ sudo git-update-server-info
fatal: Not a git repository

It's the one that got away.

I've been working with drupal and have been a part of the community for a fews years now. Although I may not be the most active member around, I have attended a decent amount of drupal meetups all over Massachusetts and New York City. I've seen what works, and I've seen what doesn't, the reason for this post is to state my opinion on what the purpose and goal of a meetup should be, and how it should be conducted.

Agaric salutes you, Stefan!

And without further adieu, the steps to move a Drupal 5 site from one of our legacy approaches to development and deployment using version control to Stefan's Git-Capistrano set-up (and upgrading to Drupal 6 in the process).

Moving CarlitosNY.com into the new system (and Drupal 6 while we're at it).

On the production server, find where it's hidden...
ben@agaricdesign:~$ locate carlitos

sudo git push
To /srv/git/drupal-6-agaric-core.git
! [rejected] master -> master (non-fast forward)
error: failed to push some refs to '/srv/git/drupal-6-agaric-core.git'

Uh... right.

But do not fear! This error likely just means other changes have been made that you should pull in first.

Watch:

Stefan has set up fantastic tools using Git and Capistrano and Rake to rapidly set up Drupal projects for Agaric. This documentation, private on MyAgaric.com, will be generalized and made public once we've worked out more bugs in the system.

This post isn't about this system specifically so much as a general caution.

If you have any setup to aid your deployment that automatically makes a database or user based on your project name, you have to be aware of MySQL's 16 character limit and do something to address this before the errors.

Agaric Design Collective's standard project starter distribution, stored as a git repository from which cloned projects can pull updates (upgraded modules or core and new additions), consists of Drupal 6 core and the following excellent contributed modules drawn from the thousands publicly available on Drupal.org.

The ability to use the Drush Package Manager (drush pm) to install a module in an arbitrarily specified directory doesn't presently exist.

Testing the code in the Drush does NOT have to be a module! issue. Specifically, the ready-to-run tarball in comment #36.