Skip to content

Commit e95b15a

Browse files
committed
Updating docs
1 parent 3cc140f commit e95b15a

File tree

1 file changed

+38
-4
lines changed

1 file changed

+38
-4
lines changed

README.md

Lines changed: 38 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,9 @@ TODO:
1212

1313
# Summary
1414

15-
By downloading and running this you are agreeing to the [StarCraft II AI and Machine Learning License](https://github.com/Blizzard/s2client-proto/blob/dca8b6831a84747c2cd6e0c33d6416e14838d886/DATA_LICENSE)
15+
By downloading and running this you are agreeing to:
16+
17+
[StarCraft II AI and Machine Learning License](https://github.com/Blizzard/s2client-proto/blob/dca8b6831a84747c2cd6e0c33d6416e14838d886/DATA_LICENSE)
1618

1719

1820
# Building Containers
@@ -23,32 +25,53 @@ By downloading and running this you are agreeing to the [StarCraft II AI and Mac
2325
cd game && ./all.sh
2426
~~~
2527

28+
This creates a new container named s2client-api.
29+
30+
The entrypoint will be the StarCraft II executable listening for API calls on port 12000.
31+
32+
You can run the game now as a container:
33+
34+
~~~
35+
docker run -P -d s2client-game
36+
~~~
37+
38+
TODO: There appears to be an issue connecting on the exposed port
2639

2740
3. Building the API build container
2841

2942
~~~
3043
cd build && ./all.sh
3144
~~~
3245

46+
This builds the API and puts binary artifacts into the build-mount volume.
47+
3348
4. Test the containers
3449

3550
~~~
36-
TODO
51+
cd game && ./run-tests.sh
3752
~~~
3853

54+
TODO: This currently crashes
55+
56+
3957
2. Installing replay packs and the Battle.net cache to run hem
4058

4159
~~~
42-
TODO
4360
~~~
4461

62+
TODO: Consider using volumes for this case as well, lots of data to move around.
63+
4564
### Running the API build
4665

66+
67+
You can run the build yourself inside the s2client-api container:
68+
4769
~~~
4870
docker run -it s2client-api
4971
./api-build.sh
5072
~~~
5173

74+
5275
### Running the Game
5376

5477
~~~
@@ -59,5 +82,16 @@ If you want to use the replay container automation you should export
5982
the container ID in an environment variable.
6083

6184
~~~
62-
export GAME_CONTAINER=docker run -d s2client-game
85+
export GAME_CONTAINER=`docker run -P -d s2client-game`
6386
~~~
87+
88+
### Developing using the API
89+
90+
~~~
91+
cd dev && ./all.sh
92+
docker run -it s2client-dev
93+
~~~
94+
95+
The developer image s2client-dev is derived from s2client-game. You will need
96+
to first build the s2client-game image. Running the developer image you can
97+
clone the git repo, update your git config and test against the packaged client.

0 commit comments

Comments
 (0)