Stefan Freudenberg

[There is no current general resolution to using directory-reserved paths, but it's surely possible with custom Apache rewrite rules-- apparently everyone concludes (as i am right now) that it's not worth the effort!]

Partial Resolution

To .htaccess, add:

    # Allow the modules path to be used by Drupal for the modules chapter.
    RewriteCond %{REQUEST_URI} ^/modules/?$
    RewriteRule ^ index.php [L]

Stefan's recommended approach:

For performance consulting, begin by asking whether they have high server load or just slow page loads. In the latter case we must first find out if it's the server or something else yslow can tell you.

In the case of high server load you should ask for the slow log. It would be nice if they had monitoring data for cpu ram and so on. Don't ask for full access to the data first. Some companies are really cautious about that and it's not necessary to get access for a starter.

A drush command. Text file with modules to enable on dev, and then run it manually or somehow automatically.

drush? make text file with all the modules and git it to drush pm_enable

If we have a defined practice for environment-specific module enabling/disabling and i'd love to disable views_ui, update, etc. on live

It would be run after sync commands-- pull data from live, but then enable update on the test site, and all site building modules on dev

stefan-agaric: this is how you can get all items from the solr index http://agaric.agariclabs.net:8180/solr/select?q=solr_id:[%TO%]
15:44 stefan-agaric: this also works http://agaric.agariclabs.net:8180/solr/select?q=%:%
15:46 mlncn: nice-- how do we actually do it in the search field though?

Stefan told me not to recommend scp -r ~/code/example username@host.example.com:/var/www/.

what is the s/find/replace syntax called?

Stefan:

that's called search and replace with regular expressions

ed is the line editor used by vi [which includes this]
sed is just a stream version of ed

s is the substitution command.

stefan:h ave you noticed that javascript and css aggregation does not work as expected on dgd7.org.
17:28 mlncn: how do you expect it to work? they changed it in D7, mostly for the better
17:28 stefan-agaric: there's 3 css and 2 js that seems to be created by it.
17:28 mlncn: there's more files, but they aren't recreated as often
17:28 stefan-agaric: what's the point?
17:29 mlncn: or rather, i should say, there's more files per page but fewer files when browsing around the site
17:29 stefan-agaric: we only need one.

Apache will also log errors to:

syslog

Stefan notes: in case of panic you can try to grep -R in /var/log for PHP Fatal error

Benjamin Doherty says this is covered in the DGD7 environment chapter.

If not installed yet:
sudo apt-get install nmap

$ nmap sojourner.mayfirst.org