Wordfence + GIT (what to add to gitignore)?
-
We’re running Wordfence on a site that’s managed via GIT as part of the development workflow. I’m wondering which files should be added to the gitignore file (keeping them untracked/out of GIT).
I’m thinking the following files should be added, but would appreciate advice:
wp-content/plugins/wordfence/tmp/**
wp-content/wflogs/**
wp-content/wfcache/**My reasoning behind this is we don’t need tmp, log and cache files, generated in non-production environments (local dev, dev and staging sites, all of which of which are password protected/non-accessible), overwriting tmp, log and cache files on the production environment, whenever code is pushed live.
Would appreciate advice from the devs, if possible?
-
Hi @theboyk, thanks for your question.
I’ve spoken to the team and have the following information:
wp-content/plugins/wordfence/tmp/is no longer used and will be removed in a future plugin version. It’s ok to ignore, but it shouldn’t contain anything anyway.wp-content/wfcache/should have already been removed, but it’s possible that permission issues prevented it. If there are any recent files there, they’re not from Wordfence. If there are no recent files there, it should be safe to remove entirely. Keep a backup in case some plugin happened to use the same name, but it seems unlikely.wp-content/wflogs/is fine to add to gitignore, though it includes both logs and configuration if not using the MySQLi storage engine. Again, it’s good to keep a periodic backup, but it makes sense to not to overwrite it on prod when pushing new code.Please also note that wordfence-waf.php, .htaccess, and/or .user.ini might be different on the various environments, if they have different paths.
Thanks,
Peter.
- The topic ‘Wordfence + GIT (what to add to gitignore)?’ is closed to new replies.
