version control - SVN atomic commit how-to -


Where am I: Linux Command Line

My problem is now:

Sometimes I could not do a nuclear act (to include all the necessary modifications for a particular ticket / work), because we have some files in the repository, which is different in the local development environment. For example:

database.xml (dbname, username, password, etc.). I modify this file in my local environment, and every time I need to commit / checkin, I manually list all the necessary files / folders for committed (this locally modified files Excluding).

Perhaps this is a wrong design decision and database.xml should be removed from the repository and database.xml.template (stored in SVN) Has been changed, so this file will not be included unless you manually do it to execute svn add ? It may be a misconception - it is all in store to store dependent information - in that case we can break everything through a modified configuration, for example ..

like That I understand it, svn: ignore property can not help in this situation because it can only be used for files that are not stored in the store.

< P> How to solve this problem What's that?

PS: I am using Ubuntu and mostly pure command line for SVN.

"Standard for this" is something like this (sorry for SVN syntax, I recently I'm using):

  resonance config & gt; Database.xml.template svn add database.xml.template svn ignore database.xml svn commit  

Then on each person's development machine:

  svn Checkout cp Database.xml.template database.xml ... edit database.xml ...  

and when they are committed,

  Echo foo & gt;  

database.xml will not be added to the file subversion.


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -