User login

Agaric

Pushing our local repository to Gitorious


git checkout master
git remote add origin git@gitorious.org:remarkup/remarkup.git
git push origin master

This was for a module named "remarkup" as covered in http://definitivedrupal.org/node/90

Manually setting up fcgi wrapper permissions

ssh root@agaric-prod
vi /home/members/agariclabs/sites/agaric.com/.red/apache2/apache.conf

Add these two lines inside the VirtualDirectory:

        FCGIWrapper /home/members/agariclabs/sites/agaric.com/bin/php-cgi .php
        SuexecUserGroup agaric agaric

Then copy the bin directory with php-cgi in it from another project and set the permissions to the same user group defined there.

Cloning git locally to test a Drupal module in development on multiple sites

Working on a site (DefinitiveDrupal.org) which is in its own big Git repository. But when working on a module that's custom to the site but probably will become generalized and contributed back, we simply git init in that module's directory to make it a repository too. No git submodules or other voodoo. In addition to getting us an independent commit history for that module, it gives us the ability to throw that module into other situations and work on it there.

Agaric internal: internal funding during paid projects; own currency; and strategy notes

[Draft - internal policy thoughts shared with the world for openness - but not official at all]

Our rates and billing assume some amount amount of work for particular projects will go unpaid by the client.

In particular, we should budget 6 hours for pre-project work in acquiring a project and 12 hours making sure everything is awesome.

Those hours may change but let's keep that 1:2 ratio.

Agaric's Trac workflow

This is in etc/trac/trac.ini. Note that each project can override in its own trac.inin (which for Agaric's system is in /srv/trac/PROJECTNAME/conf/trac.ini).

[Agaric-specific] Set up a Trac issue queue for a project

Visitors, please note that while Agaric-specific documentation may be informative to you, it is meant primarily for Agaric's internal use and is highly unlikely to work step-by-step without fulfilling an awful lot of dependencies first.

After setting up the project per Deploying the Agaric way, we can use our trac setup vlad task to do most of the work.

From within the project:

rake test vlad:setup_trac

Syndicate content