@jan_joris @WesleyCabus @ddoomen @Netlify @NetlifyCMS @Cloudflare @letsencrypt Yeah, that DNS admin feature is quite new. Great article. Thank for sharing!
@jan_joris @WesleyCabus @ddoomen @Netlify @NetlifyCMS @Cloudflare I see. (although that link 404s for me)
I've seen some use it for https, although you get free with a couple of clicks on Netlify thanks to @letsencrypt.
Meanwhile, Netlify now has more DNS tools built in so you can manage MX records and subdomains. https://www.netlify.com/blog/2017/12/19/an-easier-way-to-manage-domains-and-dns-on-netlify/
I've seen some use it for https, although you get free with a couple of clicks on Netlify thanks to @letsencrypt.
Meanwhile, Netlify now has more DNS tools built in so you can manage MX records and subdomains. https://www.netlify.com/blog/2017/12/19/an-easier-way-to-manage-domains-and-dns-on-netlify/
@jan_joris @WesleyCabus @ddoomen @Netlify @NetlifyCMS @Cloudflare Yay! Thanks for that shout. I'm curious... what are you using Cloudflare to do for you as part of that stack?
@robjloranger @bketelsen @nicholaswyoung @Netlify These tweets make me happy! Was that less than 30 minutes from saying "fine, I'll sign up on my phone" to having a site deployed (and finding a gif of an "easy" button)?
If so... BRAVO!
If so... BRAVO!
Phil Hawksworth
@philhawksworth •
Try to look at this site from @CodePen without smiling. Just try it!
Joyful at many different viewport sizes.
https://codepenworldsfair.com/
Joyful at many different viewport sizes.
https://codepenworldsfair.com/
@martinjhnhadley @Netlify That may have been it. People in the team far smarter than me have created tools to spot spammy things.
They are also the folks who sorted this out. If you have any other issues, mentioning it to support is a good way to access those boffins who are happy to help.
😃
They are also the folks who sorted this out. If you have any other issues, mentioning it to support is a good way to access those boffins who are happy to help.
😃
@AskAtlassian Wonderful. Many thanks!
@chrisdarroch @Bitbucket @github @gitlab That's too bad. Perhaps @Bitbucket can be persuaded to give this issue some ♥️
It was raised in 2012 but got a lot of discussion and seemed to be close to some action about a year ago.
https://bitbucket.org/site/master/issues/5814/refify-pull-requests-by-making-them-a-ref
It was raised in 2012 but got a lot of discussion and seemed to be close to some action about a year ago.
https://bitbucket.org/site/master/issues/5814/refify-pull-requests-by-making-them-a-ref
@martinjhnhadley @Netlify Things should be back in good order, Martin. I gather that for some reason your account had triggered some of our spam heuristics. Please let us know if you see any more issues.
@martinjhnhadley @Netlify Oooh. What's happening there? Have you pinged the Support team via http://app.netlify.com, Martin?
@bketelsen @Netlify Thanks Brian. I love it too. The team worked really hard to make things feel easy. I can't remember enjoying the process of developing things more!
Phil Hawksworth
@philhawksworth •
RT @SLHYork: One of our Accumulator Challenge teams @gouyclub have come up with an innovative fundraising idea. They've put all the details…
@qubyte @Netlify I'd recommend pinging the Support team via http://app.netlify.com. That sounds like something that they'd be able to give good advice on.
Phil Hawksworth
@philhawksworth •
Phil Hawksworth
@philhawksworth •
Quite enjoyed letting my dad argue with this painting for a while before explaining that the ticket window had been replaced by an app. http://ift.tt/2DW2Umt
@heydonworks Yep. Future Phil.
Phil Hawksworth
@philhawksworth •
Trouble at the top of the leaderboard for Yorkshire's chubbiest cheeks, as contestants lose poise to a bout of "the giggles". http://ift.tt/2E32vhd
Phil Hawksworth
@philhawksworth •
Pops versus the fish and chips. There could only ever be one winner. http://ift.tt/2BMo4Nz
@apollographql @Netlify We were indeed. Apologies for that. Things seem to have been resolved pretty quickly but there is some further investigation going on into the root cause. More info (for this and in general) via @netlifystatus
@joeybeninghove @Netlify Thanks for your understanding. We're investigating the root cause further, but things should be back to being happily served again.
@joeybeninghove @Netlify @netlifystatus The issue has been resolved. A little more info here:
https://twitter.com/netlifystatus/status/959114143545491456
https://twitter.com/netlifystatus/status/959114143545491456
@joeybeninghove @Netlify @netlifystatus Apologies Joey. And thanks for reporting. We are also seeing some issues. The team is investigating as I type this. Update will be forthcoming as soon as we are able.
https://twitter.com/netlifystatus/status/959109732349878277
https://twitter.com/netlifystatus/status/959109732349878277