-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Look at options for automating the events page. #46
Comments
Haha Agreed!! |
So, an idea for dog-fooding this with OpenWhisk:
This would likely be easier if the events were individual posts rather than a single page, but that's also a somewhat significant structural change. The assumption here, though, is that all of these events will be loaded into a service that has an API that will send events that we can consume with OpenWhisk. Which is a big assumption. So... someone who knows how events are currently being done — @nauerz-ibm? @krook? — maybe chime in about how this has been done previously. Or, since this is moving to an open source model, maybe we can just set up something new. It doesn't look like Lanyrd.com has an API, but maybe some other service exists that aggregates event data, and we could watch that for |
I like this, but agree, it has to be in some sort of predictable format like an API. Let's start small with the Meetup API and search for keywords. I played around with something similar before, but never deployed it. It basically was invoked via cron and saved results to a file, which were then included as a WordPress snippet. It looked something like this. We can use #!/bin/bash
# Requires a Meetup.com API key: xxxxxx
# Docs: http://www.meetup.com/meetup_api/docs/2/open_events/
wget https://api.meetup.com/2/open_events?key=xxxxxx&sign=true&photo-host=public&topic=openwhisk,serverless&page=40 |
Related to #175. FYI @csantanapr @mrutkows since we spoke about this approach. |
ah it looks like @jlengstorf was thinking on META from #46 (comment) |
Can we update the page via API?
Even better, could we use OpenWhisk to do this?
Something to think about post-launch.
The text was updated successfully, but these errors were encountered: