oooh, sounds like a candidate for a drush extension. See http://drupal.org/project/drush and http://drupal.org/project/drush_extras In its version two in Drupal 6, for example, drush exists entirely outside of Drupal, so on a production server with several different sites, or on your own development box or testing machine, you can install once and run many times. Moreover, it is not a module, but a self-contained system. And the cool part is that in your home user directory you can store easy-to-write extensions, starting with drush_extras (./home/drush). Victor Kane http://awebfactory.com.ar On Wed, Feb 11, 2009 at 1:50 AM, Jon Antoine <antoinesolutions@gmail.com>wrote:
After installing Drupal many times and having to check file permissions to make sure the site was secure, I got to thinking about how to automate this process. I started by writing a script to take care of this, but eventually I thought a Drupal module might be the way to go. The module could provide a hook, say hook_file_security, that would take an array of files names and their suggested security parameters. This could work very similar to the updates module providing information on the admin/reports/status page and an admin/reports/file-security page that displayed all installed modules, their files, the suggested security settings, and the current security settings.
Well, that is the base idea I had. I think something like this would really help new users of Drupal and I'm pretty sure it's possible since the installation script reports on the security settings of the files directory and the settings.php file. Any thoughts, ideas, suggestions are welcome.
Cheers,
Jon