Hey Likun,

True. How about we use the app directory and then go up the tree to see if any parent has a settings file?

Also I can add an option for the name of a settings file. But it will fall back to 'settings.yml'. Is that reasonable?

The problem is that the settings file is only used for development and isn't used in deployment. One of the problem of having the settings in the app directory is that the settings aren't app specific, but app and client specific. If I would have the settings in the app directory all the settings for all clients would end up in the zip file.