pathwalker is a restful webservice written in Golang that allows users to submit reports and images of the state of public footpaths.
This should be easily integrated into the website of the council responsible for the paths.
- /v1/api/add
- /v1/api/upload
- /v1/api/update/{survey-id}
- /v1/api/delete/{survey-id}
- /v1/api/fetch/survey/{survey-id}
- /v1/api/list/{path-id}
The included docker-compose.yml & Dockerfile can be used to build a container image that can either be hosted on a cluster, such as DockerSwarm or Kubernetes; or run on a local Docker instance for testing.
Images are stored in an S3 bucket, see below for configuration. The docker-compose.yml includes a mysql container to run alongside the app container. This can be used as a persistent database if desired, but it is primarily intended for testing locally.
To build & start a local instance, simply run these two commands from the project directory:
docker-compose build
docker-compose up
The webservice listens on :8080 and serves up healthcheck endpoints on :9080
eg http://localhost:9080/live?full=1
If using for Kubernetes liveness/readiness-probes omit the parameter
eg http://localhost:9080/ready
pathwalker reads its config from YAML files stored in the config directory and environment variables prefixed with KOANF_.
There is a config/default.yml which can be used for settings to be applied in all environments.
For environment-specific config, set the KOANF_ENVIRONMENT environment variable at runtime to load a corresponding config file. This file only needs to include those keys which differ from the default values.
eg KOANF_ENVIRONMENT=preprod will load config/preprod.yml
environment: preprod
dbhost: preprod.mysql.address
dbuser: pathwalker
dbport: 3306
dbschema: pathwalker
dbretries: 10
images_bucket: pathwalker-preprod-s3-bucket
s3_region: eu-west-2
There is provision for a .gitignored config/secrets.yml for local passwords that you don't want to commit to github. This should contain the following keys:
dbpasswd:
s3_access_key_id:
s3_secret_access_key:
In production, it is recommended that you set these as environment variables at runtime:
KOANF_DBPASSWD=
KOANF_S3_ACCESS_KEY_ID=
KOANF_S3_SECRET_ACCESS_KEY=
The service is designed to be embedded into an existing website, you will need to build a page to accept new surveys and handle authentication of users, if desired.
To add a survey you will need to POST to two endpoints: /v1/api/upload to upload any attached images and /v1/api/add to send the survey in JSON. The upload endpoint will return a comma-separated-list of image IDs to be included with the survey.
{
"path-id": "PATH-ID",
"survey-date": "YYYY-MM-DD",
"survey-submitted-by": "user@example.com",
"detail": "The meat of the survey, this is being inserted into a mysql TEXT field, which has a limit of 65,535 characters"
"image-ids": "a-series-of-guids,returned-by-image-upload"
}
A (very basic) example image upload form can be found in the examples directory.
A list of all surveys for a given path can be retrieved by sending a GET request to /v1/api/list/{path-id}
A specific survey can be retrieved by sending a GET request to /v1/api/fetch/survey/{survey-id} The survey record contains a slice of all images including the locations they can be downloaded from S3. It is recommended you put these behind a CDN.
Basic administration of the survey data can be achieved by use of the /v1/api/update/{survey-id} and /v1/api/delete/{survey-id} endpoints.
TODO: Deleting a survey will purge all associated images from S3