Closed Luc45 closed 7 months ago
I also got this when trying to bring up the env:
My qit-env.yml
file is the example included in the description:
plugins:
- gutenberg
- wp-staging
themes:
- storefront
Made sure I ran a make build
so I'd be on the latest here, too.
I also got this when trying to bring up the env:
What backend are you connected to? Point it to prod, please
If you want to use local
, you'd have to:
trunk
in the Managermake enter
on the Managerwp cd env update
qit sync
This would force it to fetch the latest environment from upstream jfyi. But switching to prod is the easiest.
What backend are you connected to? Point it to prod, please
Hm yeah I was connected to prod:
This PR does some final tweaks for the local test env:
woocommerce_version
parameter fromenv:up
(We'll handle it at Woo Custom Tests bootstrap process instead)requires
can be used in config filesThis PR is complemented by the documentation PR on the Docs repo.
Testing Instructions
Testing shortcuts
Create a config file, eg: qit-env.yml
qit env:up
and assert it installs it as expected.qit env:up
again and override the plugins with the full option name, eg:qit env:up --plugins contact-form-7
]contact-form-7
is installed.qit env:up -p contact-form-7
and assert the same behavior.Testing Custom Handlers
This one is a bit trickier to test.
Place this
qit-env.yml
file on your dir:Create these 3 files below, run
qit env:up -vvv
and assert that it downloaded the custom plugins from custom sources. Public/private handlers will download from a public/private GH repos, and advanced handler will download from a private repo, build it, and cache the build. It will only rebuild if the repo changes on the remote.I have granted @zhongruige and @MrJnrman access to the private repos needed for this test, just accept the invitation please.
public-handler.php
private-handler.php
advanced-handler.php