Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
whomwah authored Mar 31, 2020
1 parent e866d84 commit ac82c07
Showing 1 changed file with 8 additions and 11 deletions.
19 changes: 8 additions & 11 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,29 +64,26 @@ $ make coverage-api # as above but with coverage

### Running the app

From there, you can run everything in `Docker`. From the root of the repo, you just need to run:
There are two ways to run the app in `Docker`. You either run it using a Docker version of Mopidy. You don't get any sound but it's by far the easiest way. You just need to run:

```
$ make build
$ make serve
$ make build-all
$ make serve-all
```

Or to run with local Mopidy:
or you can run it using Mopidy running somewhere else. In this case you will need to change the `WS_MOPIDY_URL` to point to your own running version. You can then start things with:

```
$ make build-all
$ make serve-all
$ make build
$ make serve
```

This will give you a working client and API plus the persistence layer. The client is available at http://localhost:3001 running in dev mode, meaning any changes will cause the server to restart.
Either way. this will give you a working client and API plus the persistence layer. The client is available at http://localhost:3001 running in dev mode, meaning any changes will cause the server to restart.


### Mopidy

If you want to run your own copy of Mopidy, you can buy yourself a Raspberry Pi and follow [these instructions](docs/mopidy_install.md).

Alternatively, it is possible to run Mopidy from [within Docker](docs/mopidy_docker.md), although this currently does not support audio playback.

If you so want to run your own copy of Mopidy, you can buy yourself a Raspberry Pi and follow [these instructions](docs/mopidy_install.md).

### Client

Expand Down

0 comments on commit ac82c07

Please sign in to comment.