usage via Docker: API doesn't report any GTFS data

[derhuerst]

Hey,

sorry that I don't have a more specific bug report, probably this is just a question on how to use TransitClock properly.

I took your transitclockDocker repo and modified it slightly in order to:

• adapt the setup to the city of Herrenberg, where I'm part of a project that implements a fully integrated intermodal public transportation app,
• fix & tweak minor things, e.g. make shell scripts fail properly.

I have adapted GTFS_URL to contain a GTFS dataset, and GTFSRTVEHICLEPOSITIONS to point to a server that wasn't running. I have run all steps of go.sh except import_avl.sh & process_avl.sh because I assumed they aren't necessary for my use case.

Expected functionality

When using the TransitClock API, I would expect it to return data from the GTFS dataset that I have tried to import.

Describe the bug

The GTFS import step didn't log anything import- or GTFS-related, just its configuration parameters and technical stuff.

I tried various API calls (e.g. /key/{key}/agency/{agency}/command/serviceIds), but they don't return any data. Some of the calls fail with 400 Bad Request.

To Reproduce

Except the GTFS-RT URL (but the respective server wasn't running either when I started it), you should be able to clone the derhuerst/thetransitclock-docker#4f04c54 and run ./go.sh.

Version:

The Dockerfile pulls Core.jar, api.war & web.war from the latest TheTransitClock/transitime GitHub release.

Configuration:

Inside the repo.

---

Thanks for taking the time to look at this!

[scrudden]

Only coming to this now....

[derhuerst]

In case you don't have the time/energy to answer: Sorry to bother you with this.
In case you've forgotten about this Issue: ping. 🙂

Let me know if I can assist with finding the problem here!