Open Alexander-Minyushkin opened 8 years ago
Interesting, I haven't deployed on Heroku in a while. There are a couple of options: 1) You don't care about translation, so ignore it and run in English 2) Commit compiled translation files (.mo) and push them to Heroku 3) Use a build pack of some sort, try one of these maybe
Sorry I can't be of more help as Heroku was just a demo deployment. If you figure out a good solution, please let me know!
You might also try to swap out the gettext URL with the one here: https://github.com/lexifdev/heroku-buildpack-gettext/blob/master/bin/compile
The tarball should contain the gettext binaries compiled to run on the Heroku platform, so not the source tarball you linked to. And don't forget to adjust the GETTEXT_CHECKSUM
.
Thanks! looks like GETTEXT_TARBALL=http://fb_wanted.s3.amazonaws.com/bp/gettext.tar.gz did the job But now it compile all possible languages, not that defined in settings.LANGUAGES
Better than nothing ;) You can add the -l
flag to compilemessages.
The proposed fix works.
In bin/post_compile you load file wich is not available,
GETTEXT_TARBALL=https://s3-eu-west-1.amazonaws.com/midgard-heroku/gettext.tar.gz
Changing to latest version of gettext doesn't work either:
GETTEXT_TARBALL=http://ftp.gnu.org/pub/gnu/gettext/gettext-latest.tar.gz