https://github.com/passy/disruption-tracker
Tracking Tube disruptions and write them to a RethinkDB
https://github.com/passy/disruption-tracker
Last synced: over 1 year ago
JSON representation
Tracking Tube disruptions and write them to a RethinkDB
- Host: GitHub
- URL: https://github.com/passy/disruption-tracker
- Owner: passy
- License: bsd-3-clause
- Created: 2016-07-10T14:15:56.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2017-02-18T13:50:28.000Z (over 9 years ago)
- Last Synced: 2025-02-04T16:34:55.167Z (over 1 year ago)
- Language: Haskell
- Homepage:
- Size: 102 KB
- Stars: 2
- Watchers: 4
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# disruption-tracker
[](https://travis-ci.org/passy/disruption-tracker)
> Collecting Tube disruption data. Maybe more later.
## Status
If anything works then only by accident. This is, as with most of my project,
just an exploration. But having code in the open so you can point people at it
and ask questions is often quite useful.
## Setup
Run RethinkDB. I recommend Docker for that kinda thing. Remember to write down
the ports.
```bash
$ docker run -P --name rethink1 rethinkdb:2.3
$ docker ps
```
Build this thing.
```bash
$ stack build
```
Initialize some tables, keys and indices.
```bash
$ stack exec disruption-tracker -- --hostname 192.168.99.100 --port 32769 setup
```
If this fails, please manually drop the db for now so we can recreate it:
```javascript
r.dbDrop('test');
r.dbCreate('test');
```
Set up the RethinkDB before?
```
$ docker start rethink1
```
## Deployment
See https://github.com/passy/disruption-bot-deployment.
## Collecting
Now you can start manually collecting. Automatic polling is coming soon.
```
$ stack exec disruption-tracker -- --hostname 192.168.99.100 --port 32769 collect
```