Unable to deploy Symfony application about heroku-buildpack-php HOT 19 CLOSED

Same problem here. Currently we can't deploy the application. It seems a problem with symfony though (as referenced).

from heroku-buildpack-php.

Has this been solved? I am having similar issues, but only on Heroku. Dev/Prod work fine in other environments.

from heroku-buildpack-php.

Two steps that help mitigate this:

1. make sure you heroku config:set SYMFONY_ENV=prod before pushing
2. in composer.json's post-install-cmd list, move the clearCache command to the very end

from heroku-buildpack-php.

@eddiejaoude This issue is present in heroku due to it's slug compilation and ephemeral filesystem.

When your app is compiled and all scripts ran (cache warm up, etc) this happens in /tmp/<random id>, and all cache with absolute path are generated pointing to that path.
But when the compilation finishes the app is located at /app and /tmp is cleared up. And due to heroku's ephemeral filesystem this can't be changed later on.

The issue is handled at symfony/symfony#10999 . If you need your app up and running in heroku you may use https://github.com/CHH/heroku-buildpack-php which I believe handles this issue https://github.com/CHH/heroku-buildpack-php/blob/master/frameworks/symfony2#L45.

from heroku-buildpack-php.

@desyncr Thank you for the detailed explanation. I tried the CHH build pack, but came across another issue with no routes being found (eg. always a 404). I will try again.

from heroku-buildpack-php.

@eddiejaoude CHH solution is not bulletproof. ie, it won't work with jms serializer as it's metadata is cached in a serialized format thus a simple string replacement will break the serialization.

from heroku-buildpack-php.

Same problem here. Moving the clear:cache command to the end fixed it for me. Thank you @dzuelke

from heroku-buildpack-php.

Do you have any routes defined for the prod environment, @eddiejaoude? If you just create a blank standard edition project with nothing else then there are no routes, and everything always 404s.

from heroku-buildpack-php.

@dzuelke oh I see, thank you. I will double check.

from heroku-buildpack-php.

Thanks @dzuelke . Ok, getting closer. Moving clear:cache to the end & put routes in prod, now I have a webpage 😄 . But there is not styling anymore from the Twitter Bootstrap Bundle Braincrafted\Bundle\BootstrapBundle\BraincraftedBootstrapBundle.

@desyncr Good to be aware of! Thanks.

from heroku-buildpack-php.

It seems in prod mode I need to run the following command php app/console assetic:dump. What is the best way to run this after (at the end of) a deploy? Thanks

from heroku-buildpack-php.

This issue should be fixed when symfony/symfony#12784 is merged. So, that would mean as of Symfony 2.3.23, 2.5.8, 2.6.1, and upcoming versions (2.7., 3., ...)

To make it happen fast, can anyone test this PR and report if that works? Thanks.

from heroku-buildpack-php.

Confirmed working, @fabpot. Good job. Go for it!

from heroku-buildpack-php.

@fabpot thank you for clarifying the version numbers

from heroku-buildpack-php.

👍

from heroku-buildpack-php.

2.3.23, 2.5.8, 2.6.1 are out. I think this issue can be closed now.

from heroku-buildpack-php.

Great, thanks 👍

from heroku-buildpack-php.

👍 Thanks guys! Worked flawlessly! (tested with 2.6.1 on heroku)

from heroku-buildpack-php.

I think this can be closed now?

from heroku-buildpack-php.