User login


Updating old Agaric projects to new Rake system

Superseded, see setting up new Ubuntu computer Agaric style.

This is Agaric internal documentation, related to Deploying the Agaric Way. Make sure that you have a checkout of the siteproj 'base' project. If not, git clone it into your file system.

These instructions should be good for all legacy projects:

Using Drush to list your modules and their statuses: drush sm (for show modules)

On the command line and want to list the modules you have on your site? Fortunately, there's a module-listing command that Agaric's Stefan Freudenberg contributed to Drush.

drush sm

Think "show modules" to remember sm. (The official full name of the command is pm-list which is confusing so just ignore it.)

You can do all your usual fancy command line things:

ben@ubuntu:~/code/agaric/web$ drush sm | grep Views

Drupal wish: Configuration setting to make all content types default to create new revision

Update: All this is superseded by an existing module,

Requests for this feature go all the way back to the days of Drupal 4.6, at the least:

create new revision by default
(4.6 era post!)

This feature remains wanted-- here is the manual instructions, for!

Personal site style marketing brainstorm

was node/1379


Kerberos user creation and password changes for Agaric test sites

Everyday use

You can change your password at

Or when logged in to with kpasswd (first type your current password, and then your new one, twice).

Initial setup of a user via the command line

These commands can be run on Agaric's test server,

First, to see if a username already exists, you can list them with listprincs:

Create a new user on Agaric's test server at MayFirst/PeopleLink

Creating a public key

The user to be added (we'll call him Andrew) types this in his terminal:


Then he sends his public key to the person acting as sysadmin at the moment. As an e-mail attachment is fine. For users not used to the command line it can be hard to find the public key in a hidden .ssh folder, but it is possible to use scp to put it on a server both the user and the acting sysadmin have access to.

Adding the user to the server

The sysadmin then logs into the test server and uses standard Debian commands:

Value Pricing

Jon Lax

There will be scenarios where the success portion takes months and you may not be in a position to wait for those results due to your business situation. For us, let’s say we have a client who wants to increase twitter followers. We quote the project as follows…

Deploying the Agaric way


Where we come from

After journeying from Capistrano to Vlad we eventually use pure Rake tasks for our deployment. While Vlad was a great improvement it also had downsides. Lack of feedback from tasks made it hard to tell why they failed. Also the most interesting feature of those deployment tools is not required in our case: The ability to roll out to many servers at the same time.

Syndicate content