One thing that always bugged me is that everything on my development server is in my home directory except my databases. As I go on the road a lot and like to have my server on my laptop, "syncing" the server becomes annoying. I usually use rsync, but unless you enable the root account, you won't be able to synchronize the elusive /var/lib/mysql folder. And we all know what the community thinks of enabling the root account. This is just one of the countless reasons why I decided to move my databases to my home directory. It's also nice knowing that I need to backup only my home folder. Fortunately MySQL presents an easy way to change the user the process should run as.

It's been more than a year since I released Gallerix. I originally aimed to fill a giant gap in the wonderful world of Drupal. The need for an elegant and simple-to-use photo sharing module was voiced by many, but only make-shift solutions surfaced. Some of these involved the image module, some involved a custom view, and some involved CCK. Some even involved a combination of these. And while they filled the gap somewhat, they really only worked for administrators and people familiar with Drupal, not grandmothers hoping to share some pictures.

After a few days of hard work, I've finally upgraded this site to Drupal 6. In the process, I had to give up quite a few features, but overall, I think the transition was worth it. There will be a few major changes, but only one that will concern the majority of users that visit this site.

The minor changes involve a revamped post flow. That is, no longer will there be a separate section for announcements, thoughts, articles, and tutorials. Instead everything is treated as the same content type, and taxonomy is used to distinguish them.

But the main change concerns project issue tracking. Like many others, after ages of waiting for the Project module to be ported to Drupal 6, I've given up. So in the meantime, I will setup Trac and see how it works out. It's unfortunate that it's separate from Drupal, but hopefully it's powerful features will make it worthwhile.

For a while, I've promoted the use of the issue queue for every project of mine, even if they were hosted on Drupal too. The idea was to centralize all my issues, but unfortunately things didn't really work out that way, and some issues are here, and some issues are on drupal.org.

Because giving credit to fixed issues is so important to projects, I've decided to use Drupal's issue tracker exclusively for projects hosted on both sites. That way I can use issue numbers without ambiguity as to what site the issue number applies to.

Remember, this only applies to projects hosted on both sites, as is the case with Gallerix, CCK Multimage, and JSFX. Projects like the Gallerix Widget Engine are only hosted here, and thus retain the issue queue.