Skip to content

Commit

Permalink
docker readme.md: Remove VISSR vss_vissv2.binary and vsspathlist notes
Browse files Browse the repository at this point in the history
Update the docker readme.md to reflect changes brought about by CDSP now
using VISSR v3:

1. VISSR now provides a default binary list of VSS nodes so remove the
   note about having to generate vss_vissv2.binary
2. VISSR no longer serves a list of the VSS nodes supported at the URL
   http://<server ip>:8081/vsspathlist. Remove the associated note.

Signed-off-by: Stephen Lawrence <[email protected]>
  • Loading branch information
slawr committed Jan 20, 2025
1 parent 36a3ce7 commit 0748ae6
Showing 1 changed file with 0 additions and 9 deletions.
9 changes: 0 additions & 9 deletions docker/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,13 +50,6 @@ There is a current issue with the upstream VISSR VISS Server Dockerfile in which

If your project requires Access Grant support please discuss enabling it with the VISSR community.

### Generate `vss_vissv2.binary`
The VISSR server component requires a file called `vss_vissv2.binary` to understand the VSS tree it must work with. Unfortunately, VISSR provides no default file and you must therefore generate it yourself.

Instructions for doing that can be found in the VISSR documentation site [here](https://covesa.github.io/vissr/server/#vss-tree-configuration)

Tip: The playground maintainers have found that the method involving running `make binary` in a git clone of the VSS source tree to generate the file is straight forward. Note: check the VSS readme for the python requirements for the tooling.

### Tip: Corporate CA security (download error "tls: failed to verify certificate:")
If you are working behind a corporate security system that places a _man-in-the-middle_ between your host and the internet you may see security errors when artifacts are downloaded as part of the build process.

Expand Down Expand Up @@ -172,5 +165,3 @@ The following example uses the javascript HTML client from `vissr/client/client-
Server: readyState=3, status=200
Server: {"data":{"dp":{"ts":"2024-01-10T14:56:48Z","value":"Data-not-found"},"path":"Vehicle.Speed"},"ts":"2024-01-10T14:56:48Z"}
```

You can query what VSS nodes the server understands by asking for the VSS path list using the URL `http://localhost:8081/vsspathlist`. Entering that URL in your web browser will typically give you a graphical rendering of the JSON data returned.

0 comments on commit 0748ae6

Please sign in to comment.