@kentcdodds @CarlRosell @Netlify @airtable And mostly, I like this approach since it means I don't need to worry about caching. (which as you know, is fiddly at best).
Maybe not great for a system that has many thousand of redirect rules though. In that case a function and a db like your approach probably scales better
@kentcdodds @CarlRosell @Netlify @airtable There's not fee to hook @Netlify up to private repos. đ
@CarlRosell @kentcdodds @Netlify @airtable Ha ha! I know the feeling.
I made a tool to generate that _redirects file based on the urls posted to @Netlify's forms API. This way the redirect happen directly at the CDN level so are crazzzzzy fast. But it's a bit of a toy/example project.
https://www.netlify.com/blog/2018/03/19/create-your-own-url-shortener-with-netlifys-forms-and-functions/
I made a tool to generate that _redirects file based on the urls posted to @Netlify's forms API. This way the redirect happen directly at the CDN level so are crazzzzzy fast. But it's a bit of a toy/example project.
https://www.netlify.com/blog/2018/03/19/create-your-own-url-shortener-with-netlifys-forms-and-functions/
RT @Netlify: This should be an interesting stream to watch. @kentcdodds is live-streaming his first #serverless experiments with @Netlify FâŚ
@Olivierjmm @Netlify Couple that with the ability to instantly rollback to any previous build in the history of your project, and what you have... is a time machine!
https://www.netlify.com/docs/versioning-and-rollbacks/#rollbacks
https://www.netlify.com/docs/versioning-and-rollbacks/#rollbacks
Let's be very clear - The daily #christmasdeskdance by @Mandy_Kerr is like a little dose of sunshine which everyone should be tuning in to enjoy.
@AndyWhalePhoto @frontendyork @imconnorm @AndyCallaghan @Netlify Yep. I like to think about putting as much distance as possible between the users, and the complexity.
Serving assets directly from a CDN after pre-rendering everything can be huge in this regard. And adding small pieces of logic via serverless functions can fill any last gaps.
Serving assets directly from a CDN after pre-rendering everything can be huge in this regard. And adding small pieces of logic via serverless functions can fill any last gaps.
@Una @Mandy_Kerr Twitter has not done that for me, which leaves me woefully exposed to the risk of missing one of these.
Just kidding. It's my most actively refreshed hashtag.
Fascinated to see what further variations of joyous dancing you can bring right up to the 24th. đ
Just kidding. It's my most actively refreshed hashtag.
Fascinated to see what further variations of joyous dancing you can bring right up to the 24th. đ
@AndyWhalePhoto @frontendyork @imconnorm @AndyCallaghan @Netlify Thanks Andy!
Have fun. Let me know if you have any questions.
Have fun. Let me know if you have any questions.
@SamTurrellDev @frontendyork @Netlify @vue_london Thanks for having me! I really enjoyed the evening. Good chatting with you, Sam. And congrats on your recent success at the #PressAwards18 with @netsells!
My last talk of the year... Looking forward to this! https://twitter.com/SearchableRosie/status/1070364433975820291
@pugson @NetlifySupport @rafahari You might find this example useful:
https://github.com/imorente/gatsby-netlify-form-example/blob/master/src/pages/file-upload.js#L27
https://github.com/imorente/gatsby-netlify-form-example/blob/master/src/pages/file-upload.js#L27
@kentcdodds @airtable @Netlify @bdougieYO Looks like the build and config is all ok. But that there is an issue with that lambda in particular. As @biilmann suggested.
@kentcdodds @airtable @Netlify @bdougieYO Have you looked at the logs from the functions via the Netlify admin UI? Each invocation should be logged there along with anything you console.log in the function.
@kentcdodds @airtable @Netlify @bdougieYO Just at dinner right now (in the UK), so sorry this is brief:
This line should tell Netlify where to find your once they have been built:
https://github.com/kentcdodds/airtable-netlify-short-urls/blob/master/netlify.toml#L3
and this should point at your source functions are so that they can be built:
https://github.com/kentcdodds/airtable-netlify-short-urls/blob/master/package.json#L9
Path problems?
This line should tell Netlify where to find your once they have been built:
https://github.com/kentcdodds/airtable-netlify-short-urls/blob/master/netlify.toml#L3
and this should point at your source functions are so that they can be built:
https://github.com/kentcdodds/airtable-netlify-short-urls/blob/master/package.json#L9
Path problems?