For preview URLs how are y'all handling SSO? No SSO provider supports wildcard redirect URIs. Looking for ideas...
Next-generation Deploy Previews, plus Netlify acquires FeaturePeek (YC S19)
21–30 of 33 posts
Re: Next-generation Deploy Previews, plus Netlify acquires FeaturePeek (YC S19)
#22For preview URLs how are y'all handling SSO? No SSO provider supports wildcard redirect URIs. Looking for ideas...
Auth0 does, thankfully! I set my redirect uri to `https://deploy-preview-*--my-cool-netlify-app-staging.netlif...` just the other day. :)
They have a few rather specific rules about it, but it works for deploy previews anyway: https://auth0.com/docs/applications/wildcards-for-subdomains
Re: Next-generation Deploy Previews, plus Netlify acquires FeaturePeek (YC S19)
#23If anyone is interested in a (semi!) working version of feature previews that is open source, I threw together https://gitlab.com/Rodeoclash/StageHand
It takes a branch in GitHub and use a config file to bootstrap the application inside a K8's cluster using a "docker in docker" model. If you could describe your infrastructure as a docker-compose.yml then you can launch it as a preview.
I'm not really a marketing person so it never went any further than a proof of concept. However, if someone is interested in working with it then I'm happy to support getting it running.
Re: Next-generation Deploy Previews, plus Netlify acquires FeaturePeek (YC S19)
#24For preview URLs how are y'all handling SSO? No SSO provider supports wildcard redirect URIs. Looking for ideas...
Auth0 does, thankfully! I set my redirect uri to ` https://deploy-preview-*--my-cool-netlify-app-staging.netlif... ` just the other day. :) They have a few rather specific rules about it, but it works for deploy previews anyway: https://auth0.com/docs/applications/wildcards-for-subdomains
Auth0 does, but IIRC it does not support multiple or not-last wildcards. Ie “app.*.preview.” does not work.
If your application itself has subdomains, Auth0 doesn’t solve this easily
Re: Next-generation Deploy Previews, plus Netlify acquires FeaturePeek (YC S19)
#25> 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)
Re: Next-generation Deploy Previews, plus Netlify acquires FeaturePeek (YC S19)
#26For 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 app, but for a test environment it seems okay.
Re: Next-generation Deploy Previews, plus Netlify acquires FeaturePeek (YC S19)
#27This looks great and all but the new drawer icon covers up a key button on our app.. ironically the person who noticed took a regular screenshot and shared it in slack
Re: Next-generation Deploy Previews, plus Netlify acquires FeaturePeek (YC S19)
#28> 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 remember using ephemeral Heroku deploys in the dev pipeline well before I knew Netlify was a thing. That was pretty much the last major innovation I saw from Heroku, before Salesforce decided they'd grown fat enough to milk.
But...there were also pipelines. A deploy preview is essentially a staging or pre-prod environment. Or going from draft to published.
Re: Next-generation Deploy Previews, plus Netlify acquires FeaturePeek (YC S19)
#29> 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)
They were in fairly wide "unofficial" customer usage for a year before that too I think.
source: my last day at Heroku was a year prior to that post, and I recall using them.
Re: Next-generation Deploy Previews, plus Netlify acquires FeaturePeek (YC S19)
#30A year or so ago I was working on a similar product as FeaturePeek - a platform agnostic deploy preview and collaboration tool. I decided not enough people would want that outside of their hosting platform and shelved it. Clearly I was wrong and clearly why you should talk to more potential customers before you make decisions. Congrats to Netlify and FeaturePeek.
Unless you have inside information on the terms of the acquisition, I wouldn't beat yourself up about what might have been. There's a very broad spectrum of options here between "we like the team and have agreed to put them on payroll because it's cheaper and faster than using recruiters" to "F$%@ you money for the founders". We've no way to know which it is.