Stovak.net The internet home of Tom Stovall
i no u
i no u
when we were in school
u said u wouldn’t tell
but u did
i no u
when we were in love
u said u wouldn’t run
but u did
i no u
when we were in church
u said u would love
but u couldn’t give
anything
at least anything that would make a difference
is it prejudice
2 believe in ur lack of vision?
is it hate
2 no u eye unseen?
i no ur way
u r 2 double minus signs
at the end of every name
u subtract everything
when u speak its to say “no”
when u look, it’s to not go
when u leave its because u’re too slow
we’re running and u’re laggin behind
in ur mind
we’re shining and u’re hidin in the rain
behind a name
we’re gonna to fly and u’re the one
with ur face to the back of the bus
icarus
he didn’t no what we no
he didn’t see what we see
the things we imagine
the things we create
the things we conceive
will come to be
but u can’t see
see?
i no u
Moving to Github
As one of my new year’s resolutions to save money, I’m moving my blog out of Drupal to Github pages. Basically Github pages, if you don’t already know about them, are run by a Ruby-based product called “Jekyll”. You create posts named correctly and created with Markdown, give it some theming info and it “compiles” the pages down into a series of static html pages which are then hosted by Github’s servers.
It’s a nice system. Also blogging with a text editor like ia writer is nothing short of awesome. One of the major criticisms of Drupal was the editorial experience. The process of content creation was perceived as being more difficult than a standard text editor.
No argument from me. I, personally, can’t stand CK editor and did all my Drupal posts in Markdown anyway using the Drupal Markdown Module.
How to choose a barber shop - part 1
The strip malls of America are littered with multiple franchise chains of hair cut shops and have relegated the humble father and son barber shop to a thing of legend and lore. But if you look carefully, you can still find a real all- American barber shop in most cities in America. Here’s some selection criteria to guide your search.
whats in a name?
First, the name should be the first or last name of the owner: Billy’s barber shop, Rick’s Barber Shop, Smith’s cut and shave, Jimmy’s, Habeeb’s and sons… Whatever the nationality, you’re buying a person’s expertise not a ‘hair philosophy.’ And preferably a male’s name, although the best haircut I ever got was from a lesbian barber. But her name was Sam, somewhat proving my point yet again.
Second, it should never contain a hair or grooming pun: ‘From Hair On’, ‘The Mane Event’. Ick. Run, don’t walk, in the other direction. Third, never a misspelling of cut or clippers. ‘Cutz’, ‘Scizzors’… Ew. My second grade teacher of a mother would take a red pen and correct the signs and letterhead. If you can’t be trusted to spell you profession correctly, I don’t trust you with my hair. ##Interior Upon walking in the front door, it should be clear that this is a place where real men have been discussing women, religion and politics since the Reagan administration. There should be no ‘theme’ in the decor other than barbershop. If there’s a television, it should be on sports.
If there’s a radio, it should be news or country. Never Fox News and never right-wing talk radio. There should be nothing offensive or overly sales-y. It should not be clear what political party any of the barbers belong to. All political signs should be local: ‘Elect Charlie Fox, City Council’ ‘Vote yes on Referendum 41: our kids deserve better schools’. It should be clear they care about their city or state but not in a ‘beat you over the head with it’ sort of way. There should be no large photos of stylish people doing things outdoors. If there’s any advertising it should be for grooming products that men use.
more soon
Chicken and pancakes part 2
Sunday morning a week or so after the first incident, walk back into the same iHop in San Bruno.
I want the chicken and waffles, but instead of waffles, I want pancakes.”
”I’m sorry, we can’t do that.” the iHop waitress said.
you can charge me extra, just substitute a short stack.
no,I’m sorry, we can’t do that.”
Um, you have chicken strips, right
Yes.
what about pancakes
jes, we have the pancakes.
…Then put them together on a plate and serve them to me.
I can’t do that. It’s chicken and waffles. That’s the special.
At this point, I get in the car and drive ten miles to the Denny’s in San Mateo. “Can I get the Chicken Strips dinner, but instead of sides I just want a short stack of pancakes.” “no sir, that’s the dinner menu. You can only get dinner sides.” How much power over the time/space continuum is required to create an order of chicken strips and add an order of pancakes to it
Waiter comes back several min later and let’s me know the manager ‘approved’ it. Apparently the manager has great power.
Beautiful Disaster
Part of me feels like the book is a complete disaster. While writing it I struggled because many of the mobile tools I wanted to use simply didn’t exist in Drupal 7 or they weren’t nearly mature enough to recommend to a development audience. 6-8 months later, they’ve all been updated and there’s big portions of the book that are either different or simply don’t apply. The drush set up is the big first one. Drush can now be installed from the PEAR repository with a few command line entries and drush make is included in the drush core. I have a couple of notes about the “upcoming drush 5” but after 5.2 was released this week, the instructions in the book seem particularly dated. Herein is the danger of committing anything to printed paper regarding web development: The industry moves at such a pace that it’s deprecated months after it’s printed. I’d love to take 3 months this summer and completely rewrite big portions of it, but there’s another part of me that says “Scrape your shoe and move on”.
Chicken, waffles and pancakes
I go to the iHop in San Bruno a lot for breakfast on days when I work from home. It’s usually empty and quiet on weekdays.
I want the chicken and waffles, but instead of waffles, I want pancakes.” ”I’m sorry, we can’t do that.” the iHop waitress said.
you can charge me extra, just substitute a short stack.
no,I’m sorry, we can’t do that.”
Um, you have chicken strips, right
Yes.
what about pancakes
jes, we have the pancakes.
…Then put them together on a plate and serve them to me.
I can’t do that. It’s chicken and waffles. That’s the special.
Can I see your manager
He’s not here right now
Bullshit, let me talk to you’re manager.”
He no es here right now.
Ok, so you have a Chicken fingers plate, right
jes.
can you leave off the fries and bring me a short stack
oh, jes! Jes! That I can do.
Read the follow up here
Install Drush 5 with MAMP Pro
I use a Mac with MAMP Pro to do local development. Sometimes the paths on MAMP Pro can be a little tricky and getting Drush installed may be more command line than you’re comfortable with. Here’s a quick way to get Drush installed in the command line with MAMP Pro. 1.
Make MAMP your primary php binary. So when you get a mac and install MAMP Pro there are now two versions of php installed on your machine. The one that came with MAMP Pro and the one that came with Mac OS X. You need to tell the command line that you want to use MAMP Pro’s PHP rather than the one that came with your mac. You do that by setting the path variable. At the command line type
> echo $PATH
and the command line will respond with something similar to this:
/sbin:/usr/local/bin:/usr/X11/bin
MAMP Pro’s copy of php is inside this folder:
/Applications/MAMP/bin/php/
There should be two versions: A php 5.3.x and 5.4.x. You can tell which version you’re using by opening MAMP Pro and choosing Server then PHP.
This version of MAMP Pro uses PHP version 5.3.6. so inside
/Applications/MAMP/bin/php/
is a folder 5.3.6. This is where the version of php lives that we want Drush to use. If Drush uses another version, you’re going to have problems with executing drush commands so lets add this version of PHP to the PATH variable. We do that by editing the .bash_profile
file in our User’s home folder and adding the following line:
export PATH=/Applications/MAMP/Library/bin:/Applications/MAMP/bin/php/php5.3.6/bin:$PATH
Save the .bash_profile file and close all Terminal.app windows. When you open a new Terminal.app window, try this:
echo $PATH
You should get something like this:
/Applications/MAMP/Library/bin:/Applications/MAMP/bin/php/php5.3.6/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/local/git/bin
when you type
which php
it should answer
/Applications/MAMP/Library/bin/php
when you type
which pear
it should answer
/Applications/MAMP/Library/bin/pear
You’re now ready to install Drush.
- Install Drush 5.0 or newer. Easiest way is through PEAR: if the console_getopt pear module is not installed, install it:
>pear install Console_Getopt
if it is installed
>pear upgrade --force Console_Getopt
>pear upgrade --force pear
>pear upgrade-all
>pear channel-discover pear.drush.org
>pear install drush/drush
If you installed Drush prior to March 31, 2012, please upgrade to 5.0. If you’re not sure which version you have installed,
>drush version
will tell you the currently installed version.
- Install drush registry rebuild. One change between Drupal 6 and Drupal 7 is a database table called “registry”. this table holds the location of all your module files. If those files or any of their associated classes for any reason change location your Drupal install will white-screen. The Jenkins build script which is in this directory in a file called
build.sh
As part of every build, this shell script instructs Jenkins to do a registry rebuild to fix any modules that might have moved since the last build and avoid white-screens when file locations change. if drush is installed correctly, you can simply
drush dl registry_rebuild
Drupal Migrations: the Feeds, Migrate & Deploy modules and when to use each
1. Feeds and Migrate: A difference in approaches. 1. Creating Feeds 1. Setting up a file-based feed 1. Setting up an fetch-based feed 1. Extending the feeds module 1. Writing Migrate module classes 1. the rollback class 1. the source class 1. the destination class 1. Putting it together 1. Moving your site from Wordpress or joomla to D7 1. Moving a site from another version of Drupal to D7 1. Moving your custom modules to D7 1. A Content staging workflow with the deploy module 1. Migrating users with federated logins 1. Migrating large document stores into Drupal nodes via Github

