synchronization

This should be dead simple, but it's not... yet.

Using temporary files to store and transfer sql-dump. It is recommended that you specify --source-dump and --target-dump options on the command line, or set '%dump' or '%dump-dir' in the path-aliases section of your site alias records. This facilitates fast file transfer via rsync.

What exactly does that mean? Is some random location i make up really better than the temporary directory? Or should i be giving it some specific directory, on different serves or something? Guidance please.

Failure

in drushrc.php

When you run drush sql-sync @example.prod @example.dev you do not have exactly what is on your example production site. Tables that do not exist on production but do exist on your local development site will still exist.

You need to drop all tables in the database, or simply drop and re-create the database, first.

As when working on any Agaric project that may not have had maintenance done on it in a while, update the Rakefile to be in line with current processes.

First, make sure your Vlad checkout is up-to-date. Go to it cd ~/vlad (in my case, i symlinked Vlad's true location to my home folder so he can find it. On my system Vlad's true location is /usr/local/lib/site_ruby/1.8/i686-linux/vlad/) and git pull.

cd ~/code/projectname
mv Rakefile RakefileOLD
cp /home/ben/vlad/Rakefile Rakefile
diff -up

Believe it or not, this is the function you want:

core-rsync (rsync) Rsync the Drupal tree to/from another server using ssh.

For example:

drush rsync @example.stage:%files @example.local:%files

Can't do remote to remote though.

Pretty easy, once you know where to look-- not under Calendar, but under File > New > Calendar

then On the Network and (probably) iCal/ICS.

Should be quite possible as Tomboy notes are saved in XML; not finding anyone doing it.

In Drupal, it would make sense to make Tomboy notes their own content type, so they could have their special linking, but full web content with pictures and taxonomy and all that good stuff would be separate, and could reference/include Tomboy notes.

Initial vision:

Unplugged

The Drupal synchronization module

The Drupal Synch module

• knows that when it last synched you are at node 253, user 43, comment 422, etc...

Logs, configuration settings, installed modules etc. could - should - be one way, from the server to your offline Drupal.

offline to server and back

Drupal 6 dumps the sequences table: implications?

Drupal 6 has the database handle sequences. This may make it harder for Unplugged to do its thing.

Not really though.