You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The second, and more useful, way is to use the `wercker dev` command to launch the binary within a Docker container, using the base image defined in the `box/id` property at the top of the `wercker.yml`, like so:
27
-
```
28
-
wercker dev --expose-ports
29
-
```
30
-
The `dev` target inside `wercker.yml` uses the `internal/watch` step to dynamically reload the runtime container when sourcefile changes are detected, which allows you to quickly test changes without having to kill/rebuild/relaunch the container. For instance, add another city to the array on `app.js:3' like so:
31
-
32
-
```
33
-
var cities = {"cities":["Amsterdam","Berlin","New York","San Francisco","Tokyo","London"]}
34
-
```
35
-
36
-
and then refresh your browser pointing to `http://localhost:8080` to see:
0 commit comments