Heroku addons development - Nov 2011

Developing Heroku add-ons for Heroku hosted services @leonardo_borges

self slide ➡ Consultant at ThoughtWorks Australia ➡ Programming languages enthusiast ➡ Developed the Queensland heroku powered app for the Floods of 2010/2011 ➡ Used by thousands ➡ Generated over $38 million in donationswww.leonardoborges.com @leonardo_borges

Why?You’re good at something other people are not

Why?So you expose your service to a whole new market

Why?Grow your user baseto tens of thousands

Why? Heroku promotes your service free buzz :)and makes it dead easy for users to get started

How? Meet letmein, the polite authentication service authenticate your letmeincustomer’s ok/get out! app heroku

KensaHeroku add-on development, TDD style $ gem install kensa $ cd /letmein $ kensa init addon-manifest.json { "id": "letmein", "api": { "conﬁg_vars": [ "LETMEIN_URL" ], "password": "pXrE4efbslOkCHtu", "sso_salt": "qi198QaiuPsE6DWq", "production": "https://letmein.herokuapp.com/", "test": "http://localhost:5000/" }

Kensa Oops.$ kensa test provisionTesting POST /heroku/resources Check response [FAIL] ! expected 200, got 404done.

Add-on provisioning Allocate resources for the apppost /heroku/resources do api_key = Digest::SHA1.hexdigest(Time.now.to_s + rand(12341234).to_s) user = User.create(api_key: api_key, created_at: Time.now) result = { :id => user.api_key, :config => { "LETMEIN_URL" => url("/#{api_key}") } } result.to_jsonend

Kensa What’s next? $ kensa test provision Testing POST /heroku/resources Check response [PASS] Check valid JSON [PASS] Check authentication [FAIL] ! expected 401, got 200 done.Point is, Kensa will tell you what to do!

The consumer app and the minimalist letmein plugindef authenticate! redirect "#{ENV["LETMEIN_URL"]}/authenticate?return_to=#{url(/callback)}"endbefore /protected/* do authenticate! unless session[:user]end

Local end to end test and little demo!$ kensa run ruby ../letmein-consumer/app.rbTesting POST /heroku/resources Check response [PASS] Check valid JSON [PASS] Check authentication [PASS]...Testing DELETE /heroku/resources/5f3feb3dfb2bc20f29d14c49f4567599dbb0345f Check response [PASS] Check authentication [PASS]done.

All set? Become an add-on providerhttps://addons.heroku.com/provider/signup

Then what? This is how your users will install the add-on$ heroku addons:add letmein-----> Adding letmein to letmein-consumer... done, v3 (free)$ heroku configLETMEIN_URL => https://letmein.herokuapp.com/e223a873c2e794e93fafaea9016327f1e668be3f... ...and it’s time for another little demo!

Resources➡ https://github.com/leonardoborges/letmein➡ https://github.com/leonardoborges/letmein-consumer➡ https://addons.heroku.com/provider➡ http://www.heroku.com

Thank you!Questions? @leonardo_borges

Heroku addons development - Nov 2011

by Leonardo Borges on Jan 28, 2012

Accessibility

Categories

Tags

Upload Details

Usage Rights

Statistics

Heroku addons development - Nov 2011 — Presentation Transcript