@kentcdodds @airtable @Netlify @bdougieYO I'd use a placeholder instead of a splat. Like this:
https://github.com/philhawksworth/hawksworx.com/blob/master/netlify.toml#L46-L48
@kentcdodds @airtable @Netlify You can respond with any HTTP response code you like, including 301, 302 or 200. But I've not tried this scenario where the destination is returned dynamically.
@kentcdodds @airtable Totally.
@Netlify's redirect API supports placeholders, splats and query params.
The docs describe them here:
https://www.netlify.com/docs/redirects/#placeholders
@Netlify's redirect API supports placeholders, splats and query params.
The docs describe them here:
https://www.netlify.com/docs/redirects/#placeholders
@kentcdodds @airtable For fun, when Netlify Functions were lunched, I made a quick and dirty URL shortener with serverless functions and the Netlify redirects API which runs on the CDN.
https://www.netlify.com/blog/2018/03/19/create-your-own-url-shortener-with-netlifys-forms-and-functions/
https://www.netlify.com/blog/2018/03/19/create-your-own-url-shortener-with-netlifys-forms-and-functions/
@leolabs_org My own sites seem to be building fine.
Are you seeing this on multiple sites or recurring on one site in particular?
Are you seeing this on multiple sites or recurring on one site in particular?
@perrysetgo @Netlify Excited that you are back!
We missed you.
And were not jealous of your marvellous looking vacation at all.
We missed you.
And were not jealous of your marvellous looking vacation at all.
@iamMrDuncan Complementary, but not synonymous, IMO. At least if one interprets "serverless" as "functions as a service".
But if you take serverless to mean, "serving things without a need to care about underlying physical or virtual server infrastructure", then perhaps.
I find that broad.
But if you take serverless to mean, "serving things without a need to care about underlying physical or virtual server infrastructure", then perhaps.
I find that broad.
@crgeary @muzzlehatch_ @smashingmag That's only baffling to me if it purely means "I would never use this under any circumstances" rather than "it was not a perfect fit for my use case", as I would prefer to suspect.
Or else, there must have been some misunderstanding about what #JAMstack actually means
Or else, there must have been some misunderstanding about what #JAMstack actually means
@kmelve @wesbos @stolinski I like that too.
And I honestly don't care too much about what term is used, as long as we have a way to describe a CMS that lets you have complete control over the front end and hosting infrastructure. I often talk about things being "decoupled" rather than "headless".
And I honestly don't care too much about what term is used, as long as we have a way to describe a CMS that lets you have complete control over the front end and hosting infrastructure. I often talk about things being "decoupled" rather than "headless".
@johnnyxbell @stefanjudis @biilmann @Netlify Nope. You can create as many as you need here: https://app.netlify.com/account/applications
@muzzlehatch_ @smashingmag I'm not totally surprised.
And I see that as a huge opportunity for those already working in thew #JAMstack space.
And I see that as a huge opportunity for those already working in thew #JAMstack space.
Enjoying this by @kmelve and agreeing that "Structured content" services are incredibly valuable. For me though, there is still value in describing a CMS as "headless" if only to indicate that it will not impose its own code generation and bottleneck at request time. https://twitter.com/kmelve/status/1069279518228135937
Watching this #JAMstack poll from @smashingmag with interest. https://twitter.com/smashingmag/status/1069495500074872832
@stefanjudis @Netlify This is shaping up really nicely! What if you could also drag a folder onto it, like with http://Netlify.com/drop?!
@aloukissas @Netlify This documentation for single page apps might be what you need:
https://www.netlify.com/docs/redirects/#rewrites-and-proxying
https://www.netlify.com/docs/redirects/#rewrites-and-proxying
RT @frontendyork: 6 spots left at our event next week! Please make sure to RSVP as we're going to be very limited on space! Who knew gettin…