Does rake need to touch certain files in public directory?

Rails
1

Rails 2.0.2:

rake seems to be complaining when certain files in the public
directory are set to read-only.

An Example (using sample directory names):

myserver1=> rake db:drop
(in /my/application/directory)
rake aborted!
Permission denied - /my/application/directory/public/blank.html

If I make this file writable, then it seems to complain about another:

myserver1=> rake db:drop
(in /my/application/directory)
rake aborted!
Permission denied - /my/application/directory/public/stylesheets/
active_scaffold/DO_NOT_EDIT

Then if I make that file writable, then it seems to complain about
another:

myserver1=> rake db:drop
(in /my/application/directory)
rake aborted!
Permission denied - /my/application/directory/public/stylesheets/
active_scaffold/default/stylesheet-ie.css

When I look at those files, blank.html just seems to be touched, no
changes, however DO_NOT_EDIT actually becomes 2 bytes smaller
(strange).

–Matt

2

On Aug 6, 3:12 am, Matthew J Mucklo [email protected] wrote:

Rails 2.0.2:

rake seems to be complaining when certain files in the public
directory are set to read-only.

An Example (using sample directory names):

This is activescaffold specific I believe. It does generate some
assets in public on the fly.

Fred