Gitiles - git.j3ss.co
git.j3ss.co / tripitcalb0t / refs/tags/v0.1.4
tag5966a1269ff77d8576e2cac2410b5c79631a4770
taggerJess Frazelle <acidburn@microsoft.com>Mon Jul 16 18:40:28 2018 -0400
object636cf614bce7b46ffbf23141559dd458d5625c2c 
v0.1.4
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEE1MTdYA1m9lqO/FEeGPNoXAAiv/MFAltNHtwACgkQGPNoXAAi
v/N+UQ//QmeUZ7PenSVd6GN997ksdKle+ubfEYoeV67xWYK+pJiqvexC7wwr1XfX
lAupP9+VcPj20ONX6o6dP4+/KPPBVXjcDdABTGg3aOmDZgC3gmChtODGuyFl/9I2
bInW3mnN4pUyqke11tfrbOopkzy1P1muT7zf5aJ3AvZ0C1YYA3fRnt/2CyuabpFa
wSafa2BlGN1Hmk9w8x3zEUvQvQ5NoLKm9TgqqAdQvtXDIqbRC30fRbMsrP7d2BXc
zEXXqwg6cyBrrxrgiYt4/KtigVm0mmWrefCD2zW7ihIU07nSjT6ONC4DiBEdsDUX
rpHgCCjXQXMz9W+2JXQi6TsGK/huFqQMn0kmzNOka/HleUMrCn25fPDkPplauXcW
7G6Hx2eBuSgXnbyE9/3VNBnBQ3wxUB/MCFwCVKv250c5agQCgd5UdYqnPLXedKBF
9DpoMesTKaFOPkzYuI4AwU7PeT5/u9X9OsSoRqufFsi/ZnovldnXJ7kC7oaF++Hz
GDVHFuFyw4pMMlZHlt+XPeqBh06FbFIdMUlbNNKWNtfHSnLuD5jGn14QecycZh/h
b9duTPmwA9ibRs0qEkek8bw8JVg9wr7H+56NZdgt1OjQDLdtdUql95/NTO/XZGRD
Qp5Yfq4aPCjZfBG5z+31y5ZTIBYLNwYTI23mvtx3dEXPCIg+U/s=
=J+TK
-----END PGP SIGNATURE-----
commit636cf614bce7b46ffbf23141559dd458d5625c2c[log] [tgz]
authorJess Frazelle <acidburn@microsoft.com>Mon Jul 16 18:40:26 2018 -0400
committerJess Frazelle <acidburn@microsoft.com>Mon Jul 16 18:40:26 2018 -0400
tree5d1b44945a05586da3e0cfb7446b9564e4b2f489
parent9b9c5f34de03b99ab48b5871d8e1ff5465130553 [diff]
Bump version to v0.1.4

Signed-off-by: Jess Frazelle <acidburn@microsoft.com>
1 file changed
tree: 5d1b44945a05586da3e0cfb7446b9564e4b2f489
  1. .gitignore
  2. .goosarch
  3. .travis.yml
  4. .traviskey
  5. Dockerfile
  6. Gopkg.lock
  7. Gopkg.toml
  8. LICENSE
  9. Makefile
  10. README.md
  11. VERSION.txt
  12. main.go
  13. main_unix.go
  14. main_windows.go
  15. tripit/
  16. vendor/
  17. version/
README.md

tripitcalb0t

Travis CI GoDoc Github All Releases

Bot to automatically create Google Calendar events from TripIt flight data.

I have OCD about the layout of my calendar events so that is why I made my own bot.

Installation

Binaries

For installation instructions from binaries please visit the Releases Page.

Via Go

$ go get github.com/jessfraz/tripitcalb0t

Running with Docker

$ docker run --restart always -d \
    -v /etc/localtime:/etc/localtime:ro \
    -v /path/to/.tripitcalb0t/google.json:/.tripitcalb0t/google.json:ro \
    --name tripitcalb0t \
    -e "TRIPIT_USERNAME=your_username" \
    -e "TRIPIT_TOKEN=59f6asdfasdfasdf0" \
    -e "GOOGLE_CALENDAR_ID=your_google_calendar_id" \
    r.j3ss.co/tripitcalb0t --interval 1m

Usage

$ tripitcalb0t -h
tripitcalb0t -  Bot to automatically create Google Calendar events from TripIt flight data.

Usage: tripitcalb0t <command>

Flags:

  --calendar         Calendar name to add events to (or env var GOOGLE_CALENDAR_ID)
  -d                 enable debug logging (default: false)
  --google-keyfile   Path to Google Calendar keyfile (default: ~/.tripitcalb0t/google.json)
  --interval         update interval (ex. 5ms, 10s, 1m, 3h) (default: 1m0s)
  --once             run once and exit, do not run as a daemon (default: false)
  --tripit-token     TripIt Token for authentication (or env var TRIPIT_TOKEN)
  --tripit-username  TripIt Username for authentication (or env var TRIPIT_USERNAME)

Commands:

  version  Show the version information.

Setup

Google Calendar

  1. Enable the API: To get started using Calendar API v3, you need to first create a project in the Google API Console, enable the API, and create credentials.

    Follow the instructions for step enabling the API here.

  2. Add the new service account to the Google Calendar account with Read & Write permission.

    The newly created service account will have an email address that looks similar to: quickstart@PROJECT-ID.iam.gserviceaccount.com.

    Use this email address to add a user to the Google Calendar view you want to access via the API.

TripIt

To use this, you must enable "Web Authentication" on your account. You can follow the steps to do that here.