c-l/docker-adsb-ultrafeeder
1
0
Fork 0
mirror of https://github.com/sdr-enthusiasts/docker-adsb-ultrafeeder.git synced 2024-10-16 05:50:44 +00:00
Code Releases Activity

Update README.md

Browse source 
Updated documentation and added example regarding variable handling by mlat-client when utilizing gpsd functions.
This commit is contained in:
MNTech68 2024-08-28 16:00:32 -05:00 committed by GitHub
parent 0d5e6a5c0c
commit aecb88ee16
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 12 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
README.md
View file

@ -832,7 +832,7 @@ If you have any issues, readsb will use verbose output if you add the `GPSD_DEBU
### Optional parameters regulating the restart of `mlat-client` when the location changes
The following parameters are all optional and are subject to change. You don't need to set them unless you want to change the default behavior:
The following parameters are all optional and are subject to change. These variables should be added to the environment section of your docker-compose.yml. They will not work if entered into the .env file. You don't need to set them unless you want to change the default behavior.
| Environment Variable | Purpose | Default |
| -------------------- | ------- | ------- |
@ -840,6 +840,17 @@ The following parameters are all optional and are subject to change. You don't n
| `GPSD_MLAT_WAIT` | The wait period (in seconds) your station must be stationary before mlat is started (minimum 90 seconds) | `90` (seconds) |
| `GPSD_CHECK_INTERVAL` | How often the container checks for updated location information. (minimum 5 seconds) | `30` (seconds) |
See example below:
```yaml
environment:
...
- GPSD_MIN_DISTANCE=20
- GPSD_MLAT_WAIT=90
- GPSD_CHECK_INTERVAL=30
...
```
## Web Pages
If you have configured the container as described above, you should be able to browse to the following web pages: