Open ubuntupunk opened 4 months ago
The quick fix is to remove the section of config.yml
telling it to run composer create project for that site.
Otherwise there's now an open problem of how to ensure you can repeatedly run composer create-project
and not have it exit the second time round reporting it's already been created.
Note that the example you're following for using Craft CMS is speculative, it isn't the canonical method of using Craft CMS ( no canonical method exists )
Are you using the latest stable or develop branch version of VVV?
Yes (stable)
Is it a new VVV, or an existing VVV that used to work?
Existing, worked but now broken
Did you use a CustomFile?
No (default)
Whats the problem?
How do we reproduce it?
Install Craft according to instructions provided. Enable site. Then reload vagrant with provisioning. The provisioner will fail because installation exists. Needs some logic, if site exists, composer only update changes.
What is the output of
vagrant status
Which Operating System are you using?
Linux
Which provider are you using?
VirtualBox 6