DEV Community: Markus

gyp: No Xcode or CLT version detected! 👈 I think I know why this happens

Markus — Wed, 01 Apr 2020 07:10:20 +0000

👉 Are you a user of Xcode CLT only, not the full Xcode?

👉 Have you run into the gyp: No Xcode or CLT version detected! error?

👉 Did you solve it by sudo rm -r -f /Library/Developer/CommandLineTools and then re-installing it with xcode-select --install, only to inexplicably run into the exact same error a while later?

Here's the kicker...

👉👉 Are you a user of a Node version manager like asdf or nvm? 👈👈

I've been in this position a number of times in the last few months and I could never understand why it kept cropping up. But I think I've discovered why I continually, and intermittently had this issue.

I was working on a few older projects using Node 8. I wrapped one up yesterday and moved to a new React project this morning and so I nvm use 12.15 and ran npm i

gyp: No Xcode or CLT version detected!

😔

So I begrudgingly deleted Xcode CLT and re-installed and everything worked fine. And then it clicked.

I think `xcode-select --install` attaches itself to the node version you have installed at the time

So you fix the problem, and then, later on, run into it again when you switch to a different version of Node.

Haven't tested this thoroughly... who has the time. But would love to hear if this resonates with anyone else and maybe this is actually the case?

A headless & more secure WordPress install with Bedrock

Markus — Mon, 17 Feb 2020 11:40:49 +0000

The foundations of WordPress (WP) haven't changed much in a long time. Sure Gutenberg has changed a lot of things on the frontend, but not much has changed in the way you setup + install WordPress. This predictability is great for their famous 5-minute install, but their lack of support for package tools like Composer, is sorely missed by developers these days.

Enter Bedrock

What is Bedrock? Well if you'd asked me a year ago, I'd have said a really killer rave track from the '90s. But more recently, to me, Bedrock is the new defacto boilerplate for working with WordPress.

Bedrock is a project by Roots that in short,

Improves the WordPress folder structure
Adds full Composer support for dependency management
Supports multi-stage environments through Dotenv
Enhances security by moving the WP core outside of the web root, and by making use of bcrypt hashed passwords instead of MD5.

Installation

Installation is pretty complex. Bare with me...

composer create-project roots/bedrock

Did you survive that ordeal? 😉

This will download Bedrock and install a few core dependencies via Composer. Once that's done, open your folder in your editor of choice and you'll see an .env file ready for editing. Update all the things and then you should be good to go.

A few things to note:

Your 'root' is now the ./web/ folder. Things here will look a little different, as Bedrock cleverly abstracts everything into new locations.
Because of this new location, you'll need to set up your MAMP root to be this folder, not the project root. Otherwise, if you're using nginx, set your root to be this folder.
Everything you're looking for - themes, plugins, uploads, etc - can be found in ./web/app.

Nice.

PSA: Here's a simple repo with Docker baked into it, that you can use for local development. I'm new to Docker, so this might not be a perfect solution, but I use it regularly for my projects and so far, so good.

Plugins

There are a few plugins we'll be using to manage our website's content. Thanks to the joys of Bedrock, we can use Composer to install these:

composer require wpackagist-plugin/advanced-custom-fields
composer require wpackagist-plugin/acf-to-rest-api

Advanced Custom Fields requires no introduction. ACF-to-REST API, simply takes all your ACF data and dumps it into an acf object within your REST data. So for example, if you have a field called sub_title, this will be available in mypost.acf.sub_title.

Lovely.

Theme

Our site is gonna be a 'headless' site, so we don't require a theme. We will, however, be adding a few bits & pieces of custom code to extend some REST endpoints, so for that, we can create the bare minimum of a WordPress theme:

Simply make a folder ./web/app/themes/my-rest-site (or whatever you want to call it) and add an index.php, functions.php and style.css.

We'll circle back to this later as we get to step 2.

And that's that. You now have a Bedrock-powered WordPress site that's ready to be used as our CMS for our Gatsby site.

Have you used Bedrock before? Do you have any tips for how you've made it work for your projects? I'm keen to hear all about it in the comments below.

Next up, we'll be covering how to add custom data into our REST endpoint, and how to use WPGraphQL to graphql-ify our site.

Finding joy in WordPress again, with React, Gatsby & GraphQL

Markus — Tue, 26 Nov 2019 06:07:27 +0000

I've worked with WordPress for over 10 years. It's a great platform, and there's no doubt that its come a long way and progressed from a simple blog publishing platform, to a more of a CMS (albeit through the addition of some incredible plugins).

But the way that Automattic steam-rolled the community into adopting Gutenberg, combined with me being bored with WordPress and wanting a new challenge, led to me giving up on the platform and moving onto other things.

Fast-forward 7 months and my new employer tasked me with a WordPress project (meh), but suggested we give Gatsby a try (huzzah). It's only been a couple weeks now, but I'm finding renewed joy and enthusiasm for the stack.

Here's why.

1. It keeps clients happy.

Inspite of it being arguably out-performed by other systems like Laravel or Directus, WordPress is still a great platform. And because of how mainstream it is, it's familiar to end-users and they're comfortable with it.

2. It keeps you happy.

Stands to reason that if you're working with a fun stack, you're going to enjoy your job more. The combination of WordPress, React, Gatsby and GraphQL is just that - fun.

Over the next couple weeks I will be creating some content around some libraries, tips & tricks, methodologies and systems that I've put to use in this site build, and that have made work fun again.

You can look forward to:

A headless & more secure WordPress install with Bedrock
Extending the REST-API to extract the most from your CMS
Setting up your front-end with Gatsby
Understanding how Gatsby uses WordPress to 'build itself'
Learning some key GraphQL queries to extract what you need
Swapping WordPress plugins, with Gatsby plugins, to do things like:
- Form handling
- SEO & XML sitemaps
- Image optimisation
- and more...
Deploying a Gatsby site, and triggering builds with WordPress webhooks

Join me on this journey, as I make WordPress development fun again.

PS: This post will be updated with links to the other posts in this series, as they are written.

200+ Crypto Currency Logo's in SVG Format

Markus — Tue, 07 Aug 2018 07:01:36 +0000

Thought this might be useful to some folks here. Collected by the awesome @rebellenoire, these are all/most of the current Crypto Currency logos, in SVG format.

https://github.com/wondergryphon/cryptocurrency-logos

Busy building this resource into a site - kind of like iconmonster.com - to make them searchable & more easily usable. Probably also an npm module too... Watch this space 😉

(PS: This is my first time maintaining something like this. Would love some feedback on any ways I can make it better.)

How do you look after your circulation?

Markus — Fri, 19 May 2017 08:21:50 +0000

Right leg crossed over left, or left over right. Or perhaps right leg under left, or left under right.

â˜ï¸ I cycle through the above configurations and more, probably 50 times a day. But still, lately I'm finding that I get pins and needles more often, and for longer periods.

How do you guys find you look after your circulation when sitting for so long?

I've been thinking of getting a bench or 'ledge' to put at my feet to rest with my legs up, instead of tucking them under me or something.

I have a 3 monitor setup, so setting up a standing desk would be impractical.

I'd love some suggestions/thoughts for how others deal with this occupational hazard :)

Hi, I'm Mark

Markus — Fri, 19 May 2017 08:13:25 +0000

I have been coding for 13 years.

You can find me on Twitter as @wondergryphon

I live in Cape Town.

I mostly program in these languages: PHP, Javascript.

I am currently learning more about Javascript.

Nice to meet you.