Skip to content

Update README.md with Tips for running container on GCP #280

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 28, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 13 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,9 +70,7 @@ You can obviously mix the order and repeat titles, comments, chats, narrations,

./gradlew build

### Locally in a container

#### Dockerfile
### Locally in a container (Dockerfile)

docker build -t minecraft-storeys-maker .

Expand All @@ -89,6 +87,18 @@ If you want to run on a diffenent host then localhost, you'll need to set the fo
storeys_eventBusURL = http://<EXTERNAL-IP>:8080/


### GCP

A _Series N1: f1-micro (1 vCPU, 614 MB memory)_ is too small and crash loops; but
a _Series N1: g1-small (1 vCPU, 1.7 GB memory)_ seems to suffice for 1 or 2 player; otherwise
a _N1 standard_ or
a _e2-medium (2 vCPU, 4 GB memory)_ or more is recommended.

Remember to set the environment variables as above, add a persistent `/data` volume, and create an appropriate firewall rule.

_TODO Cost: $x VM + $y PD + $7 (?) static IP + $z Ingress+Egress = $TBD._


## FAQ

**Seriously, "storeys" (not _"stories"_) Maker, are you mental?** Yeah.. just to avoid any possible confusion with Minecraft Story Mode! ;-)
Expand Down