Ooh, thank you for making this! I may just not understand how CalDAV stuff works but is there a server we need to point to? Or download and run locally? The documentation only seems to mention constructing the URL.
Yes, you need to configure your calendar to point to a server, in the same way that you would add a Google account on your calendar app.
Right now I’m hosting the server for myself, but anyone else can use it! So, no need to download anything.
In the future, I’ll release the source code so that anyone can host their own server.
(right now, the downside of using my server is that I could see the data and the private token if I wanted to; which means I could access private Beeminder goals and datapoints)
Using the software is a two-steps process, and then, it’ll work forever:
Awesome. I’ve just added a calendar pointing to your server with my own Beeminder auth token. (I’m doing this via calendar.google.com)
How long should I expect to wait for beemergencies to appear in my calendar? Also, a killer feature for me is that these entries remove themselves when I dispatch the beemergencies. Otherwise, I find there’s too much wolf-crying and I end up tuning them out (I’ve tried automatically adding beemergencies to calendar before). Does your implementation do that?
They should appear about 2 minutes later – if they don’t, it means that I did something wrong!
They will, normally it should refresh every 15 minutes
You can always force-synchronize (this depends on the client) and it should also remove obsolete entries.
Let me know if anything doesn’t work, it makes me happy knowing it’s being used by someone else!
I haven’t tried this in a few years, but the last time I did, Google only fetched updates from the calendar once a day, and it wasn’t even always a predictable time.
)
.