A question I got at #WeAreDevs was, "What technology is @Netlify built on?" I hinted that there was a lot of complexity hidden behind the simplicity. This fascinating post talks about just one aspect: our multi-cloud CDN and multi-cloud origin servers.
https://medium.com/netlify/how-netlify-migrated-to-a-fully-multi-cloud-infrastructure-cfca95bbbb0f
Thanks to everyone at #WeAreDevs who came to hear me speak about Next Wave Infrastructure.
The slides and link to the #serverless demo I showed are now online. I dare you to try that yourself! 1click to click off that entire process.
https://noti.st/philhawksworth/8ryB2o/next-wave-infrastructure-and-how-to-use-it-for-an-easier-life
The slides and link to the #serverless demo I showed are now online. I dare you to try that yourself! 1click to click off that entire process.
https://noti.st/philhawksworth/8ryB2o/next-wave-infrastructure-and-how-to-use-it-for-an-easier-life
@WeAreDevs Find it tricky to build & deploy #serverless functions with confidence? My talk at #WeAreDevs includes a demo of what might be the fastest way to get started. With:
- Git-based deploys
- Immutable versions
- Instant unlimited instant staging envs
...in under 7mins.
- Git-based deploys
- Immutable versions
- Instant unlimited instant staging envs
...in under 7mins.
@WeAreDevs You built something great & it's time to launch it, but deploying it was hard. You had fixes to release, but it took forever to get them live, and they broke something else. This should be easier!
Find out how (& WTF?*) - #WeAreDevs, Stage D, 15:15
*why the fruit?
Find out how (& WTF?*) - #WeAreDevs, Stage D, 15:15
*why the fruit?
Last time was a blast, so we're doing it again. Tickets going fast for the next @comedyincrown night.
http://wegottickets.com/comedyinthecrown
http://wegottickets.com/comedyinthecrown
RT @stefanjudis: Whoop whoop! I just published an article describing how I decreased build times for my @contentful powered static site on…
@raymondcamden Hide the key from the client, right? The client making the request to /images/* would not see the secret in the request to giphy if you return a 200.
@raymondcamden Can you explain a little more? I don't quite understand.
You can return whatever response code you like.
More details and examples here: https://www.netlify.com/docs/redirects/
You can return whatever response code you like.
More details and examples here: https://www.netlify.com/docs/redirects/