Since I starting to set up a fresh instance of Discourse, I wondered: discourse-setup does not ask about the locale settings of the new site and generates an app.yml with LC_ALL/LANG/LANGUAGE = en_US.UTF-8.
Is this correct? If so, it would potentially be helpful if this is mentioned in the installation instructions. And if not, then it would be good if discourse-setup either asks for these settings or at least doesn’t start the container right away, so I can adjust them before the first startup.
I’m mainly asking because for an existing site, I had trouble with the upgrade from Postgres 13 to 15 because of locales (they were adjusted to de_DE.UTF-8 only after initial container creation), which I fixed by resetting to en_US.UTF-8. But on the other hand, this means the Postgres database will be created with collation en_US and this might cause some issues with search when e.g. German Umlauts are used.
Suggests (to me) that you might create a new server with the DE settings and restore the database there.
If you don’t like the safety of being sure they the new site works before you break the old one, and moving to a new os when your old one is likely approaching end of life, you could probably also make a backup, delete the postgres files, change the locale, rebuild to create the new database, and then restore the backup.
EDIT: I speak only English and am not especially expert at the intricacies of locales, but your concern about searches working correctly seem on point to me.
So generally yes, I’ll keep the old server running until everything is set.
What I’m wondering is: while I think I would be able to manually adjust the database locale, I’m not sure if I should. But if that’s the case, then I think it would be good if discourse-setup made my life a bit easier in that regard.
Sorry to bump this, but it’d be great to have some guidance here before setting up a new site (where the default language will be German).
Gerhard’s comments in the GitHub pull request sound like Discourse might already handle language settings internally/on a per column basis, but it’s hard for me to verify if this has been implemented, so I’m not sure whether the default locale of en_US.UTF-8 in app.yml is fine for a German site or not.
