• hawksworx
  • blog
  • speaking
  • about
  • search

Notes - page 114

  • 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 • April 1st 2021 replying to this from @icesofty
@icesofty @Netlify @cassidoo Ball significantly dropped on the name, though. Livid.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • April 1st 2021
"Anonymous sources" my arse.

Naming portmantopportunity missed :(

https://twitter.com/Netlify/status/1377548900651925504
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 25th 2021 replying to this from @philhawksworth
@michaelpumo @Netlify (funky site too!)
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 25th 2021 replying to this from @michaelpumo
@michaelpumo @Netlify Looking good for me, @michaelpumo.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 25th 2021 replying to this from @toddmorey
@toddmorey ❤️
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021 replying to this from @iChris
@iChris @Nike Perfect. I’ll book the sign-writer.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021 replying to this from @DavidDarnes
@DavidDarnes Much brand!
Very wow!
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021 replying to this from @iChris
@iChris @Nike Yachty McYachtface is still up for grabs though.

Veering away from Shippy McShipface for reasons of reasons of vocal clarity
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021 replying to this from @iChris
@iChris @Nike All I have to worry about now is what to name my new yachts
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021
That collaboration with @Nike might have been difficult to coordinate ...but it was worth it. https://twitter.com/andyshora/status/1374343222932217860
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021 replying to this from @Netlify
@Netlify https://twitter.com/philhawksworth/status/1374341682993491969?s=20
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021 replying to this from @philhawksworth
I started leaning on @Netlify's CI/CD for this as soon as I discovered it. (Disclaimer — then I joined them. That's how much I was taken by it)

You can explore more about Netlify Build and the other things it can do (*cough*, *cough*... time travel!)

👇

https://url.netlify.com/rJ3LHP8V_
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021 replying to this from @philhawksworth
...and since branch deploys all have the same performance characteristics of your production branch, you can even use branches as the source of different user experiences in A/B or multi-variant testing.

https://url.netlify.com/S18l3LDVu
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021 replying to this from @philhawksworth
If you have a custom domain, you can use your branch name as a subdomain

https://url.netlify.com/HkmY9UPNO
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021 replying to this from @philhawksworth
💥 Kapow!

Now you have multiple environments, each with their own CI/CD workflow based on git.

And you can do this as many times as you like. Unlimited instant environments FTW! 🎉
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021 replying to this from @philhawksworth
Branch Deploys are how @Netlify delivers multiple environments.

For example, to create a staging environment, you create a branch called "staging" and push it to your repo. Netlify runs your build just like normal, but deploys it to a URL called "http://staging--yoursite.netlify.app"
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021 replying to this from @philhawksworth
...and away goes the headache of synchronising all of the software, patches and configuration of servers before getting to work on the code and content.

(which is where, as designers and developers, we do our real work!)
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021 replying to this from @philhawksworth
..."production" and "staging" environments can be on identical, globally distributed infrastructure, each with their own URL and workflow.

Gone are the days of pricing up servers and resources to host each environment for a site.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021 replying to this from @philhawksworth
...this opens the door to automating the provisioning of environments.

Instead of creating "new" environments, we can deploy sandboxed instances to the same big network of infra to be operated by experts in that field.

Those experts don't need expertise in "our" special sauce.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021 replying to this from @philhawksworth
...and what are atomic deploys?
https://jamstack.org/glossary/atomic/
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021 replying to this from @philhawksworth
...also this allows the hosting strategies of the sites to be normalised. The important practices and workflows for hosting such things can be common, like CDN hosting, edge caching, cache-management, atomic deploys.

What is a CDN?
https://jamstack.org/glossary/cdn/
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021 replying to this from @philhawksworth
A Jamstack approach decouples the front-end from the back-end and from the infrastructure.

It is no longer confined to being the output of a back-end system. (A win for those with skills in front-end engineering who can now work outside of the constraints of the back-end.)
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021 replying to this from @philhawksworth
This is one reason I embraced a hosting model with immutable deploys instead of a constant iterative mutation of environments, their config, and their code.

What is an immutable deploy?

https://jamstack.org/glossary/immutable/
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021 replying to this from @philhawksworth
I wonder, have you ever:

- Made a project plan for a deploy/release?
- Had a long code/content freeze during a deploy?
- Costed a "deploy team"?
- Been on call or worked nights for a deploy or env migration?

(😬 Past Phil is nodding at me. I'm trying not to make eye contact!)
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • March 23rd 2021 replying to this from @philhawksworth
...most of my life leading projects had me losing sleep over these things. With only stress and no actual confidence gained from having multiple environments because they were so hard to reason about.
  • 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.