Tristan Media LLC Blog

I'm moving some sites currently on shared hosting to Slicehost and setting up MySQL replication so I can run backups from the slave and push them to Amazon S3 storage on a regular basis using s3sync.

This ONLamp article gives a handy step-by-step guide. One thing that got me though, was that I had set up iptables to firewall my servers, and I needed to get my master and slave able to talk to each other without opening up MySQL to the whole world. My solution was to email Slicehost and request private IP addresses for both servers. I then changed this line in /etc/mysql/my.cnf from

bind-address = 127.0.0.1

to

bind-address = my private IP address

on each server. Then I added this to my iptables rules on both:

-A INPUT -p tcp -m tcp --dport 3306 -j ACCEPT

I reloaded the iptables rules with iptables-restore, and then checked with telnet from another server outside of those 2 to make sure I couldn't reach port 3306.

The next problem I encountered was an error like this when I restarted the slave after copying over the data in the master to get started:

error: 'Access denied for user 'debian-sys-maint'@'localhost' (using password: YES)'

A search of the Ubuntu forums gave me this thread which explained that debian uses a file called /etc/mysql/debian.cnf for that user password, and when I moved things over from the master DB, I changed the password for that user. The solution is to change to password in that file on the slave to the same password found on the master.

We first set up the Culture Pundits website in August 2007, but now that we have reached a critical mass of websites, traffic, and advertisers, we have announced the official launch.

Check out the press release.

Continuing my exploration of custom modules and views, here is my code for allowing view builders to filter entries based on a status field, say "special offers" that is represented in our module's database table by an integer with 1 for true or 0 for false.

Add this key to your array entry for a table, at the same level as the 'join' key. See my earlier post for how the rest of the array works.

In this case, the database column is called "is_special_offer." The keys you should supply are discussed here in the Views handbook.

'filters' => array(
  'is_special_offer' => array(
     'name' => 'Product: Is Special Offer',
     'operator' => 'views_handler_operator_eqneq',
     'list' => 'views_handler_operator_yesno',
     'list-type' => 'select',
     'help' => t('Show only Special Offers'),
  )
)

All hail the power of Blueprint. All of my new projects use it as the base for setting up the design. We used it as the basis for the redesign of ArtCal done in cooperation with Subsidiary Design.

It's the easiest grid layout CSS I have ever used, and much more convenient than YUI Grids. You also get the advantage of attractively designed fonts and sizes for all HTML elements including headers.

In anticipation of a big press release distribution announcing the official launch of Culture Pundits, I redesigned my Tristan Media LLC homepage using Blueprint, adding blocks for my three main projects. I'm using PHP with a JSON feed to rotate the featured ArtCat artist on every page load. I'm using the Google AJAX Feed API to display recent items from RSS feeds.

Subsidiary is also working on new artist and gallery templates for ArtCat, using Blueprint.

Yesterday, I used Dotster to buy a domain name for a new art gallery client. Their name is an Polynesian name shared with a certain beach in the Pacific, and has no hint of a porn connection, as far as I know. This is a screen grab of what Dotster put up as a placeholder page. I recommend pairNIC in the future.

I'm working with a client on a Drupal site where another programmer has implemented several custom content types via a module, not CCK. I'm researching how to integrate this with the Views module, and found this useful information so far.

• http://drupal.org/handbook/modules/views/api
• http://drupal.org/node/148456

The hook of note seems to be hook_views_tables to get the view editing interface to know about the columns in our custom table.

Here is the start of a function to return the information to the Views module. In this example we use product_id as the primary key of our table, which is the same as the node's nid. This only exposes the name of the product to the view, but more columns and tables will be added later.

// hook to tell views about our tables
function mymodule_views_tables() {
 $tables['mymodule_product'] = array(
   'name' => 'mymodule_product',
   'join' => array(
     'left' => array(
       'table' => 'node',
       'field' => 'nid'
       ),
      'right' => array(
        'field' => 'product_id'
       )
     ),
     'fields' => array(
       'name' => array('name' => t('Product: Name'),  
                       'sortable' => TRUE),
     ),
   );

 return $tables;
}