Hello Racke and Nick, thanks for your replies. On Sunday 04.05.2014 11:55:39 Stefan Hornburg (Racke) wrote: > On 05/04/2014 09:19 AM, Lutz Gehlen wrote: > > On Saturday 03.05.2014 22:44:23 Nick Knutov wrote: > >> The good way is to use different environments (with different > >> passwords) and use config.yml only for common params. > > > > I had thought about environments, too. However, it looks like you can > > only load one environment file, or am I wrong? So I would have to > > duplicate the db settings in my current development.yml and > > production.yml and moreover would have to exlude those files from > > version control. > > > > I had hoped that there would be a way to modularize the config further > > in order to keep just the database settings or ideally just the login > > details in a separate file. > > > > In case this is not possible, am I approaching this issue in a > > completely wrong way? How does everyone else handle different > > database credentials on different machines? > > I using that approach above, database settings is going into > environments/*.yml and these files are excluded from version control.
I think I will follow that approach as well then. Cheers, Lutz _______________________________________________ dancer-users mailing list [email protected] http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
