trellis new command doesn't create the wp folder

trellis
1

Hi, I’m seeing an issue where the command trellis new foobar.com doesn’t generate the wp folder:

├── foobar.com
│ ├── site
│ │ ├── composer.json
│ │ ├── composer.lock
│ │ ├── config
│ │ │ ├── application.php
│ │ │ └── environments
│ │ │ ├── development.php
│ │ │ └── staging.php
│ │ ├── LICENSE.md
│ │ ├── pint.json
│ │ ├── README.md
│ │ ├── web
│ │ │ ├── app
│ │ │ │ ├── mu-plugins
│ │ │ │ │ └── bedrock-autoloader.php
│ │ │ │ ├── plugins
│ │ │ │ ├── themes
│ │ │ │ └── uploads
│ │ │ ├── index.php
│ │ │ └── wp-config.php
│ │ └── wp-cli.yml

Is that to be expected? I’m new to this but the docs say that folder should be created next to app from the start.

Thanks for your help.

EDIT: removed unnecessary information.

2

The wp folder is created when the composer install task runs during the provisioning of your development VM

Did you see any errors when you tried to start your machine for the first time?

3

Hi @ben, I’ve just tried it again after re-installing Homebrew yesterday (I also had to remove lima and limactl from /usr/local/bin as per this Github comment, seems they are used first and will still hang around after you migrate from Mac Intel to Silicon).

The VM install took a long time (10 minutes on my M2) with no errors but a couple of warnings:

[WARNING]: Skipping plugin (/Users/jackfaulkner_1/Development/example.com/trellis/lib/trellis/plugins/vars/version.py), cannot load: No module named ‘distutils’

[WARNING]: Platform linux on host default is using the discovered Python interpreter at /usr/bin/python3.12, but future installation of another Python interpreter could change the meaning of that path.

It seemed to complete successfully and I can see the wp folder has been created after this step. The site is available at foobar.test. Thanks for your help!

1 Like