Recommended version control practices

  • We track our entire WordPress codebase in version control (Git) and run our site in separate dev/staging/production environments. To avoid automatic changes to WordFence files that could have negative effects across separate environments, do you have general recommendations about which files to ignore? For example, wordfence-waf.php appears to have a hard-coded absolute path which we would obviously not want to propagate from one environment to another.

    Thanks,
    Coby

Viewing 1 replies (of 1 total)

  • Hi Coby,
    Another thing that you may want to consider is the firewall configuration files at (/wp-content/wflogs/), according to the Firewall Settings, these files content gets changed.

    Also, “.htaccess” or “.user.ini” -depending on your server configuration- includes path to “wordfence-waf.php” file.

    Thanks.

Viewing 1 replies (of 1 total)
  • The topic ‘Recommended version control practices’ is closed to new replies.

Tags