Does Local support non-standard WP site structure exports?

EDIT: Just wanted to mention that I’ve looked into adjusting the path in /wp-cli.yml as mentioned in WP-CLI error: Pass --path=`path/to/wordpress`, but this didn’t seem to help. Either that isn’t the fix, or it just can’t read our path properly.

EDIT: After looking into some options like creating a .env.cli file, I was able to get it to a point where we wouldn’t see the “This does not seem to be a WordPress installation” error. Unfortunately, it outputs a corrupted .zip file, and when trying to import that file, we get the following errors in the logs:

2019-06-21T13:41:41.437Z - info: importSiteAnalyzeWorker: checkLocalExport
2019-06-21T13:41:41.437Z - info: Analyzing Zip: Listing Contents for Local Export Check
2019-06-21T13:41:41.438Z - debug: Analysis of zip: Local Export
2019-06-21T13:41:41.438Z - info: importSiteAnalyzeWorker: checkBackupBuddy
2019-06-21T13:41:41.439Z - info: importSiteAnalyzeWorker: checkGenericZip
2019-06-21T13:41:41.439Z - info: Analyzing Zip: Listing Contents for Generic Zip Check
Jun 21, 2019, 10:41 AM ADT - info: [renderer/ImportSiteAnalyzePage] Message from import-site-analyze-worker: {"type":"local-export"}
Jun 21, 2019, 10:41 AM ADT - warn: [main/index] Unhandled Rejection at: Promise  Promise {
  <rejected> { Error: EEXIST: file already exists, mkdir '/private/var/folders/4q/t3f5x0vn6glf5c114_tsbl_rkz8drq/T/local-by-flywheel-Q2sTfsBFsd/app/current'
    errno: -17,
    code: 'EEXIST',
    syscall: 'mkdir',
     '/private/var/folders/4q/t3f5x0vn6glf5c114_tsbl_rkz8drq/T/local-by-flywheel-Q2sTfsBFsd/app/current' } }  reason:  
{ message:
   'EEXIST: file already exists, mkdir \'/private/var/folders/4q/t3f5x0vn6glf5c114_tsbl_rkz8drq/T/local-by-flywheel-Q2sTfsBFsd/app/current\'',
   'Error: EEXIST: file already exists, mkdir \'/private/var/folders/4q/t3f5x0vn6glf5c114_tsbl_rkz8drq/T/local-by-flywheel-Q2sTfsBFsd/app/current\'',
  errno: -17,
  code: 'EEXIST',
  syscall: 'mkdir',
   '/private/var/folders/4q/t3f5x0vn6glf5c114_tsbl_rkz8drq/T/local-by-flywheel-Q2sTfsBFsd/app/current' }
Jun 21, 2019, 10:42 AM ADT - info: [main/docker-delete-site-container] Deleting Site Container 
{ name: 'testsiteexport', container: null }

So… slightly further along, but not really?

Hello! My team has been using Local for a few years now, and it’s been great for easily spinning up sites when we need to work on them. Our only real issue is we can’t seem to export and import them, which does seem to negate what appears to be a large benefit of the app.

Most of our sites are built upon a custom Bedrock ( folder structure, running on Apache, PHP 7.2, and MySQL 5.6. We can get our sites to function properly through Local, but they seem to fail at exporting/importing properly.

When running an export, after the “Compressing Files” process, we get the following error in the Local logs:

Jun 20, 2019, 2:26 PM ADT - warn: [main/SiteModel] wpInstalled not returning "installed" 
{ stdout: '',
   'Error: This does not seem to be a WordPress installation.\nPass --path=`path/to/wordpress` or run `wp core download`.' }

Our current site folder structures are generally as follows (from the site root):

├── app
│   ├── current -> releases/2019-06-18
│   ├── releases
│   │   └── 2019-06-18
│   │       ├── config
│   │       │   └── environments
│   │       ├── vendor
│   │       └── web
│   │           ├── app ------------------------> (Themes, plugins, etc.)
│   │           └── wp ------------------------> (Where the core WP files are stored)
│   ├── shared
│   │   └── web
│   │       └── app
│   │           └── uploads
│   └── sql
├── conf
│   ├── apache
│   │   ├── conf-enabled
│   │   ├── mods-available
│   │   ├── mods-enabled
│   │   └── sites-enabled
│   ├── mysql
│   │   └── conf.d
│   ├── nginx
│   └── php
│       └── 7.2.0
│           └── etc
│               └── php-fpm.d
└── logs
    ├── apache
    ├── mysql
    ├── nginx
    └── php
        └── 7.2.0

As you can see, we do use symlinks in the folder structure. Primarily for app -> current folder, and for referencing a .env file. We have tried making an export without any symlinks as well, but seemed to get the same errors mentioned above.

Is there any way we could keep our current folder structure, while being able to make the export/import process work? If not, is there any plans to add support for non-standard WP folder structures? Any suggestions or confirmations of this not being supported would be greatly appreciated!

1 Like