【问题标题】:Composer searches / and \ pathsComposer 搜索 / 和 \ 路径
【发布时间】:2015-07-11 06:13:53
【问题描述】:

我正在将我的 PHP 应用程序部署到 Microsoft Azure 平台。在部署时它运行composer install,并且它在windows中存在反斜杠问题:对于项目和库中的每个类,它都使用/和\作为路径分隔符来解析文件。出现了数以万计的此类错误:

Warning: Ambigous class resolution. "SomeClass" was found in both
"D:/home/site/wwwroot/vendor/somevendeor/somelib/src/SomeClass.php" and 
"D:\home\site\wwwroot\vendor\somevendeor\somelib\src\SomeClass.php"

两次解析每个文件并通过网络打印所有错误需要很长时间,以至于 Azure 取消了作曲家进程。部署失败 10 次中有 9 次失败(使应用程序处于无效、无法运行的状态)。

有谁知道对此可以做些什么?我会很感激每一个提示!谢谢:)

编辑:这是我的 composer.json:

{
    "name": "laravel/laravel",
    "description": "The Laravel Framework.",
    "keywords": ["framework", "laravel"],
    "require": {
        "laravel/framework": "4.2.*",       
        "cartalyst/sentry": "2.0.*",
        "facebook/php-sdk-v4": "4.0.*",
        "thetwelvelabs/foursquare": "dev-master@dev",
        "hybridauth/hybridauth": "*",
        "caouecs/laravel4-lang": "*",
        "phpoffice/phpexcel": "*",
        "google/apiclient": "*"
    },
    "autoload": {
        ...
    },
    "scripts": {
        ...
    },
    "config": {
        "preferred-install": "dist"
    },
    "minimum-stability": "dev"
}

编辑 2:这是我的 deploy.sh(在 Azure 上的 Repo 推送成功后执行):

#!/bin/bash

# ----------------------
# KUDU Deployment Script
# Version: 0.2.2
# ----------------------

# Helpers
# -------

exitWithMessageOnError () {
  if [ ! $? -eq 0 ]; then
    echo "An error has occurred during web site deployment."
    echo $1
    exit 1
  fi
}

# Prerequisites
# -------------

# Verify node.js installed
hash node 2>/dev/null
exitWithMessageOnError "Missing node.js executable, please install node.js, if already installed make sure it can be reached from current environment."

# Setup
# -----

SCRIPT_DIR="${BASH_SOURCE[0]%\\*}"
SCRIPT_DIR="${SCRIPT_DIR%/*}"
ARTIFACTS=$SCRIPT_DIR/../artifacts
KUDU_SYNC_CMD=${KUDU_SYNC_CMD//\"}

if [[ ! -n "$DEPLOYMENT_SOURCE" ]]; then
  DEPLOYMENT_SOURCE=$SCRIPT_DIR
fi

if [[ ! -n "$NEXT_MANIFEST_PATH" ]]; then
  NEXT_MANIFEST_PATH=$ARTIFACTS/manifest

  if [[ ! -n "$PREVIOUS_MANIFEST_PATH" ]]; then
    PREVIOUS_MANIFEST_PATH=$NEXT_MANIFEST_PATH
  fi
fi

if [[ ! -n "$DEPLOYMENT_TARGET" ]]; then
  DEPLOYMENT_TARGET=$ARTIFACTS/wwwroot
else
  KUDU_SERVICE=true
fi

if [[ ! -n "$KUDU_SYNC_CMD" ]]; then
  # Install kudu sync
  echo Installing Kudu Sync
  npm install kudusync -g --silent
  exitWithMessageOnError "npm failed"

  if [[ ! -n "$KUDU_SERVICE" ]]; then
    # In case we are running locally this is the correct location of kuduSync
    KUDU_SYNC_CMD=kuduSync
  else
    # In case we are running on kudu service this is the correct location of kuduSync
    KUDU_SYNC_CMD=$APPDATA/npm/node_modules/kuduSync/bin/kuduSync
  fi
fi

##################################################################################################################################
# Download Composer
# ----------
echo Downloading Composer
curl -sS https://getcomposer.org/installer | php

##################################################################################################################################
# Deployment
# ----------

echo "Switching to Maintenance Mode"

cd $DEPLOYMENT_TARGET
php artisan down
exitWithMessageOnError "Failed to turn maintenance on (php artisan down)"

echo Handling Basic Web Site deployment.

# 1. KuduSync
if [[ "$IN_PLACE_DEPLOYMENT" -ne "1" ]]; then
  "$KUDU_SYNC_CMD" -v 50 -f "$DEPLOYMENT_SOURCE" -t "$DEPLOYMENT_TARGET" -n "$NEXT_MANIFEST_PATH" -p "$PREVIOUS_MANIFEST_PATH" -i ".git;.hg;.deployment;deploy.sh"
  exitWithMessageOnError "Kudu Sync failed"
fi

##################################################################################################################################
# Dependency install
# ----------
# Invoke Composer in the deployment directory

echo Invoking composer install in deployment directory $DEPLOYMENT_TARGET
cd $DEPLOYMENT_TARGET
php $DEPLOYMENT_TARGET/composer.phar install -v --prefer-dist --no-dev --optimize-autoloader --no-interaction

echo Deleting all active Sessions
rm -f $DEPLOYMENT_TARGET/app/storage/sessions/*
echo Deleted all active Sessions

echo Clearing the cache
rm -f $DEPLOYMENT_TARGET/app/storage/cache/*
echo Cache Cleared

##################################################################################################################################

# Post deployment stub
if [[ -n "$POST_DEPLOYMENT_ACTION" ]]; then
  POST_DEPLOYMENT_ACTION=${POST_DEPLOYMENT_ACTION//\"}
  cd "${POST_DEPLOYMENT_ACTION_DIR%\\*}"
  "$POST_DEPLOYMENT_ACTION"
  exitWithMessageOnError "post deployment action failed"
fi

echo "Turning off Maintenance Mode"

cd $DEPLOYMENT_TARGET
php artisan up
exitWithMessageOnError "Failed to turn maintenance off (php artisan up)"

echo "Finished successfully."

【问题讨论】:

  • 您能否展示您的composer.json 文件 - 最好是只添加一个库的简短文件,这样仍然可以证明问题所在。
  • 部署后通过 shell 手动执行composer -o dump-autoload 时不会出现此问题。 composer.json 包含库和一些自动加载目录,没什么特别的。我认为这与问题无关。
  • 这是否意味着您不会提供数据来证明问题?如果这是 Composer 中错误处理 Windows 路径的错误,则应在此处修复。
  • 不,我只是认为这并不重要。我怀疑主机有问题(在我的机器上,一切都很好)。但我包括了 composer.json
  • 部署期间触发错误的命令是什么?

标签: php azure composer-php backslash


【解决方案1】:

我使用您提供的详细信息尝试了 git 部署。以下更改对我有用

您的部署脚本引用了 artisan 文件。我不得不删除下面的行

deploy.sh

   php artisan down
   php artisan up

我在 package.json

中没有您的脚本/自动加载详细信息
  "autoload": {
        ...
    },
    "scripts": {
        ...
    },

查看上述配置更改并检查是否可以解决您的问题。

【讨论】:

  • 你的问题解决了吗?
  • 重新设置使它在三个阶段中的两个阶段消失,第三阶段没有任何变化。我会等待另一个作曲家更新。
猜你喜欢
  • 2013-08-25
  • 1970-01-01
  • 2014-06-05
  • 1970-01-01
  • 2012-06-07
  • 2012-01-01
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
相关资源
最近更新 更多