Running Coral for development is very similar to installing Coral via Source as described in our Getting Started guide.
Coral requires NodeJS ^14.18, we recommend using
nvm to help manage node
# Clone and cd into the Coral directory.git clone https://github.com/coralproject/talk.gitcd talk # Install dependencies.npm install
Running Coral with default settings assumes that you have:
- MongoDB ^4.2 running on
- Redis ^3.2 running on
If you don't already have these databases running, you can execute the following assuming you have Docker installed on your local machine:
docker run -d -p 27017:27017 --restart always --name mongo mongo:4.2docker run -d -p 6379:6379 --restart always --name redis redis:3.2
We recommend installing watchman for better watch performance.
# On macOS, you can run the following with Homebrew.brew install watchman
Then start Coral in development mode with:
# Run the server in development mode in order to facilitate auto-restarting and# rebuilding when file changes are detected. This might take a while to fully# run.npm run watch
When the client code has been built, navigate to http://localhost:8080/install to start the installation wizard.
To see the comment stream goto http://localhost:8080/.
To run linting and tests use the following commands:
# Run the linters.npm run lint # Run our unit and integration tests.npm run test
To test out the email sending functionality, you can run inbucket which provides a test SMTP server that can visualize emails in the browser:
docker run -d --name inbucket --restart always -p 2500:2500 -p 9001:9000 inbucket/inbucket
You can then configure the email server on Coral
by setting the email settings in
Configure -> Email in the admin:
Navigate to http://localhost:9001, click the "Monitor" tab. New emails received on this screen.
To get started contributing, check out our Contribution Guidelines.
We’re so proud to have received submissions from a lot of 3rd party contributors translating Coral into their own languages.
You can see what languages Coral currently supports here: https://github.com/coralproject/talk/tree/main/src/locales
Strings are added or removed from localization bundles in the translation files
as needed. Strings MUST NOT be changed after they've been committed and
main. Changing a string requires creating a new ID with a new name
(preferably descriptive instead of incremented) and deletion of the obsolete ID.
It's often useful to add a comment above the string with info about how and
where the string is used.
Once a language has enough coverage, it should be added to
The Perspective API
also supports comments in specific languages. When the language is supported in
Coral and supported by the Perspective API, the language should be added to the
language map in
To assist with the translation process, we have a script that is based on the work by @cristiandean in https://github.com/coralproject/talk/pull/2949 that will detect missing, new, or changed translation keys for the specified language. You can use this with:
# usage: ./scripts/i18n/validate.ts <locale>./scripts/i18n/validate.ts pt-BR