Automatically synchronize beta testers for your application.
This takes users in campaign monitor (but ultimately, any API Source), and then syncs them to given targets. In Gyde's case, this means:
- A tester signs up to our Beta Test mailing list with Campaign Monitor.
- We invite them to Test Flight builds for the application as an external tester.
- We invite them to a community slack organisation for discussion between us and Beta testers.
- Check in to a health check url (e.g. https://healthchecks.io) if needed.
- Party Time!
We use TOML (Hey, I needed an excuse to play with it) located in a config.toml file. As an example, this may look like:
checkin_url = "optional-check-in-url"
[sources.campaign_monitor]
list_id = "api-oriented-list-id"
api_key = "cm-api-hey-here"
[destinations.test_flight]
app_id = "your-app-id"
email = "itunes-connect-email"
password = "itunes-connect-password"
[destinations.slack]
enabled = true
token = "slack-channel-post-token"Alternatively, you can specify it in the form of environment variables - e.g:
SYNCER__CHECKIN_URL=your-checkin-url
SYNCER__DESTINATIONS__SLACK__ENABLED=true
SYNCER__DESTINATIONS__SLACK__TOKEN=slack-id
SYNCER__DESTINATIONS__TEST_FLIGHT__APP_ID=itunes-app-id
SYNCER__DESTINATIONS__TEST_FLIGHT__EMAIL=testflight-user-email
SYNCER__DESTINATIONS__TEST_FLIGHT__PASSWORD=testflight-user-pw
SYNCER__SOURCES__CAMPAIGN_MONITOR__API_KEY=cm-api-key
SYNCER__SOURCES__CAMPAIGN_MONITOR__LIST_ID=cm-api-list-id
Internally, we deploy to heroku, with zero normal dynos and a scheduled task set to run:
./bin/sync-beta-testersevery 10 minutes using heroku scheduler. Since it processes deltas, we end up paying nothing as the runtime is minimal. Likewise, we use the environment-based configuration formation.
The gem is available as open source under the terms of the MIT License.