[Question] Self-hosted cms

[dgfh0450]

We’ve already implemented all translations and configurations using next-intl. However, we need a CMS for easier management, so we’d like to adopt this library.
We need a self-hosted CMS. The landing page mentions self-hosting, but we’d like to find documentation on how to get started with the self-hosted setup.

Additionally, we’d like to know whether it’s possible to remotely push changes back to GitHub when translation values (JSON files) are updated in the CMS.

[aymericzip]

Hey @dgfh0450

We are working on it. There is no clear doc yet. We hope to release it in the next 4 months.
But you can clone the repo and, add your secrets by reusing .env.template and run the dockerfiles (see root package.json)

If you guys wanna contribute to match your needs, you're welcome

Additionally, we’d like to know whether it’s possible to remotely push changes back to GitHub when translation values (JSON files) are updated in the CMS.

Yes, the v8 (that will be released today) will allow it. You can set up dictionary.location (in each .content or globally in you .config) and set location

---

location ('remote' | 'local' | 'hybrid' | 'plugin')

Indicates the location of the dictionary. This property can be set to control where the dictionary is sourced from:

• 'local': Local dictionary (from content files)
• 'remote': Remote dictionary (from external source/CMS)
• 'hybrid': Dictionary that exists both locally and remotely
• 'plugin': Dictionary provided by a plugin