0.5.13

Changed

• Executing tric use without a target now attempts to set the current working directory as the target.
• tric info now outputs all valid targets, which is what tric use without a valid target used to do.
• The Composer prompt from tric init no longer appears if composer.json is not found, likewise for the NPM prompt if package.json is not found.
• Fixed an issue that would prevent the npm and npm_lts services from correctly returning their exit status.
• Add support for the --pretty flag to the npm and npm_lts commands to print a more human-readable output.

0.5.12

Changed

• Fixed two issues in the target command where the command would fail if no previous target had been set.
• Set the start of the random network subnet pool for parallel processes used by the target command to a higher number to reduce the chance of running into overlapping pool issues.

0.5.11

Changed

• Activate all debug options in the wordpress service.
• Use a custom WordPress image for the stack, based on the default wordpress one, but modified to support and use XDebug.

0.5.10

Changed

• Fixed a smaller issue in the command.

0.5.9

Changed

• Add the site-cli command to start a wp-cli container on a running and ready WordPress stack.

0.5.7

Changed

• Add the npm_lts service and service to the stack to run npm commands on the current LTS version of node.

0.5.6

Changed

• Fixed an issue where the terminal columns and lines detection would cause issues in CI context.
• Fixed an issue where the npm image would not build correctly in CI context.

0.5.5

Changed

• Add support for the bash sub-command to the tric cli command to allow opening a bash shell into the cli container to manage the WordPress installation currently being served by tric serve.

0.5.4

Changed

• Add support for multiple commands in the target command to allow running a set of commands on a set of targets.

0.5.3

Changed

• Update the WordPress version used in the stack to 5.5.
• Fix handling of default answers in prompts.