Live data from Hacker News

Next-generation Deploy Previews, plus Netlify acquires FeaturePeek (YC S19)

netlify.com

31–33 of 33 posts

Re: Next-generation Deploy Previews, plus Netlify acquires FeaturePeek (YC S19)

#31

> About five years ago, Netlify pioneered the concept of Deploy Previews. Doesn’t Heroku’s “Review Apps” predates this? https://blog.heroku.com/heroku_review_apps_beta (funnily enough, it’s been exactly 6 years ago today based on the beta’s blog post above)

There was a company called Runnable that had a product offering, but if I recall correctly was acquired by MuleSoft and shut down.

Their first round was in 2012, and even though I believe they had a different product originally, their preview environment offering predated Heroku’s.

Re: Next-generation Deploy Previews, plus Netlify acquires FeaturePeek (YC S19)

#32

> About five years ago, Netlify pioneered the concept of Deploy Previews. Doesn’t Heroku’s “Review Apps” predates this? https://blog.heroku.com/heroku_review_apps_beta (funnily enough, it’s been exactly 6 years ago today based on the beta’s blog post above)

I think even Heroku is not the first company offering this to public. There was an app called Teatro.io which did the same in 2014. It's down now, but I've found https://web.archive.org/web/20140614011544/http://teatro.io/.

Re: Next-generation Deploy Previews, plus Netlify acquires FeaturePeek (YC S19)

#33
post #21

For preview URLs how are y'all handling SSO? No SSO provider supports wildcard redirect URIs. Looking for ideas...

I ran into this issue when setting up UI previews for a GitHub OAuth app. My solution is to have a single callback server that looks in the OAuth state to determine where to redirect. This isn't secure, so when building the UI, I sign the UI's preview URL with a secret and send that in the OAuth state. The callback server checks the signature and redirects that way. It's hacky and I wouldn't trust it for a production…

Excellent idea, thanks!
Post reply on HN