Should .htaccess be the version in the source control?

If you adhere to the principle that the application should be launched “out of the box” when exiting version control, it .htaccessshould be enabled. Something is not so good about this, as it really is not part of the application. I'm in conflict, could anyone calm down?

+4
source share
2 answers

I usually save the .htaccess application in the original control, which includes the Apache configuration necessary to run the application, i.e. rewrite rules that are not related to the server on which it is running, access to environment variables, etc.

: .htaccess , , , , .

, , , .htaccess, , . , Apache .htaccess, VirtualHost, , .

+6

, , "".

, , .htaccess , . , ( ..) , ( URL-, / ..). , , , , , .

. ( ):

  1. - , . , .htaccess , - Apache VirtualHost. , , Apache .
  2. .htaccess , , ### FOO APPLICATION SETTINGS - DO NOT CHANGE ### ### ADD ANY ADDITIONAL LOCAL CONFIG BELOW THIS LINE #### . , , , , , , , , . , (, , dev-, ), , , (, ). zipfile).
  3. , , - .htaccess.sample , ( ) , . , , , .htaccess. , , .
  4. , №3, , . , , , (, ) , , , . , WordPress , .
0

All Articles