Agaric

A lot of this will apply for any small business (and won't apply to huge worker cooperatives, although technically our three-member collective is a multinational).

Set old_type if you want to programmatically update a node type / machine name.

(This is not about changing the type of a node, but changing what type is called on the machine-info level.)

$type->old_type is what node_type_save() checks for when updating a node type, if it's not set it will create a new node type even if orig_type is set to an existing bundle. So really all you need to do right before saving a modified content type is set the old_type to the orig_type, such as:

This has to be done for each site. This is after installing Memcache on your server.

Memcache module

Then, in settings.php, add:

These notes accompany a presentation given at BioRaft Drupal Nights and at NYCcamp.

The image-heavy (but often context-light) presentation slides are on Prezi.

As a completely hypothetical example, suppose you boneheadly thought it would be nice to standardize your local login name to something different than on some existing servers.

You want standard scripts that assume current username to work— you wrote them to share, after all. So how to make this work?

Something like this in your ~/.ssh/config file (create and chmod 600 if it doesn't exist already) will work:

Host agaric-test
Hostname test.example.org
User bmelanco

Micky found this which was key to debugging our connection problem— one way to watch what is happening with the SSH connection attempt is by opening a port just for this use on the server:

sudo /usr/sbin/sshd -d -p 2222

Then from the client:

ssh -vv -p 2222 example.com

Per http://www.unixlore.net/articles/troubleshooting-ssh-connections.html

Create an SSH key

Send a copy of the public key to an agaric with access to the test server to add it there. Read more about setting up public keys and agent forwarding.

Get Drush

Follow composer instructions on https://github.com/drush-ops/drush (preferred over apt-get or PEAR.)

Stefan set up the kgb-bot to post in the Agaric IRC channel when anyone pushes a commit to one of our repositories. These repositories are hosted on our server, and each one needs to have a very simple bit of configuration added to it and to the KGB server configuration when we add one.

Here's the easiest way for me to do that. For information about getting started with KGB in the first place, see http://www.donarmstrong.com/posts/switching_to_kgb/

Agaric decided to make a contributed module to do this: http://drupal.org/project/usersearchtoadmin

See that project page. The below is mostly notes on wrong turns!

It would be nice if this just used a different permission other than a person's ability to access profiles:

A principal at Agaric regrettably uses Microsoft Windows as a primary operating system. In fact, though, everything works great for him using the open source integrated development environment Eclipse to develop, including using the eGit plugin-- except when something goes wrong, and my (limited) command line knowledge of Git is useless to help him.

Fortunately, it turns out to be pretty easy to have command-line Git on Windows with Eclipse, it just isn't well documented.