This website is composed of information connected through taxonomy. It is simultaneously a proof-of-concept and a means to allow Agaric to share and store information both within the collective and the world as part of our open documentation philosophy.

User login

This website is composed of information connected through taxonomy. It is simultaneously a proof-of-concept and a means to allow Agaric to share and store information both within the collective and the world as part of our open documentation philosophy.

Drupal ingredient-dish-meal code-module-site analogy, and different cooks and restaurants

Code as ingredients, modules as dishes, sites as meals, installation profile as recipe, and restaurants with a menu as providers of distributions (or SaaS, though she doesn't mention that).

That's the takeaway from today's post by Karen Borchert at Agile Approach.

http://www.agileapproach.com/blog-entry/code-free-explanation-of-drupal-distributions

To find out what is making a cron run very long (or failing)

A bunch of functions run when cron is run, to find out what is causing the overall run to take a long time (possibly timing out and breaking), you need to look at them piece by piece. This code does that:

http://drupal.org/project/drush_debug_tools

Code courtesy Tim Hilliard and tip courtesy George Cassie.

When the Minimim Viable Product isn't Minimum, or when Viable is a matter of time

Many products depend on community, on adoption within a tribe, on buzz--these products aren't viable when they first launch, precisely because they haven't been adopted. "Being used by my peers," is a key element of what makes something like a fax machine a viable product, and of course, your new tool isn't.

With enough patience and push and consistent enthusiasm, these products have a shot at crossing the threshhold. But if the mindset is "see what works and do it more," you'll often discover yourself giving up long before that happens.

Share your bash command line history among all open terminals.

Just put
PROMPT_COMMAND="history -a; history -n"
in your .bashrc. This command is executed every time before a new prompt.
history -a
appends local history changes to the .bash_history and
history -n
fetches fetches changes in .bash_history.

For OSX, use ~/.profile instead of the .bashrc file.