Making folders writable

Comments

• Lance

  December 2010 edited 11:36AM

  In the same vein.. The install notes on .91 say to make the "/fuel/codeigniter/cache/dwoo/compiled" directory write-able.
  
  I found I have to make the dwoo directory (so one up) writable otherwise error city.. On OSX 10.5.8/xampp and OSX 10.6.x/Apple install
• admin

  December 2010 edited 11:36AM

  Thanks Lance. I've updated the install directions to include that folder as well.
• shinokada

  December 2010 edited 11:36AM

  And if you are using Ubuntu, this is it.
  https://help.ubuntu.com/community/FilePermissions
• mblos16

  June 2011 edited 11:36AM

  So.... does this need to be 777 or can it be 766?
• admin

  June 2011 edited 11:36AM

  I think that may depend on your server/user setup for 766 permissions working.
• pfote

  October 2011 edited 11:36AM

  @mblos16
  standard setup is to chown the directories to the user the webserver runs under, and set permissions to 755
  
  777 is almost always a bad idea for a directory accessible through the webserver, as soon as someone finds (for instance) a sql injection loophole, you'll have unwanted visitors on your server
• starsinmypockets

  February 2012 edited 11:36AM

  I'm having a problem with file ownership when writing to an assets folder subdirectory. In my case, fuel is accessing my server as 501:admin (user group). I've created the subdirectory assets/gallery_images, and given it 501:admin ownership, and 777 permissions. However, when I save to this directory (using the simpleimage image processing class) the file is given www-data ownership, essentially locking fuel out from further interactions with the file... Any thoughts here are appreciated...