• hawksworx
  • blog
  • speaking
  • about
  • search

Notes - page 426

  • 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 20th 2018 replying to this from @JonTheGeek
@JonTheGeek @Netlify Great. Pleased to hear all is well.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 20th 2018 replying to this from @JonTheGeek
@JonTheGeek @Netlify Not at all. I know the feeling.
That old traditional saying: "A watched DNS update never propagates"
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 20th 2018 replying to this from @JonTheGeek
@JonTheGeek @Netlify Waiting for DNS is the worst!
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 20th 2018 replying to this from @JonTheGeek
@JonTheGeek @Netlify Yikes! I've not seen that.

Did you make a recent change to your DNS to move your domain over? Very often issues like this are down to DNS propagation still happening. I'm seeing a successful site load FWIW.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 20th 2018 replying to this from @JonTheGeek
@JonTheGeek @Netlify The site looks good to me on either domain... but I do see (via dev tools) that there are all sorts of tracking codes and js requests happening. Seemingly from Disqus and the embedded Twitter view.

What was the error you saw? A complete failure or a partial load?
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 20th 2018 replying to this from @ChrisFerdinandi
@ChrisFerdinandi I was pondering just that! Let me go through the form and double check the theme. Could be great!
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 20th 2018 replying to this from @peduarte
@peduarte @Netlify Yyyyes!
Oi oi!
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 20th 2018 replying to this from @patrick_h_lauke
@patrick_h_lauke It would be spinning by default.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 20th 2018 replying to this from @now_maciej
@nowakowskipl @Netlify Ah... perhaps it is the routing... the CDN will be trying to find an asset on that paths, but with a SPA the path does not exist... I think the redirect settings will be what you need to tweak:

https://www.netlify.com/docs/redirects/#history-pushstate-and-single-page-apps
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 20th 2018
When a conference digitally enhances you with a fancy 8-bit bow tie, it raises sartorial questions. https://twitter.com/coldfrontconf/status/965881463089479680
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 20th 2018 replying to this from @coldfrontconf
@coldfrontconf @Netlify Sartorial decisions:
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 20th 2018 replying to this from @now_maciej
@nowakowskipl @Netlify The route works via the link on your home page. Could this be a client-side SPA which does not have all of the routes pre-rendered as valid entry points? Do you get different behavior locally?

@Netlify can help with pre-rendering: https://www.netlify.com/docs/prerendering/
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 19th 2018
Very excited to be returning to Copenhagen for @coldfrontconf again later this year. Its quality talks, friendly atmosphere, and great organisation have made it a firm favourite for me.

And there is a call for recommendations now open. Who do you want to see give a talk? https://twitter.com/coldfrontconf/status/963322097979109376
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 19th 2018 replying to this from @jamchiller
@jamchiller @Netlify Nice.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 17th 2018 replying to this from @gedaly
@Gedaly @Netlify Yes indeed! Once the redirects are deployed they should be very fast as they happen at the CDN. Not sure what a sensible max number of entries might be though.

I made a simple example which generates your redirects automatically:

https://github.com/philhawksworth/linkylinky
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 17th 2018
RT @thenewdynamic: 🔥 “Build Better Faster Websites: the New Dynamic 02/17 links and showcase” http://newsletter.thenewdynamic.org/archive/96681 with @philhawksworth…
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 17th 2018 replying to this from @
@m1sp @Kikobeats @Netlify And @ddprrt wrote a great article on how you can use Wordpress as a back-end and get content from its API into a #JAMstack build.

https://fettblog.eu/wordpress-and-jamstack-sites/
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 16th 2018 replying to this from @philhawksworth
@bdougieYO @Netlify @github or good luck.
Whatever. Too upset to sepllcheck.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 16th 2018 replying to this from @bdougieYO
@bdougieYO @Netlify I can't believe that day is already here. Legend!
I hope @github know how lucky they are. Good look BeeeDougie!
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 16th 2018 replying to this from @philhawksworth
@JordanHawker @Netlify Depending on how your site is built, this might be the information you're looking for:

https://www.netlify.com/docs/redirects/#history-pushstate-and-single-page-apps
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 16th 2018 replying to this from @AxleHellfire
@JordanHawker @Netlify Ack! I'm an idiot. I didn't spot that Intercom is for those on the paid plan. Best direct support contact without that is https://www.netlify.com/support/. Sorry for adding confusion there!

Meanwhile I'm afraid I don't quite understand the expected and actual behaviors you get
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 16th 2018 replying to this from @AxleHellfire
@JordanHawker @Netlify Hi Jordan. Would you mind asking this to support via the little intercom chat thing-a-mi-bob in https://app.netlify.com? That way the team can see your build/settings and diagnose things far more easily.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 16th 2018 replying to this from @chrisbiscardi
@chrisbiscardi @Netlify 👍
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 16th 2018 replying to this from @toddhalfpenny
@toddhalfpenny 1.5p
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 16th 2018 replying to this from @chrisbiscardi
@chrisbiscardi @Netlify Folders in your site will form the path on your site (so, yes... if I'm understanding your second example correctly).

You can also have different branches in your repo drive different subdomains domains.

Docs for that here: https://www.netlify.com/docs/custom-domains/#branch-subdomains
  • 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.