summaryrefslogtreecommitdiff
path: root/DEVELOP
diff options
context:
space:
mode:
authorFlorian Pelgrim <florian.pelgrim@craneworks.de>2014-10-25 10:38:18 -0400
committerYaroslav Halchenko <debian@onerussian.com>2014-10-25 10:38:18 -0400
commit3dabd5fc833e2546d4715366126ac600a2088614 (patch)
treed8c0c05cb0d1c9540c67311f61e3c40e17fdcf26 /DEVELOP
parent6293e448895cc342ef83f005a92f304a5d783c3d (diff)
downloadfail2ban-3dabd5fc833e2546d4715366126ac600a2088614.tar.gz
DOC: documentation about available vagrantfile setup
manually picked up from a commit within https://github.com/fail2ban/fail2ban/pull/786
Diffstat (limited to 'DEVELOP')
-rw-r--r--DEVELOP12
1 files changed, 12 insertions, 0 deletions
diff --git a/DEVELOP b/DEVELOP
index f1426561..1384a6ac 100644
--- a/DEVELOP
+++ b/DEVELOP
@@ -81,6 +81,18 @@ some quick commands::
status test
+Testing with vagrant
+--------------------
+
+Testing can now be done inside a vagrant VM. Vagrantfile provided in
+source code repository established two VMs:
+
+- VM "secure" which can be used for testing fail2ban code.
+- VM "attacker" which hcan be used to perform attack against our "secure" VM.
+
+Both VMs are sharing the 192.168.200/24 network. If you are using this network
+take a look into the Vagrantfile and change the IP.
+
Coding Standards
================