I noticed that I had a large drushrc.php file (test site):
2750788 Mar 20 23:04 drushrc.php

I was wondering if it would be of benefit to gzip this file.

I am not sure if that would be possible or beneficial.

Comments

SocialNicheGuru created an issue. See original summary.

jon pugh’s picture

jon pugh
he/him
Primary language English
Location Newburgh, NY
commented

For some reason, Aegir stores tons of metadata about your site's modules in this drushrc.php file.

I really don't know why. Perhaps we should look at cleaning this file up, unless there is a really good reason for having this data in there that I'm just not aware of.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
commented
Status: Active » Closed (works as designed)

The short answer is "no". drushrc.php files ought never be served via the webserver to begin with. They contain DB credentials, so that commands like drush @example.com sqlc work. As a result, they should be owned by aegir:aegir and have mode 0440, i.e., only readable by the aegir user.

The $options['packages'] array, which makes up by far the majority of these files, contains a listing of all the modules, themes, etc. on the site, along with meta-data about them (e.g., versions, etc.) This is rebuilt on each 'verify' task, and passed back to the front-end, to populate the 'Packages' tables that, in turn, are used to compare platforms, flag warnings and errors, if modules have been removed, are being downgraded, etc.