Wordpress Installed? failing on wp 5.6 missing web/wp/wp- includes/class-wp-application-passwords.php

mZoo · March 7, 2021, 10:49pm

Well, yes. I had done that, thanks. Sorry the previous post wasn’t more clear.

Seems that when composer installs from the lockfile, the aforementioned dotenv files are missing.

Temporarily adding this task:


- name: Clean out Composer installed stuff
  command: rm -rf vendor composer.lock
  args:
    chdir: "{{ deploy_helper.new_release_path }}"

before Install Composer dependencies enables deploy to succeed.

So, why is installation from the lockfile breaking?

This is the relevant section and it looks fine to me:

{
    "name": "vlucas/phpdotenv",
    "version": "v5.3.0",
    "source": {
        "type": "git",
        "url": "https://github.com/vlucas/phpdotenv.git",
        "reference": "b3eac5c7ac896e52deab4a99068e3f4ab12d9e56"
    },
    "dist": {
        "type": "zip",
        "url": "https://api.github.com/repos/vlucas/phpdotenv/zipball/b3eac5c7ac896e52deab4a99068e3f4ab12d9e56",
        "reference": "b3eac5c7ac896e52deab4a99068e3f4ab12d9e56",
        "shasum": ""
    },
    "require": {
        "ext-pcre": "*",
        "graham-campbell/result-type": "^1.0.1",
        "php": "^7.1.3 || ^8.0",
        "phpoption/phpoption": "^1.7.4",
        "symfony/polyfill-ctype": "^1.17",
        "symfony/polyfill-mbstring": "^1.17",
        "symfony/polyfill-php80": "^1.17"
    },
    "require-dev": {
        "bamarni/composer-bin-plugin": "^1.4.1",
        "ext-filter": "*",
        "phpunit/phpunit": "^7.5.20 || ^8.5.14 || ^9.5.1"
    },
    "suggest": {
        "ext-filter": "Required to use the boolean validator."
    },
    "type": "library",
    "extra": {
        "branch-alias": {
            "dev-master": "5.3-dev"
        }
    },
    "autoload": {
        "psr-4": {
            "Dotenv\\": "src/"
        }
    },
    "notification-url": "https://packagist.org/downloads/",
    "license": [
        "BSD-3-Clause"
    ],
    "authors": [
        {
            "name": "Graham Campbell",
            "email": "graham@alt-three.com",
            "homepage": "https://gjcampbell.co.uk/"
        },
        {
            "name": "Vance Lucas",
            "email": "vance@vancelucas.com",
            "homepage": "https://vancelucas.com/"
        }
    ],
    "description": "Loads environment variables from `.env` to `getenv()`, `$_ENV` and `$_SERVER` automagically.",
    "keywords": [
        "dotenv",
        "env",
        "environment"
    ],
    "support": {
        "issues": "https://github.com/vlucas/phpdotenv/issues",
        "source": "https://github.com/vlucas/phpdotenv/tree/v5.3.0"
    },
    "funding": [
        {
            "url": "https://github.com/GrahamCampbell",
            "type": "github"
        },
        {
            "url": "https://tidelift.com/funding/github/packagist/vlucas/phpdotenv",
            "type": "tidelift"
        }
    ],
    "time": "2021-01-20T15:23:13+00:00"
}

The files are all there in the zipped file. At the moment, I’m just working with the barebones bedrock composer dependencies.

mZoo · March 9, 2021, 12:23am

Ok. It’s just removing the vendor directory:

- name: Clean out Composer installed stuff
  command: rm -rf vendor
  args:
    chdir: "{{ deploy_helper.new_release_path }}"

that enables Install Composer Dependencies to succeed.

Otherwise half of the files are missing from vlucas/phpdotenv/src/Repository/Adapter/

Any suggestions from the masters as to how to debug “why” this is happening?

strarsis · March 10, 2021, 12:10am

I just remembered that Trellis simply copies the vendor/ folder during deploy from the previous deploy in an extra step in order to speed up deployment:

github.com

roots/trellis/blob/a81c10b5b0bc01c5ffb61891dd7c6b82c166278a/roles/deploy/defaults/main.yml#L15


project_version: "{{ branch is defined | ternary(branch, project.branch) | default('master') }}"

# The source_path is used to fetch the tags from git, or synchronise via rsync. This way
# you do not have to download/sync the entire project on every deploy
project_source_path: "{{ project_root }}/shared/source"

# There are certain folders you'll want to copy from release to release to speed up deploys.
# Examples: Composer's `vendor` folder, npm's `node_modules`.
# These should not be part of project_shared_children since dependencies need to be atomic and tied to a deploy.
project_copy_folders:
  - vendor

# All the templates to process on the remote system on deploy. These could contain config files.
# `src` and `dest` paths work the same as project_local_files.
project_templates:
  - name: .env config
    src: roles/deploy/templates/env.j2
    dest: .env
    mode: '0600'

# The shared_children is a list of all files/folders in your project that need to be linked to a path in `/shared`.

So it could be that there is a corrupted vendor/ folder that is applied to each new deploy (until it has been cleaned out, too, not just the copied one).

mZoo · March 10, 2021, 12:22am

Ah. You mean a corrupted local vendor file. Pretty sure I had removed that, locally, but will try again. Thank you. Will report back.

strarsis · March 10, 2021, 12:24am

Yes, notably a vendor/ directory in the previous releases. But please note that the current/active release needs the vendor/ folder. So only do this (remove/rename the vendor/ folder or previous releases) if this is a staging/test server that allows for downtime.

mZoo · March 10, 2021, 12:28am

Wait, it copies the vendor directory from the previous release? I though you were saying rsyncs the local vendor directory.

strarsis · March 10, 2021, 12:34am

No, it copies from a previous release in order to speed up the deployment:

github.com

roots/trellis/blob/a81c10b5b0bc01c5ffb61891dd7c6b82c166278a/roles/deploy/tasks/build.yml#L29


    dest: "{{ deploy_helper.new_release_path }}/{{ item.dest }}"
    mode: "{{ item.mode | default('0644') }}"
  with_items: "{{ project.project_templates | default(project_templates) }}"

- name: Check if project folders exist
  stat:
    path: "{{ deploy_helper.current_path }}/{{ item }}"
  register: project_folder_paths
  with_items: "{{ project.project_copy_folders | default(project_copy_folders) }}"

- name: Copy project folders
  command: cp -rp {{ deploy_helper.current_path }}/{{ item.item }} {{ deploy_helper.new_release_path }}
  with_items: "{{ project_folder_paths.results }}"
  when: item.stat.exists

- name: Check if deploy_build_after scripts exist
  stat:
    path: "{{ item }}"
  delegate_to: localhost
  register: deploy_build_after_paths
  with_items: "{{ deploy_build_after | default([]) }}"

strarsis · March 12, 2021, 10:26pm

Were you able to figure out the reason?

mZoo · March 12, 2021, 10:37pm

Thanks for reaching out. I have not, man! Need to get back to it. When I removed the Copy project folders task, these was the error about missing wp-includes/cache-compat.php, and without my workaround of removing the vendor directory within the new_release_path, the same missing files in vlucas/phpdotenv comes up.

When I cp -rp the vendor directory from “current” manually, all the files are there.

So at the moment, it’s still a mystery. I’ll poke at it again ASAP.

system · April 8, 2021, 9:15pm

This topic was automatically closed after 42 days. New replies are no longer allowed.