Menu
I am working on a large web project which is managed in an SVN repository.
Each time a team member checks out the project, or we check out the project on a new production server, we have to modify a custom configuration file for that server. I have a "config.ini.base" file under revision control, which we keep updated with the latest settings, the idea being that team members copy that to create their "config.ini" (which is listed under 'ignore' on the directory).
To avoid confusion and mistakes, I'd like to somehow block any changes to "config.ini.base" from being committed to the repository, unless it is committed explicitly or the read-only setting is somehow explicitly overridden. How would I do this?
933
Find your Subversion repository in the list of repositories and click on Actions > View... Go to the Updates tab. Make the "Use the system default settings for updates" option is unchecked. Check the "Disable polling" option.
If you need to manage access via svn:// protocol (embedded authorization), all you need to do is to change files in conf folder of your newly created repository: Set up passwd ( repos/conf/passwd ) in order to define a list of users and passwords.
SVN stands for Subversion. So, SVN and Subversion are the same. SVN is used to manage and track changes to code and assets across projects.
Subversion does not version permissions. There exist 2 wrapper scripts which you can use instead of “svn” for commit, checkout, update, etc., and store permissions in properties. They are: asvn and svn+perms. Last but not least there is a patch which adds the functionality into the svn core.
svn lock
Also, worth a read is Advanced Locking
173
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
