I use an automated routine to handle this. I set svn:ignore before I ever modified databases.yml so that takes care of import. On export on the production server, I add the DSN to databases.yml inside the shell script that I use to export from svn and run a few other housecleaning chores in the process.
Charley [EMAIL PROTECTED] said on Friday, January 25, 2008: > >Hey everyone, > >I am currently looking for a way to keep the passwords and in fact the >entire MySQL URL (propel.database.url / propel.database.createUrl) used >in propel.ini in a separate file. > >The main reason behind this is keeping passwords from being committed to >SVN. Furthermore, when the Symfony project is checked out on another >machine the connection info will likely have to be changed. While this >is no problem care has to be taken not to commit it back to the >repository once the connection info has been modified and when the >actual contents of the propel.ini are changed there may be conflicts. > >The same issue applies to the database.yml but from what I have read >(not tried it yet) Symfony allows PHP code in .yml files thus allowing >to pull in the connection info from an external file not maintained in >the repository. Unfortunately this doesn't seem to be possible for >propel.ini. So, is there a similar mechanism for propel.ini that I am >missing? > >Thanks, >Georg > >> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
