• hawksworx
  • blog
  • speaking
  • about
  • search

Notes - page 1280

  • Newest
  • Previous
  • Next
  • Oldest

The archive of what I posted on Twitter, which I now self host due to a lack of trust in Twitter and some other reasons.

I'll soon begin refelcting all my Mastodon posts here too. I'm happier self-hosting or maintaining an archive of my content on URLs that I can own.

There are tools to help you do this too. Such as this one from the makers of Eleventy.

A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 19th 2019 replying to this from @LucP
@LucP Thanks! And agreed, still relevant. But also, look how the CMS industry has evolved since then. In particular the growth in decoupled/headless products. This direction gives me some hope.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 19th 2019 replying to this from @atelierschork
@atelierschork * looks around office for hidden camera *
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 19th 2019
Walking around with my chest puffed out and a spring in my step after getting a complement about a talk I gave 7 years ago. (The fact that it is remembered at all, let alone some of its messages, makes me rather happy) https://twitter.com/asinnema/status/1097593641416212482
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 19th 2019 replying to this from @elliotjaystocks
@elliotjaystocks @kaibrach @Netlify Well, @Netlify does not operate its own data centres. It is built to be agnostic to the underlying cloud provider for reasons of resiliency, redundancy and performance. It spans 7 difference cloud providers each of whom will have their own policies on this.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 18th 2019 replying to this from @peduarte
@peduarte @ohadpr @Netlify I did indeed. You can also use @zapier which has an official @Netlify integration.

https://zapier.com/apps/netlify/integrations
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 18th 2019 replying to this from @asinnema
@asinnema Wow, 2012!
Interesting to see how little my slide design has changed in that time!

(I’ve found my font and I’m sticking to it!)
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 18th 2019 replying to this from @Darren_M
@Darren_M @Netlify You get that abstraction automatically since neither your hosted site on @Netlify, nor @netlifyCMS have moving parts on any server. They are served statically from a global CDN and the CMS talks directly to GitHub APIs from the client. In this model... there is no server.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 18th 2019 replying to this from @philhawksworth
@SlvrEagle23 @Netlify Curious to learn what regular site collaboration tasks you are struggling to satisfy. I'd hate for a FOSS project to be stifled by our free tier if there are existing usage patterns which might satisfy your needs.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 18th 2019 replying to this from @BusterNeece
@SlvrEagle23 @Netlify I'm a bit surprised by this. Most can manage collaboration in the git repo for a site rather than in the Netlify admin. You can have projects with hundreds of collaborators discussing, managing and deploying to a site via github. Many large projects do so with us for free.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 18th 2019 replying to this from @overflowhidden
@overflowhidden @Netlify Aha!
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 18th 2019 replying to this from @overflowhidden
@overflowhidden @Netlify I don't quite follow how this is related to NPM, but if you want run some tasks after a deploy has completed, you could use a serverless function.

Netlify Functions can be triggered by events. Like a successful (or failed) deploy.

https://www.netlify.com/docs/functions/#event-triggered-functions
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 18th 2019
Delighted to be a part of this event!
It will be full of wonderful people. I can't wait! https://twitter.com/upfrontconf/status/1097437224826793986
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 18th 2019 replying to this from @Mandy_Kerr
@Mandy_Kerr @Netlify
Embedded image from social media
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 18th 2019 replying to this from @overflowhidden
@overflowhidden @Netlify How do you mean?
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 18th 2019 replying to this from @notrab
@notrab @Netlify You're starting to sound like Meatloaf.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 18th 2019
I've always been proud of the @Netlify docs.

We'd love it if you'd help us to make them even better. And to keep them easy to use as our product continues to grow. https://twitter.com/Netlify/status/1097430776499658752
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 17th 2019 replying to this from @JJTheNYJetPlane
@JJTheNYJetPlane How odd. Nothing reported here. Glad you are up and running now.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 17th 2019 replying to this from @owenconti
@owenconti @Netlify You bet. Good luck!
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 17th 2019 replying to this from @owenconti
@owenconti @Netlify You could remove the hook from your repo. And yes, you can add as many build hooks as you like. Or you could call put directly to the API.

https://www.netlify.com/docs/api/#deploying-to-netlify
Embedded image from social media
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 17th 2019 replying to this from @JJTheNYJetPlane
@JJTheNYJetPlane If issues continue, I'd recommend contacting support@netlify.com.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 17th 2019 replying to this from @owenconti
@owenconti @Netlify You can turn auto publishing off from your deploys page.
Embedded image from social media
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 17th 2019 replying to this from @therealdanvega
@therealdanvega @gamesover @Netlify With @Netlify you could use the Redirects API to return any http code you like for any urls or patterns.

Perhaps http 410 is what you need.

/this-path-is-gone/* /gone.html 410

https://www.netlify.com/docs/redirects/#http-status-codes
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 16th 2019
TOUGH DAY AT THE @NETLIFY OFFICE https://t.co/bpNkksbAxy
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 16th 2019 replying to this from @mikesherov
@mikesherov @zachleat Eagerly awaiting that.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 15th 2019 replying to this from @borisrorsvort
@borisrorsvort @Netlify Thanks for advocating for this!
I agree. A valuable resource for education.

I'm sure we can help. Can you please contact our support team so that they can help figure this out?

👉 support@netlify.com
  • Permalink
  • |
  • Twitter
  • Newest
  • Previous
  • Next
  • Oldest

The source code of this site is available on GitHub and is hosted and updated by Netlify automatically after each code commit

Other than where specified, the content on this site is published under a Creative Commons Attribution 3.0 licence.

Subscribe to a feed of blog posts on this site.