Skip to content

authentication removing container for wunder fleet gbfs access

License

Notifications You must be signed in to change notification settings

stadtulm/wunderfleet-gbfs-opener

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Wunder Fleet GBFS Opener

In the City of Ulm we have scooter sharing providers based on the Wunder Fleet provider software. They provide, combined with their MDS interface, GBFS data - but sadly only with authentication.

The MDS standard requires that GBFS data has to be publicly available. Until Wunder updates their interface to be fully compatible with MDS, we're using this tool to provide the GBFS data ourselves.

This docker container is basically nothing more than a simple nginx proxy, that authenticates against the GBFS URL. It also rewrites the URLs contained inside, so it is usable by tools which enter by accessing gbfs.json and use the URLs to find the free_bike_status and system_information data.

Usage

The container needs two environment variables to run: WUNDER_BACKEND_HOST and WUNDER_API_TOKEN.

Ask your sharing provider to get these two. Note that the WUNDER_API_TOKEN is the City Access Token for their Mobility Data API. It may be that your sharing provider has to call their wunder support representative to create these for you.

If you mount the container with something like the kubernetes ingress, the container also provides you with support for the X-Forwarded-Proto, X-Forwarded-Host, X-Forwarded-Port and X-Forwarded-Prefix headers, so the URLs that are rewritten in the json contain the right parts needed to work.

If you want to use your own dns server for resolving the WUNDER_BACKEND_HOST domain name, set the DNS_RESOLVER environment variable.

About

authentication removing container for wunder fleet gbfs access

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published