Rest in Peace Chris Moore

One thing you can always do to ensure justice

to assure you’re doing good

Capital “G”, Good

…is to always try to come back to something you love daily,

and to try to make it better

just a little bit better, a little more helpful

a little less heavy with mistakes

a little bit better focused.


Chris Moore was one of the hosts of a podcast called “Barbell Shrugged”. That podcast continues to this day.

The quote from him above is from what I believe to be his final podcast. Those words are fitting and inspirational and speak to where he believed to be headed.

Whatever I could write about Chris, especially in this post, pales in comparison to anything he could or would have written or said.

Still, lacking as it might be, I feel compelled to write something.

Maybe though, we start with his latest goal for his communication,

Iron Heart Studios is a media company committed to rich, responsible and resonating story-telling.

Iron Heart comes from a desire to be strong in mind, body, character and purpose. The beating heart of our company is the drive to impact peoples lives in positive ways. To help them utilise their strength to shape life, family, community and landscape. To be a force for good in this world.

Iron Heart’s essential purpose is to be a vehicle for that message, and turn those sparks of light into bright beacons for all to see. We’re here to communicate the stories that will inspire you to become strong and use that strength to do something positive…something heroic.

In 2015, as I began a journey into Muay Thai and strength training, I discovered the hosts of Barbell Shrugged (Chris, Mike and Doug), and were amused, entertained and educated by their podcast. Episodes could range from very serious, philosophical episodes with the CEO of Eleiko (“Do More of What Makes You Stronger“) to the bordering on “Beavis and Butthead” episode called “How To Add Mass To Dat Ass“. And point well taken, that latter episode was excellent, and begins with Chris.

While surfing YouTube early one morning, I was shocked to see this:

Screen Shot 2016-07-02 at 5.16.31 PM


Although I didn’t know Chris, and had no personal interaction with him, his untimely passing was quite upsetting. Judging by the posts of many others who had exactly the same interaction (meaning consumers of his podcast), they too were impacted. After a year (for me) or years (for others) of listening to Chris, there is a void with his passing that will be difficult, if not impossible, to fill.

Chris, to me, embodies Warrior-Philosopher. He both takes action and is reflective. That seems increasingly rare, and likely has always been rare. And the world is a much lesser place without him.

Here is a wonderful picture from his Barbell Buddha site.

Screen Shot 2016-07-02 at 5.10.06 PM.png

Rather than straining your eyes:

  1. Just Start!
  2. Be consistent
  3. Be Positive
  4. Think about it
  5. Practice being Grateful
  6. Acknowledge names & Places
  7. Create Meaning / New identity / New narrative

Chris also had another podcast called “Barbell Buddha”. Those podcasts were both more serious and felt very personal, almost as if you were sitting in Chris’ den with a drink of choice (coffee, tea or wine) just listening. They may have been a little less edited too. It gave one a feeling of having a personal conversation with Chris.

We often lament how impersonal the Web is. I disagree. It’s not as if sitting in a coffee shop chatting with a friend about the weather makes for a deeply personal connection.

Be humble and relinquish all desires.

Instead, give all you have with love

and life will surely deliver all its possibilities in abundance.




AWS – Deploy a Static Website to S3 using the CLI

(This article assumes a folder with existing code for the website on your local machine. )

The steps are:

  1. (Optional) If the bucket already exists, remove it using rb.
  2. Create the bucket using mb.
  3. Recursively copy the local web files to the target using cp.
  4. Instruct S3 to treat the bucket as a static website.
  5. Apply the policy to the bucket.

Since I’ve already run through this particular exercise, I need to delete the existing bucket using the rb (“remove bucket”) command with –force to delete a bucket full of resources as evidenced below.

Screen Shot 2016-07-01 at 3.48.54 PM

rb is a little dangerous since someone else could snap up the name I want to use, but for the purposes of demonstration, this is fine.

aws s3 rb s3://gma-web --force

If we executed aws s3 ls here, we would see that gma-web no longer exists. For now, we’ll go ahead and create the bucket.

aws s3 mb s3://gma-web

As a sanity check, ls the new bucket. No files will display since our newly created bucket is empty.

aws s3 ls s3://gma-web

Copy the code using cp with –recursive.

aws s3 cp gma_v1 s3://gma-web --recursive

Since we want our bucket to behave like a static website, we need to inform S3 of this.

aws s3 website s3://gma-web/ --index-document index.html --error-document error.html

As with many things UNIX, no news is good news if our prompt returns with no message.

Users will get a 403 error when navigating our site, so we need to apply a policy letting them in.

To create the Policy, I simply used nano to create a file called policy.json with the following contents. Except for gma-web shown below, everything else is fairly standard.

	  "Principal": "*",

While it may be tempting to change the “Version” to the current date, AWS will return an error if you do so.

To put the policy in place: [Source]

aws s3api put-bucket-policy --bucket gma-web --policy file://policy.json

Subsequent updates can be as simple as:

aws s3 cp index.html s3://gma-web

And now our sample site renders just fine.

Screen Shot 2016-07-01 at 4.20.58 PM