@pepelsbey_ I'm not aware of an issue with gulp v4. Although I do notice that I am using v3.9.1 for all of my own projects. (Not through a decision to resolve this though).
Let me investigate.
Let me investigate.
@Nujcharee Nice!
@auchenberg This is fucking madness.
@LucasTizma DNS propagation is the watched pot which never boils! Especially when you want to share the cool results of your hard work!
@LucasTizma Just took a peep and it looks like all is well (DNS has propagated for me over in England, at least)... and things are looking snappy!
@LucasTizma That's very possible. The docs hint at how to inspect what IP your domain is resolving to. That's a good place to start.
@LucasTizma Hmmm. There are some tips in the docs to help troubleshoot your DNS config and be sure that your nameservers are pointing to the right things.
https://www.netlify.com/docs/dns/
Otherwise if you contact support from within the Netlify admin, they'll be able track what's up and help.
https://www.netlify.com/docs/dns/
Otherwise if you contact support from within the Netlify admin, they'll be able track what's up and help.
@katie_fenn I love, Love, LOVE that space shuttle!
Phil Hawksworth
@philhawksworth •
Woah! @Netlify are starting the year by giving away all of our secrets.
https://twitter.com/ohpalmer/status/948272456594227200
https://twitter.com/ohpalmer/status/948272456594227200
@IMAC2 @_Nec @SaraSoueidan @Netlify It does. Netlify takes the output of your build and automatically deploys it to its global CDN. Lots of the smart stuff happens right on the CDN at the edge.
Even A/B testing, custom redirections, language and regional content routing happen at the CDN level.
Even A/B testing, custom redirections, language and regional content routing happen at the CDN level.
@LucasTizma @daveaglick @TannerLD @Netlify This thread fills me up with a warm fuzzy feeling. Especially the timings.
Hoping that you find you can do all you need. Welcome!
Hoping that you find you can do all you need. Welcome!
@brad_frost @chriscoyier We'll try again next year.
@bitandbang @TheAndrewWyatt @auchenberg @TheLarkInn Agreed. Making the most of APIs, optimised & provided by specialists is a huge enabler - either client-side or server-side at build time, APIs can add functionality & enliven content.
Automated builds and rapid deploys triggered by events can now make static sites feel dymanic.
Automated builds and rapid deploys triggered by events can now make static sites feel dymanic.
@TheAndrewWyatt @auchenberg @TheLarkInn @bitandbang One of this big things for me is just shifting attitudes. We often turn to Node, PHP, Python be default whenever we build something. Even if it is not best served by moving parts on infrastructure you have to secure, scale and maintain forever.
Does a blog really need a DB?
Does a blog really need a DB?
@TheAndrewWyatt @auchenberg @TheLarkInn @bitandbang It's a new label for mostly old technology. But the tooling and the mindset is different. With automation and careful thought "static" can do so much that we currently over engineer fragile, complex things to do.
+ Security, scale & perf are by default not hard fought to get
+ Security, scale & perf are by default not hard fought to get
@DasSurma @notwaldorf @jaffathecake Let's be honest. It's a miracle that he doesn't just rub his body with mud and stick moss and ferns over his rude bits.