Wish: Ability to set database creation file permissions in user configuration area

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Databases are created 644 owned by web user (www/apache/httpd)
2. Web user (www/apache/httpd) has full rw access
3. Drush (Drupal shell in ssh account) running in human user account 
(janebloggs) has only r access, so cannot update Drupal7/SQLite install with 
Drush

What is the expected output? What do you see instead?
Behaviour is as expected, but this is a wish. If SQLite database files are 
chmod 664 then all works, but in some scenarios the human using web account 
access via http (getting www/apache/httpd rights) is not the same human as that 
running Drush in ssh, especially if Drush is being remote-controlled by ssh, so 
it is not easy/possible for them to chmod the SQLite files.

What version of the product are you using? On what operating system?
V1.9.1 on FreeBSD 8.2 Release - works very well

Please provide any additional information below.
If there was a facility to set the umask for creating new sqlite databases this 
would be a gift to the people in the Drupal community who use both Drush and 
SQLite. Being able to create SQLite files 664 would be absolutely magic! Then 
end users can use http access to control everything while site builders can use 
ssh/remote ssh control.

Original issue reported on code.google.com by yippyb...@gmail.com on 22 Mar 2012 at 10:02

[GoogleCodeExporter]

I agree that this would be an excellent feature. We will try our best to 
implement it in a future release. If you manage to patch it yourself, send the 
code and we will include it in the next release.

Original comment by daneirac...@gmail.com on 2 Jun 2012 at 8:08

• Changed state: Accepted
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I agree that this seems to be a useful feature. Another use-case I can think of 
would be creating a DB as read-write, putting schema and data in it and then 
changing permissions to read-only.
Shouldn't be hard to implement (just a chmod(filename, 0664); for example. Only 
question is where to put the UI for this.

I think it should be possible to change file permissions any time (not only 
when creating a new db). So maybe we could add another tab "permissions" for 
databases?

Original comment by crazy4ch...@gmail.com on 23 Oct 2012 at 10:31

• Added labels: Type-Enhancement
• Removed labels: Type-Defect