I'm considering setting up a utility vm that's non project-specific. This could host squid, bind, jenkins, gitlab, maybe an api.module-based site, etc. These are tools that should be shared across projects, and be reasonably persistent.

For a squid cache, here are some docs about using it with Drush: http://reluctanthacker.rollett.org/using-squid-caching-server-drush-modu...

Comments

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
commented
Assigned: Unassigned » ergonlogic

Here's an Aegir-specific write-up of how to install Squid: http://community.aegirproject.org/handbook/administrator/post-install-co....

patcon’s picture

patcon commented

Just looking into this myself now. Drush had caching for "drush dl" in 4.x, and now that make is in 5.x and uses the pm primitives to download files, there's almost no need for squid caching, if I'm not mistaken.

Squid caching (while faster memory-based rather than filesystem) can't deal with git repos, and drush caching can (using the --reference option for git, to clone local repos elsewhere on the system that get pulled in). So I think drush caching is the best all-round solution. Could use both, but two layers of caching might just lead to confusing problem-solving down the road.

Anyhow, just a thought :)

Squid caching still might be useful for other things (haven't tested how drush handles libraries)

RElevant: http://drupal.org/node/581348