Skip to content

Commit

Permalink
Add Railway.app instructions
Browse files Browse the repository at this point in the history
  • Loading branch information
bkimminich committed Oct 15, 2023
1 parent b478d02 commit d959ca9
Show file tree
Hide file tree
Showing 2 changed files with 21 additions and 7 deletions.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
27 changes: 20 additions & 7 deletions docs/modules/ROOT/pages/part1/running.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -113,7 +113,9 @@ of the repository)
. Run `cd vagrant && vagrant up`
. Browse to http://192.168.56.110

=== Amazon EC2 Instance
=== Major Cloud Providers

==== Amazon EC2 Instance

You need to have an account at
https://aws.amazon.com[Amazon Web Services] in order to create a
Expand All @@ -138,7 +140,7 @@ docker pull bkimminich/juice-shop
docker run -d -p 80:3000 bkimminich/juice-shop
----

==== AWS EC2 Launch Template
===== AWS EC2 Launch Template

. In the _EC2_ sidenav select _Launch Templates_ and click _Create
launch template_
Expand All @@ -152,7 +154,7 @@ the script above into _User Data_
. Launch one or multiple EC2 instances from your template
. Browse to your instance's public DNS

=== Azure Container Instance
==== Azure Container Instance

. Open and login (via `az login`) to your
https://azure.github.io/projects/clis/[Azure CLI] *or* login to
Expand All @@ -167,7 +169,7 @@ bkimminich/juice-shop --dns-name-label <dns name label> --ports 3000
. Your container will be available at `http://<dns name
label>.<location name>.azurecontainer.io:3000`

==== Azure Web App for Containers
===== Azure Web App for Containers

. Open your https://azure.github.io/projects/clis/[Azure CLI] *or*
login to the https://portal.azure.com[Azure Portal], open the
Expand All @@ -183,7 +185,7 @@ webapp create --resource-group <group name> --plan <plan name> `
`--name <app name> --deployment-container-image-name
bkimminich/juice-shop`

=== Google Compute Engine Instance
==== Google Compute Engine Instance

. Login to the Google Cloud Console and
https://console.cloud.google.com/home/dashboard?cloudshell=true[open Cloud Shell].
Expand All @@ -203,7 +205,9 @@ gcloud compute firewall-rules create juice-rule --allow tcp:3000
. Your container is now running and available at
`http://<EXTERNAL_IP>:3000/`

=== Heroku
=== Other hosting providers

==== Heroku

image::part1/deploy-to-heroku.svg["Deploy to Heroku" button]

Expand All @@ -223,12 +227,21 @@ https://hello.heroku.com/webmail/36622/844098776/9fe33b8eda9eb79bca7ee569888b187

image::part1/heroku-button-of-the-month.png["Heroku Button of the Month" November 2017]

=== Gitpod
==== Gitpod

. Login to https://gitpod.io[gitpod.io] and use https://gitpod.io/#https://github.com/juice-shop/juice-shop/ to start a new workspace. If you want to spin up a forked repository, your URL needs to be adjusted accordingly.
. After the Gitpod workspace is loaded, Gitpod tasks is still running to install `npm install` and launch the website. Despite Gitpod showing your workspace state already as _Running_, you need to wait until the installation process is done, before the website becomes accessable. The _Open Preview Window (Internal Browser)_, will open automatically and refresh itself automatically when the server has started.
. Your Juice Shop instance is now also available at `+https://3000-<GITPOD_WORKSPACE_ID>.<GITPOD_HOSTING_ZONE>.gitpod.io+`.

==== Railway

image::part1/deploy-on-railway.svg["Deploy on Railway" button]

. Sign up for an account on https://railway.app/[Railway] and log in to your account.
. Visit https://railway.app/new/template/6JBGcJ to deploy Juice Shop on your Railway account.

_A step-by-step guide can be found in https://alphasec.io/practice-hacking-skills-with-owasp-juice-shop/[this blog post]._

== Installing a specific release version

The installation instructions above will all give you the latest
Expand Down

0 comments on commit d959ca9

Please sign in to comment.