@zachleat @growdigital @Netlify It must happen!
I've toyed with that phrase before in talks about @netlify, but never taken it all the way up to 88mph.
⏪ Step *back through time* to see any previous deploy.
⏩ See what the site will look like *in the future* thanks to preview builds
https://www.netlify.com/blog/2016/07/20/introducing-deploy-previews-in-netlify/
I've toyed with that phrase before in talks about @netlify, but never taken it all the way up to 88mph.
⏪ Step *back through time* to see any previous deploy.
⏩ See what the site will look like *in the future* thanks to preview builds
https://www.netlify.com/blog/2016/07/20/introducing-deploy-previews-in-netlify/
@mattferderer @growdigital @Netlify Also, even with cached DB requests, you still need to render views and serve things on demand. Granted, adding layers of caching can expedite requests, but you are really adding layers of logic that you have to manage yourself which essentially make things behave as if static. :)
@mattferderer @growdigital @Netlify It's hard to know what state a site using cached DB request is in at any given time. And the developer needs to manage and invalidate that cache and interdependencies.
A static site can be wholly cached as an atomic, immutable deploy. Netlify does that for you automatically.
A static site can be wholly cached as an atomic, immutable deploy. Netlify does that for you automatically.
@notwaldorf **Adds Time Lord to LinkedIn profile**
Hey, remember that time you said I was a time lord? Wasn't that a nice moment? I remember it vividly. That http://setyourwatchby.netlify.com site looked exactly like this: https://5b634d0667610c4f935c85e2--setyourwatchby.netlify.com/
Sometimes I go there to reminisce.
Hey, remember that time you said I was a time lord? Wasn't that a nice moment? I remember it vividly. That http://setyourwatchby.netlify.com site looked exactly like this: https://5b634d0667610c4f935c85e2--setyourwatchby.netlify.com/
Sometimes I go there to reminisce.
@zachleat @growdigital @Netlify Ha ha. That would be silly 😜. We'd not be able to look back at the exact state of the clock at any given minute of any day since it was launched just by visiting the unique URL for that deploy. And we NEED that.
WE NEED IT, ZACH!
WE NEED IT, ZACH!
@nhoizey @eleven_ty Ha. Interesting question. But no. All the dependencies are cached between deployments on @Netlify for speed and stability. Yarn or npm install only happens if the package.json file changes.
I made a thing.
Then I wrote about it. https://twitter.com/Netlify/status/1025046932857806851
Then I wrote about it. https://twitter.com/Netlify/status/1025046932857806851
@growdigital @Netlify That's a good instinct! It is wasteful. I'm not advocating for us all to perform fresh builds every minute. But I wanted to demonstrate that there are tools that let us rebuild and redeploy cheaply/frequently, and those can be triggered by many different events.
Not so static.
Not so static.
@LoganHoup @Netlify Not currently. You have ability to create rules based on country and language... but not timezone or city. I've heard conversations though... so who knows!
Meanwhile, all of America is sent to the LA timezone(!) unless you choose one explicitly: https://setyourwatchby.netlify.com/timezones
Meanwhile, all of America is sent to the LA timezone(!) unless you choose one explicitly: https://setyourwatchby.netlify.com/timezones
@tomantonis I guess so. As long as you know your position in the world and the relative bearing from there to Mecca. This does all that for you.
@NechitaGabriel @Netlify I'm not totally sure tbh... but higher than that. What you are describing sounds perfectly reasonable to me.
Of course, if it becomes something you depend on for business usage, it's worth considering one of the paid tiers... but you'll be fine with that sort of number.
Of course, if it becomes something you depend on for business usage, it's worth considering one of the paid tiers... but you'll be fine with that sort of number.
@NechitaGabriel @Netlify Nope.
Although I believe that if you get into very high numbers of sites, there are heuristics that try to identify any behaviour that might suggest spammy usage. But you should be fine.
Although I believe that if you get into very high numbers of sites, there are heuristics that try to identify any behaviour that might suggest spammy usage. But you should be fine.
@trickydisco78 @Netlify @biilmann I'm sorry, I don't quite understand. Are you using a free {something}.netlify.com subdomain, or are you directing your own custom domain to netlify, or have you purchased a domain directly through Netlify?
@trickydisco78 @Netlify That's right. It helps your site become more resilient to changes in underlying network configurations and the fun and games that is DNS.
In addition to what you'll find in our docs, @biilmann wrote some good info on this: https://www.netlify.com/blog/2017/02/28/to-www-or-not-www/
In addition to what you'll find in our docs, @biilmann wrote some good info on this: https://www.netlify.com/blog/2017/02/28/to-www-or-not-www/
@keithdamiani @fideloper @stauffermatt @michaeldyrynda @Netlify I'll defend @michaeldyrynda's use of the word "squiz" to my dying breath. 🧐
Now, I'm off to take a cheeky squiz at that video.
Now, I'm off to take a cheeky squiz at that video.
@AJKandy Documentation and living styleguides are both sweet spots for static site generators, and for using various component models.
@Netlify hosts the docs for lots of big projects who employ a variety of those techniques. To name a few:
https://twitter.com/Netlify/status/1011233062066294784
@Netlify hosts the docs for lots of big projects who employ a variety of those techniques. To name a few:
https://twitter.com/Netlify/status/1011233062066294784
@rachelandrew Sounds like a reasonable requirement. And something that a static site generator could eat for breakfast.
Most have concept of macros or shortcodes to help with exactly this.
Most have concept of macros or shortcodes to help with exactly this.