Issue #7679 has been updated by Nigel Kersten. Status changed from Needs Decision to Needs More Information Assignee deleted (Nigel Kersten) Priority changed from Normal to Low
We're not going to blaze new ground here. I'd appreciate seeing other efforts to make web/rails apps FHS compliant before we go in that direction. ---------------------------------------- Bug #7679: FHS compliance https://projects.puppetlabs.com/issues/7679 Author: Guillaume Rousse Status: Needs More Information Priority: Low Assignee: Category: Target version: Keywords: Branch: Affected URL: Affected Dashboard version: Dashboard assume a single top-level directory setup, containing configuration, read-only data (app, db) and read-write data (public, tmp, log). This is not compliant with FHS, which requires than those different kind of content should be kept separated. FHS compliance could be achieved through symlinks, but native support in the application would be better. Also, the installation guide explains than the whole installation tree should belong to the specific user id dashboard is running as, but this is false. Actually, the dashboard user only need write access to the 3 writable directories, read access to the database.yml configuration file. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
