fanyx
/
docker-tmserver
1
0
Fork 0
Code Issues Pull Requests Projects Releases 2 Wiki Activity

Update README.md

This commit is contained in:
fanyx 2020-01-05 15:25:03 +01:00 committed by GitHub
parent 2dd7f3bac4
commit a119825572
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 20 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
README.md
View File

@ -65,7 +65,26 @@ Other configuration options are listed below:
- $LAPS_TIMELIMIT | time limit in milliseconds for laps mode -> Default : 0
```
### Running a custom playlists
### Running custom tracks
While the Nadeo tracks are available in this repository and accessible under `GameData/Tracks/Challenges/Nadeo/` you can also run custom tracks following the instructions below.
You can run custom tracks by mounting a volume from where your tracks are stored to `/opt/tmserver/GameData/Tracks/Custom`.
In this example i am storing my tracks in `./tracks` relative to the docker-compose file.
```
[...]
tmserver:
image: fanyx/tmserver:latest
[...]
volumes:
- ./tracks:/opt/tmserver/GameData/Tracks/Custom
[...]
```
### Running a custom playlist
You can add tracks to a playlist in a simple way. Just provide a `playlist.txt` that contains every track in a certain format. Create a folder next to your `docker-compose.yml`, mount it as a volume to `/opt/tmserver/playlist` and put the `playlist.txt` in there.
@ -87,18 +106,3 @@ Challenges/Nadeo/C01-Race.Challenge.Gbx
Custom/mini01.Challenge.Gbx
Custom/SpeedxZxZ.Challenge.Gbx
```
### Running custom tracks
You can run custom tracks by mounting a volume from where your tracks are stored to `/opt/tmserver/GameData/Tracks/Custom`.
In this example i am storing my tracks in `./tracks` relative to the docker-compose file.
```
[...]
tmserver:
image: fanyx/tmserver:latest
[...]
volumes:
- ./tracks:/opt/tmserver/GameData/Tracks/Custom
[...]
```