maxmustermann/PowerShell
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Merge pull request 80 from dev/use-latest-tag into develop

Browse source
This commit is contained in:
Andy Schwartzmeyer 2015-07-20 23:10:37 +00:00
parent acd3a5bd66 a36cb6fd05
commit c7e5834a17
2 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -64,7 +64,7 @@ Clone our [monad-linux][] source from Visual Studio Online. We use the `develop`
git clone -b develop --recursive https://msostc.visualstudio.com/DefaultCollection/PS/_git/monad-linux
```
When checking out a commit (or pulling in commits), you need to update all the submodules too.
When checking out a commit (or pulling in commits), you **must** update all the submodules too. Not doing so is the cause of many headaches.
```sh
git submodule update --init --recursive
@ -103,6 +103,8 @@ We have an [automated build repository][] on the Docker Hub that provisions an i
Using this image amounts to running an ephemeral container with the local source code mounted as a shared volume, which is precisely what `build.sh` does (as well as pass on command-line arguments). If the `andschwa/magrathea` image is not already present, it is automatically pulled from the Hub.
This is what `build.sh` looks like (there is no need to run this command manually):
```sh
docker run --rm --interactive --tty --volume /absolute/path/to/monad-linux/:/opt/monad --workdir /opt/monad/scripts andschwa/magrathea make run
```

2
scripts/build.sh
View file

@ -1,4 +1,4 @@
#!/usr/bin/env sh
# Docker requires the volume path to be absolute... so we resolve it ourselves.
docker run --rm --interactive --tty --volume $(dirname $(pwd))/:/opt/monad --workdir /opt/monad/scripts andschwa/magrathea $@
docker run --rm --interactive --tty --volume $(dirname $(pwd))/:/opt/monad --workdir /opt/monad/scripts andschwa/magrathea:latest $@