Getting consumer URL during provisioning

[raasdnil]

Hi all,

We are intend to enable http://StillAlive.com as a heroku Add On.

Part of the provisioning process is creating a working recipe for the
new account. As well as obviously having the user provide the phone
number, twitter ID or email they want downtime notifications sent to.

The Exceptional Add-On does something similar, at least, per the docs
it says: "If you already have an Exceptional account, the Exceptional
app will be linked to it automatically. Otherwise a new account will
be created for you - you’ll receive an invitation in your email to
create a password."

How does the exceptional add on find the existing account from the
POST params that are coming from Heroku?

I'll need to send the user who creates an account an email like this
to confirm the alert email and direct them on loging into the system
(through Heroku's interface) to create their first site checking
recipe, as well as letting us know what phone number to call / sms for
a downtime alert etc.

Is the heroku_id passed in during the provision request the email
address I am looking for?

Anyway, pointers would be fantastic.

Mikel

[Peter van Hardenberg]

Heroku doesn't support passing parameters through a provisioning call at the moment, but that's something we've certainly discussed adding. What about using the SSO page, or an environment variable on the app? How would the user reconfigure the addon once it is provisioned if they pass the phone number at provision-time?

Feels to me like the SSO page is a good fit. I believe you can include a provisioning-time message to the user that could say something like "Your app is now being monitored and will send notifications to <owner_email>. To configure additional notification channels, use the dashboard at <sso url>."

I'd definitely be happy to alpha-test the addon for some of my apps...

-p

--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt." -- Kurt Vonnegut

[Mikel Lindsaar]

Thanks Peter for your reply

On 02/04/2011, at 5:41 AM, Peter van Hardenberg wrote:
> Heroku doesn't support passing parameters through a provisioning call at the moment, but that's something we've certainly discussed adding. What about using the SSO page, or an environment variable on the app? How would the user reconfigure the addon once it is provisioned if they pass the phone number at provision-time?
> Feels to me like the SSO page is a good fit.

Yes, I have implemented the SSO interface. The whole thing is ready to alpha test once I get my head around this problem.

> I believe you can include a provisioning-time message to the user that could say something like "Your app is now being monitored and will send notifications to <owner_email>. To configure additional notification channels, use the dashboard at <sso url>."

Exactly what I want. Where or how do I get that "owner_email" from?

If I get an owner_email somehow, then I can group multiple beginner sites together and provide the user with a single interface to monitor all their sites.

> I'd definitely be happy to alpha-test the addon for some of my apps...

Great, I'll put you down for the Alpha :)

Mikel

[Pat Allan]

Hi Mikel

You can get the owner email - I'm pretty certain this only works *after* you've responded to the provisioning request from Heroku:
http://groups.google.com/group/heroku-add-on-providers/browse_thread/thread/87d117d69af42233

So you'll probably need some two-step process of setting it up and then attaching it to an existing user if appropriate. I wouldn't use Exceptional as an example - their approach also includes installing a plug-in, and Heroku's not supporting that level of interaction for new add-ons.

Cheers

--
Pat

[Mikel Lindsaar]

On 02/04/2011, at 10:59 AM, Pat Allan wrote:
> You can get the owner email - I'm pretty certain this only works *after* you've responded to the provisioning request from Heroku:
> http://groups.google.com/group/heroku-add-on-providers/browse_thread/thread/87d117d69af42233

Perfect, thanks. I saw that in the docs, but could not see if it was the client data it was returning.

> So you'll probably need some two-step process of setting it up and then attaching it to an existing user if appropriate. I wouldn't use Exceptional as an example - their approach also includes installing a plug-in, and Heroku's not supporting that level of interaction for new add-ons.

Yup, sorted.

Thanks :)

Mikel