svn - How do you sanitize your source before doing a subversion commit? -


Sometimes when you are working with your local copy, you have stored the configuration settings that you are bound to Do not want to be unresponsive and to ignore the file as there are also application specific settings. For example, a Django settings.py file contains both the database connection details and the project settings, such as which application to load.

Is there any way to secure these types of files when they are committed? And then what's the way to restore your local settings during a checkout?

My existing environment is Linux and Command Line Subversions

settings.py.example , "itemprop =" text ">

In your copy of the work, you settings.py.example to settings.py and work with copy. If you need to make any changes to the standard configuration, then change settings.py.example and check it. Otherwise, you will not need to change it, and your revised code is not even under the settings.py version control, so it does not take into account (you can call it svn: ignore In the property it can be included to make it more agile).


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -