Return to Answer

Programming, Administering, and Using are different aspects to computing.

• A programmer builds an application - and exposes configuration hooks that can cause the program to execute different paths.
• An administrator reads the program's documentation, and alters the configuration to suit their environmental needs.
• The user is oblivious to these aspects, and is not relevant to this discussion.

Changing the configuration of the program does not actually change the program's behaviour, it just changes the parts of the program that are exercised, and, thus, the configuration is not actually code.

So, in my opinion, the config file is not code, and thus is not on-topic on Code Review.

The counter-argument about .htaccess files, is that the regular expressions really are micro-programs, that are embedded in a containing system. The regular expressions are compiled, and changing the regular expression changes the bahaviour of the regex engine. The rest of the .htaccess fill is just 'context' for the regex program.

The bulk of the specific question would best be answered on Server Fault for systems in a business environments, or on Super User for hobby/single user systems.

Programming, Administering, and Using are different aspects to computing.

• A programmer builds an application - and exposes configuration hooks that can cause the program to execute different paths.
• An administrator reads the program's documentation, and alters the configuration to suit their environmental needs.
• The user is oblivious to these aspects, and is not relevant to this discussion.

Changing the configuration of the program does not actually change the program's behaviour, it just changes the parts of the program that are exercised, and, thus, the configuration is not actually code.

So, in my opinion, the config file is not code, and thus is not on-topic on Code Review.

The counter-argument about .htaccess files, is that the regular expressions really are micro-programs, that are embedded in a containing system. The regular expressions are compiled, and changing the regular expression changes the behaviour of the regex engine. The rest of the .htaccess fill is just 'context' for the regex program.

The bulk of the specific question would best be answered on Server Fault for systems in a business environments, or on Super User for hobby/single user systems.

Programming, Administering, and Using are different aspects to computing.

• A programmer builds an application - and exposes configuration hooks that can cause the program to execute different paths.
• An administrator reads the program's documentation, and alters the configuration to suit their environmental needs.
• The user is oblivious to these aspects, and is not relevant to this discussion.

Changing the configuration of the program does not actually change the program's behaviour, it just changes the parts of the program that are exercised, and, thus, the configuration is not actually code.

So, in my opinion, the config file is not code, and thus is not on-topic on Code Review.

The counter-argument about .htaccess files, is that the regular expressions really are micro-programs, that are embedded in a containing system. The regular expressions are compiled, and changing the regular expression changes the bahaviour of the regex engine. The rest of the .htaccess fill is just 'context' for the regex program.

The bulk of the specific question would best be answered on Server Fault for systems in a business environments, or on Super User for hobby/single user systems.

Programming, Administering, and Using are different aspects to computing.

• A programmer builds an application - and exposes configuration hooks that can cause the program to execute different paths.
• An administrator reads the program's documentation, and alters the configuration to suit their environmental needs.
• The user is oblivious to these aspects, and is not relevant to this discussion.

Changing the configuration of the program does not actually change the program's behaviour, it just changes the parts of the program that are exercised, and, thus, the configuration is not actually code.

So, in my opinion, the config file is not code, and thus is not on-topic on Code Review.

The counter-argument about .htaccess files, is that the regular expressions really are micro-programs, that are embedded in a containing system. The regular expressions are compiled, and changing the regular expression changes the bahaviour of the regex engine. The rest of the .htaccess fill is just 'context' for the regex program.

The bulk of the specific question would best be answered on Server Fault for systems in a business environments, or on Super User for hobby/single user systems.

Programming, Administering, and Using are different aspects to computing.

• A programmer builds an application - and exposes configuration hooks that can cause the program to execute different paths.
• An administrator reads the program's documentation, and alters the configuration to suit their environmental needs.
• The user is oblivious to these aspects, and is not relevant to this discussion.

Changing the configuration of the program does not actually change the program's behaviour, it just changes the parts of the program that are exercised, and, thus, the configuration is not actually code.

So, in my opinion, the config file is not code, and thus is not on-topic on Code Review.

The counter-argument about .htaccess files, is that the regular expressions really are micro-programs, that are embedded in a containing system. The regular expressions are compiled, and changing the regular expression changes the bahaviour of the regex engine. The rest of the .htaccess fill is just 'context' for the regex program.

The bulk of the specific question would best be answered on Server Fault for systems in a business environments, or on Super User for hobby/single user systems.

Programming, Administering, and Using are different aspects to computing.

• A programmer builds an application - and exposes configuration hooks that can cause the program to execute different paths.
• An administrator reads the program's documentation, and alters the configuration to suit their environmental needs.
• The user is oblivious to these aspects, and is not relevant to this discussion.

Changing the configuration of the program does not actually change the program's behaviour, it just changes the parts of the program that are exercised, and, thus, the configuration is not actually code.

So, in my opinion, the config file is not code, and thus is not on-topic on Code Review.

The counter-argument about .htaccess files, is that the regular expressions really are micro-programs, that are embedded in a containing system. The regular expressions are compiled, and changing the regular expression changes the bahaviour of the regex engine. The rest of the .htaccess fill is just 'context' for the regex program.

The bulk of the specific question would best be answered on Server Fault for systems in a business environments, or on Super User for hobby/single user systems.