Skip to content

Commit 86bc7dc

Browse files
committed
Actually remove the cloud installation instructions
(rather than just their links in the ToC)
1 parent c175097 commit 86bc7dc

File tree

1 file changed

+0
-59
lines changed

1 file changed

+0
-59
lines changed

README.md

Lines changed: 0 additions & 59 deletions
Original file line numberDiff line numberDiff line change
@@ -116,65 +116,6 @@ For a detailed introduction, full list of features and architecture overview ple
116116
3. Run `cd vagrant && vagrant up`
117117
4. Browse to [192.168.56.110](http://192.168.56.110)
118118

119-
### Amazon EC2 Instance
120-
121-
1. In the _EC2_ sidenav select _Instances_ and click _Launch Instance_
122-
2. In _Step 1: Choose an Amazon Machine Image (AMI)_ choose an _Amazon Linux AMI_ or _Amazon Linux 2 AMI_
123-
3. In _Step 3: Configure Instance Details_ unfold _Advanced Details_ and copy the script below into _User Data_
124-
4. In _Step 6: Configure Security Group_ add a _Rule_ that opens port 80 for HTTP
125-
5. Launch your instance
126-
6. Browse to your instance's public DNS
127-
128-
```
129-
#!/bin/bash
130-
yum update -y
131-
yum install -y docker
132-
service docker start
133-
docker pull bkimminich/juice-shop
134-
docker run -d -p 80:3000 bkimminich/juice-shop
135-
```
136-
137-
### Azure Container Instance
138-
139-
1. Open and login (via `az login`) to your
140-
[Azure CLI](https://azure.github.io/projects/clis/) **or** login to the [Azure Portal](https://portal.azure.com),
141-
open the _CloudShell_
142-
and then choose _Bash_ (not PowerShell).
143-
2. Create a resource group by running `az group create --name <group name> --location <location name, e.g. "centralus">`
144-
3. Create a new container by
145-
running `az container create --resource-group <group name> --name <container name> --image bkimminich/juice-shop --dns-name-label <dns name label> --ports 3000 --ip-address public`
146-
4. Your container will be available at `http://<dns name label>.<location name>.azurecontainer.io:3000`
147-
148-
### Google Compute Engine Instance
149-
150-
1. Login to the Google Cloud Console and
151-
[open Cloud Shell](https://console.cloud.google.com/home/dashboard?cloudshell=true).
152-
2. Launch a new GCE instance based on the juice-shop container. Take note of the `EXTERNAL_IP` provided in the output.
153-
154-
```
155-
gcloud compute instances create-with-container owasp-juice-shop-app --container-image bkimminich/juice-shop
156-
```
157-
158-
3. Create a firewall rule that allows inbound traffic to port 3000
159-
160-
```
161-
gcloud compute firewall-rules create juice-rule --allow tcp:3000
162-
```
163-
164-
4. Your container is now running and available at
165-
`http://<EXTERNAL_IP>:3000/`
166-
167-
### Heroku
168-
169-
1. [Sign up to Heroku](https://signup.heroku.com/) and
170-
[log in to your account](https://id.heroku.com/login)
171-
2. Click the button below and follow the instructions
172-
173-
[![Deploy](https://www.herokucdn.com/deploy/button.svg)](https://heroku.com/deploy)
174-
175-
If you have forked the Juice Shop repository on GitHub, the _Deploy to
176-
Heroku_ button will deploy your forked version of the application.
177-
178119
## Demo
179120

180121
Feel free to have a look at the latest version of OWASP Juice Shop:

0 commit comments

Comments
 (0)