cleaning up vagrant and various other files. fixing docker compose startup
This commit is contained in:
@@ -66,9 +66,6 @@ gem 'jquery-rails'
|
||||
# To use ActiveModel has_secure_password
|
||||
gem 'bcrypt'
|
||||
|
||||
# To use Jbuilder templates for JSON
|
||||
# gem 'jbuilder'
|
||||
|
||||
# Use unicorn as the app server
|
||||
gem 'unicorn'
|
||||
|
||||
@@ -76,14 +73,6 @@ gem 'jquery-rails'
|
||||
gem 'powder'
|
||||
|
||||
gem 'aruba'
|
||||
|
||||
|
||||
# Deploy with Capistrano
|
||||
# gem 'capistrano'
|
||||
|
||||
# To use debugger
|
||||
# gem 'debugger'
|
||||
|
||||
gem 'execjs'
|
||||
gem 'therubyracer'
|
||||
|
||||
|
||||
Vendored
-13
@@ -1,13 +0,0 @@
|
||||
VAGRANTFILE_API_VERSION = "2"
|
||||
ENV['VAGRANT_DEFAULT_PROVIDER'] ||= 'docker'
|
||||
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
|
||||
config.vm.define "railsgoat" do |rg|
|
||||
rg.vm.provider "docker" do |d|
|
||||
d.image = "owasp/railsgoat"
|
||||
d.name = "railsgoat"
|
||||
d.ports = ["3000:3000"]
|
||||
d.vagrant_vagrantfile = "./Vagrantfile.proxy"
|
||||
end
|
||||
end
|
||||
|
||||
end
|
||||
@@ -1,10 +0,0 @@
|
||||
VAGRANTFILE_API_VERSION = "2"
|
||||
|
||||
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
|
||||
config.vm.box = "hashicorp/precise64"
|
||||
config.vm.provision "docker"
|
||||
config.vm.provision "shell", inline:
|
||||
"ps aux | grep 'sshd:' | awk '{print $2}' | xargs kill"
|
||||
|
||||
config.vm.network :forwarded_port, guest: 3000, host: 3000
|
||||
end
|
||||
+1
-1
@@ -2,7 +2,7 @@ version: '2'
|
||||
services:
|
||||
web:
|
||||
build: .
|
||||
command: bundle exec rails s -p 3000 -b '0.0.0.0'
|
||||
command: bash -c "rm -f tmp/pids/server.pid && bundle exec rails s -p 3000 -b '0.0.0.0'"
|
||||
volumes:
|
||||
- .:/myapp
|
||||
ports:
|
||||
|
||||
@@ -1,11 +0,0 @@
|
||||
# simplest.attack
|
||||
Feature: simplest attack possible
|
||||
Scenario:
|
||||
When I launch a "generic" attack with:
|
||||
"""
|
||||
ls -a
|
||||
"""
|
||||
Then the output should contain:
|
||||
"""
|
||||
.
|
||||
"""
|
||||
@@ -1,17 +0,0 @@
|
||||
#sqlmap.attack
|
||||
Feature: Run sqlmap against a target
|
||||
# See:
|
||||
# https://github.com/sqlmapproject/sqlmap/wiki/Usage
|
||||
|
||||
Scenario: Identify SQL injection vulnerabilities
|
||||
Given "sqlmap" is installed
|
||||
And the following profile:
|
||||
| target_url | http://localhost:300/|
|
||||
When I launch a "sqlmap" attack with:
|
||||
"""
|
||||
/usr/bin/python <sqlmap_path> -u <target_url> --dbms sqlite
|
||||
"""
|
||||
Then the output should contain:
|
||||
"""
|
||||
sqlmap identified the following injection points
|
||||
"""
|
||||
Reference in New Issue
Block a user