It must be hard for hosting support to have to deal with front-end folks like me, who just about get by on the command line but rapidly glaze over when confronted with

“just /usr/local/bin… ”

And it must be hard when I’m merely one of many clamouring for their attention.

But nevertheless, it would be great if knowledge was not assumed, and some explanation was provided of wtf their opaque incantations mean

…So I’m in a sitch where I’m trying to get an instance of #CraftCMS running.

- I understand that Craft uses Composer as its package manager, but to be honest my understanding doesn’t go much further.
- I don’t understand *when* it needs to run and when it doesn’t or why.
- I have a hosting context which *for reasons* are on a lower version of PHP than the version Craft needs
- There is apparently a way to tell Composer to use the version Craft needs…

…I presume this is a one-time thing until such time as Craft itself needs to be updated again 🤷‍♂️

Bottom line is, when hosting contexts work, I can do all kinds of stuff. Happy days!

But when they don’t, one rapidly enters a context in which one is just expected to know stuff that nobody bothers to explain :/

…My persistent disquiet in the world of the command line is assumed understanding.

‘Just’ run

/floozal/squiddly/v875.ph/wonkdongle

…and all will be fine

…One of the more annoying traits in support tickets goes something like this:

- I frame a context
- I ask specific questions about that context (I’m trying to learn)

What I get back is:

- My questions are ignored
- They ask me a question that assumes I understand a context which I’ve just demonstrated I don’t

*Meet the customer where they actually are, people*

…tbh I see this play out a lot on Mastodon with Linux people.

I do understand that there is a domain of complexity that sometimes can’t be just skated over, and sometimes there is a strong incentive to merely relay the incantations.

But there is an underlying whiff of *not listening* or arrogance to it. I’m sure that’s not intended most of the time, but that is often how it lands

@urlyman

You forgot the '-iCa --check' options though.