ringo-admin --config option fails if config file is not is src folder.

[toirl]

Usually the ringo-admin command will use the development.ini configuration file as default which is located in the "src" folder of the application.

In case you copy the development.ini into production.ini (e.g) in another location which is not within the src then the following command will fail (At least for the ringo-admin user passwd command).

When invoking the command next to the production.ini

ringo-admin --config production.ini ...

will result in:

IOError: [Errno 2] No such file or directory: '/production.ini'

A workaround is to provide the absolut path of the configuration file.

The expected behaviour should be that the the config file should always be loaded relativ the the CWD of the command as long as not provided as absolut path. Default name for development.ini is ok.