@RawInfoSec @Scott_Helme @troyhunt Thankfully everyone who hosts their own WordPress site is also an expert at securing a LAMP stack server and a DBA. It's fine.
@DinisCruz @Azizur @Netlify @GoHugoIO That is a feature on the paid plan. https://www.netlify.com/pricing/
@benpbarnett An excellent leaving present from those lovely folks at @rga.
Now the whole world can enjoy crystal clear audio quality as I shout "get off the feckin' keyboard! You're sending tweets with your arrrrrrse"
Now the whole world can enjoy crystal clear audio quality as I shout "get off the feckin' keyboard! You're sending tweets with your arrrrrrse"
@DavidDarnes @Netlify Ha ha. Amazing.
@Scott_Helme @troyhunt If only there were an easy way to control your HTTP headers so you could sort this out without fuss.
oh, hai @Netlify's _headers config:
https://medium.com/netlify/10-netlify-features-to-surprise-and-delight-225e846b7b21#8161
oh, hai @Netlify's _headers config:
https://medium.com/netlify/10-netlify-features-to-surprise-and-delight-225e846b7b21#8161
@DavidDarnes I double dare you.
Phil Hawksworth
@philhawksworth •
Me: I think I'll do a little work.
Her: Do you. http://ift.tt/2Cz00z6
Her: Do you. http://ift.tt/2Cz00z6
Phil Hawksworth
@philhawksworth •
Brilliantly written and chillingly convincing. A pretty persuasive argument for site owners to sort out their CSPs (Content Security Policies). I can almost see @Scott_Helme and @troyhunt nodding along.
https://medium.com/@david.gilbertson/im-harvesting-credit-card-numbers-and-passwords-from-your-site-here-s-how-9a8cb347c5b5
https://medium.com/@david.gilbertson/im-harvesting-credit-card-numbers-and-passwords-from-your-site-here-s-how-9a8cb347c5b5
@DinisCruz @Azizur @Netlify @GoHugoIO Just a thought... If you need people to quickly spin up an instance of a site from your template, they can do this with *almost* one click via the @netlify Deploy Button.
https://www.netlify.com/docs/deploy-button/
Nice example here(you are quite safe to click it!):
https://www.netlifycms.org/docs/start-with-a-template/
https://www.netlify.com/docs/deploy-button/
Nice example here(you are quite safe to click it!):
https://www.netlifycms.org/docs/start-with-a-template/
@DinisCruz @Azizur @Netlify I think the same properties are true of @GoHugoIO. You can run the site locally during dev (the speed of that makes developing and populating a delight, BTW) or push to a github for an instant rebuild and deploy on @Netlify.
But whatever #jamstack setup is working for you!
But whatever #jamstack setup is working for you!
@_munter_ @RyanTownsend @Netlify @adactio Wouldn't have been a problem if I had been a good boy when I decided to simplify my URLs and instigated a proper redirect pattern to handle all of that!
I was either forgetful or ignorant of how to do that on GH-Pages.
Naughty Philip.
I was either forgetful or ignorant of how to do that on GH-Pages.
Naughty Philip.
@_munter_ @RyanTownsend @Netlify This is handy.
In my case I spotted inbound links from a post from @adactio back in 2009, which used a url format I had on my blog and later simplified.
https://domscripting.com/blog/display/120
I thought I had correctly redirected everything around 2011, but I forgot a pattern I once used.
In my case I spotted inbound links from a post from @adactio back in 2009, which used a url format I had on my blog and later simplified.
https://domscripting.com/blog/display/120
I thought I had correctly redirected everything around 2011, but I forgot a pattern I once used.
@RyanTownsend @Netlify I was just looking at my Google Analytics and seeing some 404 hits.
Currently that type of logging access and reporting is not available directly from Netlify.
Currently that type of logging access and reporting is not available directly from Netlify.
@robmuh @captainsafia @Netlify I like that mindset shift. #jamstack by default (unless something more is *genuinely* warranted) rather than LAMP or MEAN stack by default, even if all the moving parts could have been avoided.
Phil Hawksworth
@philhawksworth •
🤔 Spotting 404s on my blog caused by links to an old URL pattern I later simplified. Thought I dealt with that years ago, but fixed it in moments today thanks to @netlify's simple _redirects config:
/blog/:year/:month/:day/:slug /blog/:slug 301
😎
https://medium.com/netlify/10-netlify-features-to-surprise-and-delight-225e846b7b21#7007
/blog/:year/:month/:day/:slug /blog/:slug 301
😎
https://medium.com/netlify/10-netlify-features-to-surprise-and-delight-225e846b7b21#7007
@auchenberg Sorry to hear that you've been having such a tough time. Thank you for sharing this thoughtful and inspiring post. So many valuable lessons in there for all of us. Irrespective of our own health status.
Giant hugs and huge respect. x
Giant hugs and huge respect. x
@magicspon @Netlify It could be that you've somehow got 2 webhooks firing the build.
In your admin, take a look in your Deploy Settings at the Build Hooks
(https://app.netlify.com/sites/{your-site}/settings/deploys#build-hooks)
In your admin, take a look in your Deploy Settings at the Build Hooks
(https://app.netlify.com/sites/{your-site}/settings/deploys#build-hooks)
@Jack_Franklin @Netlify You should probably read further down in the ToS. "An ice cream for Phil" is in there somewhere.