Meetup API throttling

[popey]

I've added a bunch (possibly too many?) meetup events to my config.ru. I'm getting throttled by the meetup api, and their advice is to simply add a pause between one call and the next. Perhaps this is something that could be done in almanack? Otherwise I guess I just have to reduce the number of meetups I'm following?

[Aupajo]

@popey What I've done is use multiple API keys and just cycle them:

Almanack.config do |c|
  meetup_keys = %w( MEETUP_KEY_1 MEETUP_KEY_2 MEETUP_KEY_3 ).cycle

  # Will use the first key
  c.add_meetup_group(group_urlname: 'WikiHouse-NZ', meetup_api_key: meetup_keys.next)
  # Will use the second key
  c.add_meetup_group(group_urlname: 'Design-Thinking-Group', meetup_api_key: meetup_keys.next)
  # Will use the third key
  c.add_meetup_group(group_urlname: 'CHC-JS', meetup_api_key: meetup_keys.next)
  # Will use the first key
  c.add_meetup_group(group_urlname: 'ISIG-Christchurch-NZ', meetup_api_key: meetup_keys.next)
  # Etc.
end

Hope that helps!

[Aupajo]

The combination of caching and multiple API keys works well.

Almanack.config do |c|
  # Don't fetch event information more than once every 15 minutes
  c.cache_responses = true
  c.cache_expiry = ENV.fetch('CACHE_DURATION_IN_SECONDS') { 900 }.to_i

  meetup_keys = %w( MEETUP_KEY_1 MEETUP_KEY_2 ).cycle
  meetup_groups = %w(
    WikiHouse-NZ
    CHC-JS
    ISIG-Christchurch-NZ
    Design-Thinking-Group
  )

  meetup_groups.each do |group|
    c.add_meetup_group(group_urlname: group, meetup_api_key: meetup_keys.next)
  end
end