wp-cli | ⚙️ WP-CLI framework | Command Line Interface library

Is apache running?

You must also spoof your DNS to point to your local ip, so your machine does not ask internet dns servers for an ip, which they would not be able to find.

I'm assuming you're on mac, so edit /etc/hosts and add:

You are going to need to do a manual update.

Download the current/or version you need and once you’ve downloaded it, extract the zip file to your computer. Then, open the folder that contains all of the WordPress files and delete the following items:

• The wp-config-sample.php file.

• The wp-config.php file (you might not see this file – just make sure to delete it if it’s there). The wp-content folder.

• Once you’ve deleted those items, upload the remaining files/folders to your server via FTP. When prompted about duplicate files by your FTP client, tell it to overwrite all files:

If there is no package for Sass (and it makes sense there wouldn't be, unless sass could be installed as a stand-alone binary or something like that), you cannot install Sass as a composer dependency

Which in any case wouldn't make much sense, since Sass cannot be a dependency for a PHP project, as it has nothing to do with PHP.

Alternately, how could I install the latest version of SASS cross-OS via a script that Composer runs using post-install-cmd?

The install instructions for Sass include no provisions for a "cross OS installer without using npm". So unles you write a script checking for the OS, what does it have installed, etc (which would be brittle and some serious overkill), you cannot automate this with a post-install-cmd.

Which again, wouldn't make a lot of sense in any case. If the package consumers need to use sass part of the project, it's a given they are developers and are capable of going through the sass requirements.

Point your package consumers to the appropriate documentation and be done.

I have tried to install https://openbase.com/js/@myrotvorets/po2json using:

You may need to have a detail look for multi-stage build.

With multi-stage builds, you use multiple FROM statements in your Dockerfile. Each FROM instruction can use a different base, and each of them begins a new stage of the build. You can selectively copy artifacts from one stage to another, leaving behind everything you don’t want in the final image. To show how this works, let’s adapt the Dockerfile from the previous section to use multi-stage builds.

Above means, unless you explicitly copy things from previous stage to next stage, the items in previous stage won't be seen in next stage. For you, when you define the FROM php:7.3, this means your final image will be based on php:7.3, has non business with wordpress.

For next you got:

mz-docker-dev_wordpress_1 docker-php-entrypoint php -a Exit 0

This is because the php:7.3's entrypoint is "docker-php-entrypoint", the container will exit directly after run the entrypoint if no foreground process there.

So, for you, just remove FROM php:7.3, base on wordpress image to do your customized works is the solution.

I found it: With xargs, using the -n1 switch to take max. 1 argument at a time:

I have solved it, 3 things were overlapping hence the confusion:

1. The list of custom providers printed by wp-cli seems not to print custom added providers, so it was confusing my debugging
2. As some pointed out it the comments, my regex was not properly written (thanks)
3. I had an extra / at the end of my test url, which was making the oembed provider crash, and the error returned by wordpress was 'oembed_invalid_url', I didn't see it

I found the problem it was the hook below: