@ryanfiller_ @brob @gatsbyjs @Netlify Thanks Ryan! Keen to see where this ends up. Out of curiosity, without clearing the build cache, do the builds fail or just appear to not update on the browser after the deploy?
@brob @gatsbyjs @Netlify You bet!
I'm a touch baffled by @ryanfiller_'s first tweet in this thread. Not sure why a manual build-cache purge should be necessary. That should happen automatically if the deps need updating.
Would be interested on the results of any explorations.
I'm a touch baffled by @ryanfiller_'s first tweet in this thread. Not sure why a manual build-cache purge should be necessary. That should happen automatically if the deps need updating.
Would be interested on the results of any explorations.
Phil Hawksworth
@philhawksworth •
Triggered a little by this from @dhh, I had a very quick play with generating a site from a Medium RSS feed.
https://rss-jamstack.netlify.com/
Modern SSGs on the #JAMstack make this a joy! 🤗
I'll keep it up-to-date by having @ifttt ping a @Netlify deploy hook whenever the feed changes. https://twitter.com/dhh/status/1037398155879309312
https://rss-jamstack.netlify.com/
Modern SSGs on the #JAMstack make this a joy! 🤗
I'll keep it up-to-date by having @ifttt ping a @Netlify deploy hook whenever the feed changes. https://twitter.com/dhh/status/1037398155879309312
Phil Hawksworth
@philhawksworth •
There's gold in this from @rem:
https://remysharp.com/2018/08/23/cli-improved
I'm going to have to level up my CLI fu.
💻📈
https://remysharp.com/2018/08/23/cli-improved
I'm going to have to level up my CLI fu.
💻📈
@gaddafirusli @Netlify Well, I can't disagree with that! 😜
Then again, if the biggest lock-in is the potential headache of switching DNS some time in the future ...that feels like the most open lock available! 🤓
Then again, if the biggest lock-in is the potential headache of switching DNS some time in the future ...that feels like the most open lock available! 🤓
@gaddafirusli @Netlify That's one of the advantages of static sites. As long as you can generate them yourself (which will be part of your dev process anyway) then you have greater portability for a future move if you need.
🥚🥚🥚🥚🥚🥚
🥚🥚🥚🥚🥚🥚
Phil Hawksworth
@philhawksworth •
Swooning rather deeply at @eleven_ty once again.
✨
Data files can now include executable JavaScript, so you can execute code to fetch data at build time
✨
https://www.11ty.io/docs/data-js/
✨
Data files can now include executable JavaScript, so you can execute code to fetch data at build time
✨
https://www.11ty.io/docs/data-js/
@simonswiss @vuejs How many gets could a getter get if a getter could get gets?
@MinaMarkham @eleven_ty @Netlify Fun, right?!
I got addicted, and now I have a site that I deploy every single minute!
https://setyourwatchby.netlify.com
I got addicted, and now I have a site that I deploy every single minute!
https://setyourwatchby.netlify.com
@patrick_h_lauke @Netlify @IanPouncey Noted. Ta! 🤓
You can do some pattern matching with wildcards and splats FWIW.
https://www.netlify.com/docs/redirects/#splats
You can do some pattern matching with wildcards and splats FWIW.
https://www.netlify.com/docs/redirects/#splats
@patrick_h_lauke @Netlify @IanPouncey "All the setting up"
https://twitter.com/Netlify/status/1029433619222278145
https://twitter.com/Netlify/status/1029433619222278145
@cdvillard @reybango @SiteGround @Netlify Or you could scoop the content into a static site at build time and serve it with no JS for free... including a free auto-renewing cert for HTTPS thanks to @letsencrypt on @Netlify
https://fettblog.eu/wordpress-and-jamstack-sites/
But I am biased (by cost, stability, features, perf, and um... salary 😜)
https://fettblog.eu/wordpress-and-jamstack-sites/
But I am biased (by cost, stability, features, perf, and um... salary 😜)
@dakotabryantCO @gatsbyjs @Netlify Those neon logos tho! 😍😍😍
@mojavelinux @bk2204 @Netlify Ah. I see!
And as it turns out, you are quite right. This feature is currently undergoing some testing and you can probably expect to see it before long on @Netlify!
TIL! 🧐
And as it turns out, you are quite right. This feature is currently undergoing some testing and you can probably expect to see it before long on @Netlify!
TIL! 🧐
Phil Hawksworth
@philhawksworth •
If you decide to detect and advertise my presence @jack, I'll make it a tiny bit easier for you to implement by being gone forever. https://twitter.com/jack/status/1035633081862901760
@mojavelinux @bk2204 @Netlify Could the solution to this be using git branches? That sounds like a perfect use of them and you can set @Netlify to build all, none, or any of them you specify.
@jobsworth @psd Printing and framing this thread.
Phil Hawksworth
@philhawksworth •
@mr_ligi @pedrouid @Netlify @letsencrypt True. @github apps have introduced that, although that was not previously the case, which is why we implemented this in the least intrusive way available, never receiving creds.
The process of creating a well integrated @GitHub app takes a little time. (but watch this space! 🙂)
The process of creating a well integrated @GitHub app takes a little time. (but watch this space! 🙂)
@mr_ligi @pedrouid @bmann @MPtherealMVP @Netlify @letsencrypt Heh... our tweets crossed mid-air!
https://twitter.com/philhawksworth/status/1036610205369491456
https://twitter.com/philhawksworth/status/1036610205369491456