Gitiles
Code Review Sign In
realtimeroboticsgroup.org / RealtimeRoboticsGroup / test / 11e61afdc9fdbea03f79e99f889fb2adb23f8b84 / . / scouting / webserver
tree: 15afccf71b1424f84638d9d7196b6feedfb24824 [path history] [tgz]
  1. driver_ranking/
  2. match_list/
  3. rankings/
  4. requests/
  5. server/
  6. static/
  7. BUILD
  8. main.go
  9. README.md
scouting/webserver/README.md

The scouting web server

This directory contains the code that combines to make the scouting web server.

main.go

This is the main application that brings all the pieces together. Run it like so:

bazel run //scouting/webserver:webserver

server/

This directory contains the code that manages the web server itself. It's responsible for starting and stopping the server. It also exposes a Handle() method that lets other libraries enhance the server's functionality.

static/

This directory contains the code that serves static files at the root of the server. Make sure that none of the files you're serving clash with any of the paths used by the other libraries that enhance the server's functionality. E.g. if POST requests for match data are serviced at /requests/xyz, then don't serve any files in a requests directory.

requests/

This directory contains the code that services requests from the web page. The web page sends serialized flatbuffers (see the scouting/webserver/requests/messages directory) and receives serialized flatbuffers in response.

requests/debug/cli

This directory contains a debug application that lets you interact with the webserver. It allows you to make call calls that the web page would normally make.