Ignorirovanie files already tracked?

usually configuration files are in a separate folder, and we don't swapon and apim only the folder ID.

If I understand correctly, you will only work with a centralized brunches. In our project, no one works with trunk, per trunk similar files have a standard configuration. And every developer working on your branch, changes these config files by themselves. As far as I know, in svn you cannot do as you want, except to write their clever hooks to the server that is if that reverting such files on the trunk or something. But IMHO it is somehow svetnenko.

1) is Created database_config.example.php where are the actual settings
2) It is added to the repository
3) For directories in which it lies dobavlen svn:ignore = database_config.php
4) After chakuuta create a copy database_config.example.php with the name database_config.php and specify in it the individual settings
\r
Of the disadvantages only what is necessary from time to time to update your database_config.php when you add settings in database_config.example.php

The option is similar to the previous one, but he is not the same to use something like inheritance or cascade: Yes database_config.common.php where described the model configuration and which versionseries (there is a new feature in the project default settings there committse and crawl on all developers), and ignored VCS database_config.instance.php which are overridden, only the necessary settings. Roughly speaking, the first recorded host, port, user, password, database, prefix, and the second overrides only the user, password, and database or only the host.

svn:ignore won't work for file that is already attached to the turnips

have you tried locking? Turtles have a description of the action (EN, EN)
\r... If you lock the file, then only you will be able to fix this file. Fixing other users will be blocked until then, until you release the lock. A locked file cannot be modified in the repository in any way, and this means that it cannot be deleted or renamed either, except by the lock owner...