cap deploy failed about sylius HOT 6 CLOSED

Hi @PaddyLock,

This is a common issue with Composer, not specific to Sylius. It sounds like you're running out of memory (I'm guessing you're using a t1.micro AWS image). You need to create a swap file (check out this old thread from AWS https://forums.aws.amazon.com/thread.jspa?threadID=53053) so that your instance does not run out of memory when trying to install/update dependencies.

Hope this helps!

from sylius.

Thanks, I have created a swap file and now It works. However I had to change the following value to false to get it to work the first time. Do you know why?

set :update_vendors, false

Also I had to manually create and copy contents to shared/app/config/parameters.yml on the server, as described here - http://capifony.org/

Thanks

from sylius.

Yes, seems like you copy vendors from previous release, without running composer, and it's the composer script that copies the parameters file. Parameters file is shared between deploys, you should simply fill it once and then deploy should work. :)

from sylius.

An additional step that is needed, which might help someone else is to set permissions on cache and logs folders:

sudo apt-get install acl
cd shared
sudo setfacl -R -m u:www-data:rwX -m u:whoami:rwX app/logs
sudo setfacl -dR -m u:www-data:rwx -m u:whoami:rwx app/logs
cd current
sudo setfacl -R -m u:www-data:rwX -m u:whoami:rwX app/cache
sudo setfacl -dR -m u:www-data:rwx -m u:whoami:rwx app/cache

cheers

from sylius.

Happy that it's resolved, we should write a nice cookbook entry about how to deploy/configure Sylius to Amazon. @PaddyLock I can close this right?

from sylius.

Yes, thanks

from sylius.