Skip to content

Script @auto-scripts was called via post-install-cmd #99

Description

@infografik

Code

$ ./bin/console deploy -v
[...]
Copying the updated code to the new release directory
[user@domain] Executing command: (export APP_ENV=prod; cd /dir/releases/20190919133916 && cp -RPp /dir/repo/* /dir/releases/20190919133916)
----- START -----
Here is mistake: cp -RPp /dir/repo/* /dir/releases/20190919133916)
The * character does not copy files starting with a dot. Please add:
&& cp -R /dir/repo/.e* /dir/releases/20190919133916) && cp -R /dir/repo/.g* /dir/releases/20190919133916)
Only .* cannot be added due to the presence of '..' in the folder.
----- STOP -----
[...]
Installing Composer dependencies
[user@domain] Executing command: (export APP_ENV=prod; cd /dir/releases/20190919133916 && /usr/local/bin/composer install --no-dev --prefer-dist --no-interaction --quiet)
| err :: Script @auto-scripts was called via post-install-cmd
[ERROR] Cancelling the deployment and reverting the changes
[...]
In Process.php line 256:
[Symfony\Component\Process\Exception\ProcessFailedException] The command "ssh -A user@domain '(export APP_ENV=prod; cd /dir/releases/20190919133916 && /usr/local/bin/composer install --no-dev --prefer-dist --no-interaction --quiet)'" failed.
Exit Code: 255(Unknown error)
[...]
Error Output:
================
Script @auto-scripts was called via post-install-cmd
[...]

Error reason

In /dir/releases/201909133916:
assets composer.json config package.json public symfony.lock tests var webpack.config.js bin composer.lock package-lock.json phpunit.xml.dist src templates translations vendor yarn.lock

There are no files starting with a dot (files are present in /dir/releases/20190919133916):
.env .env-test .git .gitignore

Activity

  1. felixprojekt commented on Oct 13, 2019

    @felixprojekt

    Same issue here

  2. lcavero commented on Nov 1, 2019

    @lcavero

    please fix it!

  3. alzedd commented on May 24, 2020

    @alzedd

    Any News?

  4. lcavero commented on May 25, 2020

    @lcavero

    I solve it adding this lines in deploy.php

    public function beforePreparing() { $this->runRemote('cp {{ deploy_dir }}/repo/.env {{ project_dir }}/.env'); $this->runRemote('cp {{ deploy_dir }}/repo/.env.development {{ project_dir }}/.env.development'); }

  5. alzedd commented on May 25, 2020

    @alzedd

    while I was waiting for a fix to this issue I put my .env file in the shared folder, which I think it's the best thing to do in order to hide sensitive data such as database coordinates and so on

  6. fd6130 commented on Nov 15, 2021

    @fd6130

    while I was waiting for a fix to this issue I put my .env file in the shared folder, which I think it's the best thing to do in order to hide sensitive data such as database coordinates and so on

    But if the .env is a breaking change, rolling back will become another issue i think.

  7. ciscolybon commented on Apr 29, 2022

    @ciscolybon

    salut

  8. adeltby commented on Mar 10, 2023

    @adeltby

    you should make the .env file and set APP_ENV=prod after that run

    composer dump-env prod

    then run :

    composer install --no-dev --optimize-autoloader

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions