-
Notifications
You must be signed in to change notification settings - Fork 329
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fresh install doesn't work out of the box #91
Comments
A quick fix for this is to use Heroku's (deprecated) cedar-10 stack instead of cedar-14 (the latter has been the default stack for new apps since late 2014). To do this, run:
Then, to trigger a rebuild:
Using cedar-10 isn't ideal. I'll post back when I figure out how to get things running properly on cedar-14. |
@mchung would probably need to recompile for cedar-14 for this buildpack to work with cedar-14. Alternatively you can run WP on the standard Heroku stack now (and their php buildpack), see https://github.com/mchung/heroku-buildpack-wordpress for a "See also" list that I just added. |
can we get information on this, or will cedar-14 not be supported in the near future? |
Bump. Any word on how to migrate to cedar-14? |
To keep using this buildpack on cedar-14 @mchung needs to recompile on cedar-14 and put the files into his s3 bucket that the buildpack uses. Or someone else needs to recompile, scripts are available at https://github.com/mchung/heroku-buildpack-wordpress/tree/master/support - vulcan is deprecated now too (https://github.com/heroku/vulcan), so they need to be migrated first, probably. Once you have those compiled, you can set your own S3 bucket with the S3_BUCKET variable. Instead, I recommend using the standard PHP buildpack now provided by Heroku. An example is at https://github.com/xyu/heroku-wp |
@mchung and others. But it doesn't really work any more... So it would be great to add a big red message in the Readme or something so people don't waist there time. It's ok to stop maintaining a repo but a clearer message is important. At least that's what I think. |
It's complaining about missing libraries :
nginx: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory
php-fpm: error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory
The text was updated successfully, but these errors were encountered: