geemus (u/geemus) - Readit News

geemus commented on Show HN: Anchor Relay – A faster, easier way to get Let's Encrypt certificates anchor.dev/relay... · Posted by u/geemus

xmprt · 5 days ago

I'm sure some people would find this useful but forgive me if I'm not ready to hand away my security to some unknown third party company. I don't know the first thing about CAs but Let's Encrypt really isn't that difficult to understand.

geemus · 5 days ago

We take security very seriously, which is why we designed Relay to work so that we never have to see your encryption keys. If Let's Encrypt is working well enough for you, that's great, but we've also heard about rough edges that people struggle with so we are trying to help them out.

geemus commented on Show HN: Dynosaur, An autoscaler for Heroku using Google Analytics Live engineering.harrys.com/20... · Posted by u/dschwartz88

willcodeforfoo · 12 years ago

It's kind of surprising that Heroku hasn't cracked this nut on their own. Perhaps it isn't in their best interest to scale down? Scalability certainly is often touted as one of the benefits of "the cloud".

geemus · 12 years ago

Unfortunately auto-scaling is incredibly application specific. It would be a great feature, but it seems likely to be quite difficult to make a particular solution that is useful to more than a small subset of users. You can get some sense of this from the other comments above (ie how analytics wouldn't be a good scaling metric for them).

geemus commented on Heroku Platform API, Now Available in Public Beta blog.heroku.com/archives/... · Posted by u/Lightning

nthj · 12 years ago

> The legacy API was mostly used just internally

I find that amazing. I think every app I've ever worked on or built with Heroku has tied into the API in one way or another. It's one of your best features.

geemus · 12 years ago

A number of people definitely found their way through the toolbelt code to use the API previously, which is amazing. We hope by giving a stronger focus and some proper documentation that we can make it much more accessible to more and more people.

geemus commented on Heroku Platform API, Now Available in Public Beta blog.heroku.com/archives/... · Posted by u/Lightning

nchuhoai · 12 years ago

I might be misinformed, but wasn't the purpose of stuffing version/format into the URL so that it is easier to develop with? I.e. setting only one URL to make a request is easier than having to set an URL + Accept Version Header + Accept Format Header.

geemus · 12 years ago

Both the format and version are in the same header if that helps. So there are a couple values in there you might have to change, similar to the couple values you would have to change in the url to modify version/format. So in that regard I think the difficulty or complexity of one or the other is pretty similar. Hope that helps explain a bit, but let me know if I missed the point of your question.

geemus commented on Heroku Platform API, Now Available in Public Beta blog.heroku.com/archives/... · Posted by u/Lightning

Timothee · 12 years ago

It seems to me that the problem is that the backend is treating the XHR like if you were hitting the main site. So sometimes (but not for all endpoints I think), if I were logged out, the XHR would be redirected to the login page.

To me, the API endpoints should behave the same way in a browser as with curl without ever redirecting to the login page.

But, once again, it might have been fixed in the meantime… I haven't tried recently.

geemus · 12 years ago

Sure. I haven't tried either. Its on my list of stuff to dig into and sort out, so hopefully we have a better answer soon.

geemus commented on Heroku Platform API, Now Available in Public Beta blog.heroku.com/archives/... · Posted by u/Lightning

themgt · 12 years ago

From a glance this looks like a formalization of what already existed at: https://api-docs.heroku.com/ and which obviously the command-line client uses (although the docs and command line/production API have drifted apart)

At Pogoapp we basically reverse-engineered our API from Heroku's command line client, but it's excellent to have Heroku make the API public and formal, because it should make that process much easier and set up Heroku's API as a good target for other PaaS hosts to standardize on (in the same way Ceph & RiakCS have S3-compatible REST APIs)

geemus · 12 years ago

We definitely used what you mentioned as a starting point. There are some changes, hopefully for the better, but it should in time provide all the same functionality in a more public and formal way. We definitely love that people were excited and motivated enough to reverse-engineer things as you did, so we hope this makes it easier on you and more accessible to others.

geemus commented on Heroku Platform API, Now Available in Public Beta blog.heroku.com/archives/... · Posted by u/Lightning

aeden · 12 years ago

Billing and provisioning. Please oh please let us provision new Heroku accounts. :-)

geemus · 12 years ago

Billing is definitely on our todo list as we progress with the beta. Provisioning new accounts is a little trickier as it could potentially open the door to abuse. Which isn't to say we'll never do it or that it isn't possible, just that it is more complicated.

geemus commented on Heroku Platform API, Now Available in Public Beta blog.heroku.com/archives/... · Posted by u/Lightning

benologist · 12 years ago

What I'm imagining is click a button and have it create and deploy fully configured apps for me, similar to what I can do with all the add on services. They might be paid or free or tiered etc, it might be a once-off fee or a monthly/annual subscription or an on-going charge like some of Amazon's AMIs.

There's lots of commercially licensed, self-hosted software (blog, forum, ecommerce etc) and hosted-as-a-service (wordpress.com, discourse.org, duelapp.com etc) etc that would be applicable.

Enabling that by API or in general would be awesome.

geemus · 12 years ago

I was pretty sure that was the kind of thing you meant, but just wanted to clarify. The API should certainly facilitate doing the kind of setup and management that this would require. But it doesn't currently provide a direct way to do the billing portion of things. So I think it could be a ready solution to open source self-hosted stuff, for instance, but you would have to provide your own billing stuff for commercially licensed things.