Deploy version control configuration files

I have a particular problem with configuration files and deployment. When I deploy my project, it ultimately moves on to two different sections: staging and production (using SVN here)

I am making a branch from my local working copy of the project. What this does is overwrite the intermediate and configuration copy of the configuration files, so I have to manually enter and make the correct changes every time I deploy.

Does it make sense to delete configuration files from SVN completely since it is installed in stone? Or is there any other way to do this?

+3
source share
2 answers

, (, , ). . , :

  • script
+2

SVN - .

SVN svn: ignore, . , , SVN , .

.

A: .

  • cd trunk/blah, , , .
  • svn propedit svn:ignore . . .
  • , (), . , *.txt , SVN , .txt. config.php , SVN config.php.
  • .
  • . svn commit -m "New Ignores"

B: SVN .

  • cd trunk/blah, , , .
  • svn propset svn:ignore config.php ., SVN, config.php.
    • . svn commit -m "New Ignores"

svn: ignore. " SVN."

+1

Source: https://habr.com/ru/post/1757528/


All Articles