Add support for more locales

[heroku]

Add support for more locales

[edmorley]

@samuel02 Hi! I would try running the locale buildpack prior to the existing buildpacks:
https://github.com/heroku/heroku-buildpack-locale

[samuel02]

@edmorley thanks for the suggestion! I tried updating my app.json to:

{
  "environments": {
    "test": {
      "addons": [
         "heroku-redis:in-dyno",
         "heroku-postgresql:in-dyno"
      ],
      "buildpacks": [
        {"url":  "https://github.com/heroku/heroku-buildpack-locale"},
        {"url":  "https://github.com/heroku/heroku-buildpack-ruby"}
      ],
      "env": {
        "LANG": "sv_SE.utf8"
      }
    }
  }
}

But still getting the same error. I see that it is installing language packs but for some reason Postgres doesn't seem to pick it up? Any ideas?

[edmorley]

I'm not very familiar with Postgres locales, so not sure.

I would say the issue is one of:

1. The locales need to be in place before the postgres server is started
2. The locales need to be in place before the postgres DB is initialised
3. One of the settings here needs changing/overriding:

   heroku-buildpack-ci-postgresql/bin/compile

   Lines 93 to 100 in 2bd0c5d

   	export PGDATA=$BUILD_DIR/.indyno/vendor/postgresql/data
   	LC_COLLATE=en_US.UTF-8 \
   	LC_CTYPE=en_US.UTF-8 \
   	LC_MESSAGES=en_US.UTF-8 \
   	LC_MONETARY=en_US.UTF-8 \
   	LC_NUMERIC=en_US.UTF-8 \
   	LC_TIME=en_US.UTF-8 \
   	initdb -E UTF8 | indent

Re (1)/(2): If the in-dyno PG buildpack is automatically added by Heroku CI (due to having heroku-postgresql:in-dyno under the test.addons key in app.json), then it's added before all other buildpacks. If you wanted to try having it run after the locale buildpack, you could remove heroku-postgresql:in-dyno from addons and explicitly add this buildpack to buildpacks (either via the heroku/ci-postgresql buildpack registry alias, or the GitHub URL https://github.com/heroku/heroku-buildpack-ci-postgresql -- in general the buildpack registry aliases are preferred).

To try with (3), I'd first try forking this buildpack, adding it directly to buildpacks and removing heroku-postgresql:in-dyno from addons (as above) and adjusting the settings. If that works you could then try switching back to the non-forked buildpack and seeing if the settings can be updated retrospectively when your CI run starts, to save having to maintain a forked buildpack.