Nick Funk 662f5ce314 [CORL-409] Prevent users from ignoring staff members (#2355)
* Throw error if user tries to ignore a staff member

Throws a UserCannotBeIgnoredError if a user tries to ignore
a user who is a staff member. A staff member in this case is
considered anyone who has a role of staff, moderator, or admin.

CORL-409

* Prevent users from ignoring staff in the user info popover

Creates the staff roles in a constant next to the user model.
Uses this to add a computed property to the user resolver.

CORL-409

* Remove unnecessary async declaration from userIsStaff helper function

CORL-409

* Specify ignoreable on users in client test fixtures

Allows the tests to pass for the required computed property
of ignoreable that is computed by whether a user is a staff
member or not.

CORL-409

* Update more fixtures with ignoreable property on mocked users/commenters

CORL-409

* Consolidate ignore-able calculation into re-usable helper methods

Re-use the logic for whether a role is a staff member to
clearly define when a user is ignore-able or not across the
business logic.

CORL-409

* Set the ignoreable optimisticResponse on comment mutations

We have set the ignoreable value in the graphQL schema, so now
the optimisticResponses are looking for a default value to use
until the data result arrives. Put to false since the ignoreable
value is set on our author, we likely don't want to ignore ourselves.

CORL-409
2019-06-13 17:24:50 +00:00
2019-05-09 22:54:56 +02:00
2019-06-07 21:42:26 +00:00
2019-04-15 19:46:55 +02:00
2018-06-21 10:44:36 -06:00
2019-04-15 19:46:55 +02:00
2019-03-12 15:12:21 +01:00
2018-07-06 13:08:10 -06:00
2019-05-22 21:32:24 +02:00
2019-05-22 21:32:24 +02:00
2019-03-12 15:12:21 +01:00
2019-03-15 13:15:31 -06:00
2019-06-10 23:09:20 +01:00
2019-05-09 22:54:56 +02:00

Coral CircleCI

Online comments are broken. Our open-source commenting platform, Coral, rethinks how moderation, comment display, and conversation function, creating the opportunity for safer, smarter discussions around your work. Read more about Coral here.

Built with <3 by The Coral Project, a part of Vox Media.

Preview Coral easily by running Coral via a Heroku App:

Deploy

Table of Contents

Requirements

  • MongoDB >=3.6
  • Redis >=3.2
  • NodeJS >=10
  • NPM >=6.7

Running

You can install Coral using Docker or via Source. We recommend Docker, as it provides the easiest deployment solution going forward, as all the dependencies are baked and shipped with the provided coralproject/talk:next image. When v5 releases to master, you'll be able to select it using coralproject/talk:5.

Docker

The easiest way to get started with Coral is through our published Docker image and provided example docker-compose.yml file. The following assumes that you have Docker and Docker Compose installed on your local machine:

# Create directories to persist the data in MongoDB and Redis.
mkdir -p data/{mongo,redis}

# Create the `docker-compose.yml` file to get started.
cat > docker-compose.yml <<EOF
version: "2"
services:
  talk:
    image: coralproject/talk:next
    restart: always
    ports:
      - "127.0.0.1:3000:5000"
    depends_on:
      - mongo
      - redis
    environment:
      - MONGODB_URI=mongodb://mongo:27017/coral
      - REDIS_URI=redis://redis:6379
      - SIGNING_SECRET=<replace me with something secret>
  mongo:
    image: mongo:3.6
    volumes:
      - ./data/mongo:/data/db
  redis:
    image: redis:3.2
    volumes:
      - ./data/redis:/data
EOF

# Start up Coral using Docker.
docker-compose up -d

Then head on over to http://localhost:3000 to install Coral!

Source

Coral requires NodeJS >=10, we recommend using nvm to help manage node versions: https://github.com/creationix/nvm.

# Clone and cd into the Coral directory.
git clone https://github.com/coralproject/talk.git
cd talk

# Install dependencies.
npm install

# Build the application dependencies.
# This might take a while.
npm run build

This should output all the compiled application code to ./dist.

Running Coral with default settings assumes that you have:

  • MongoDB >=3.6 running on 127.0.0.1:27017
  • Redis >=3.2 running on 127.0.0.1:6379

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:3.6
docker run -d -p 6379:6379 --restart always --name redis redis:3.2

Then start Coral with:

# Start the server in production mode.
npm run start

Then head on over to http://localhost:3000 to install Coral!

Development

Running Coral for development is very similar to installing Coral via Source as described above.

Coral requires NodeJS >=10, we recommend using nvm to help manage node versions: https://github.com/creationix/nvm.

# Clone and cd into the Coral directory.
git clone https://github.com/coralproject/talk.git
cd talk

# Install dependencies.
npm install

Running Coral with default settings assumes that you have:

  • MongoDB >=3.6 running on 127.0.0.1:27017
  • Redis >=3.2 running on 127.0.0.1:6379

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:3.6
docker run -d -p 6379:6379 --restart always --name redis redis:3.2

Then start Coral 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. Note: Ensure localhost:8080 is used in the permitted domains list.

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

Embed On Your Site

With Coral setup and running locally you can test embeding the comment stream with this sample embed script:

<div id="coral_thread"></div>
<script type="text/javascript">
(function() {
    var talk = document.createElement('script'); talk.type = 'text/javascript'; talk.async = true;
    var url = '{{ CORAL_DOMAIN_NAME }}';
    talk.src = '//' + url + '/assets/js/embed.js';
    talk.onload = function() {
        Coral.createStreamEmbed({
            id: "coral_thread",
            autoRender: true,
            rootURL: '//' + url,
        });
    };
    (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(talk);
})();
</script>

Replace the value of CORAL_DOMAIN_NAME with the location of your running instance of Coral.

Email

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 -p 2500:2500 -p 9000:9000 inbucket/inbucket

You can then configure the email server on Coral by updating the Tenant with:

{
  // ...
  "email": {
    "enabled": true,
    "smtpURI": "smtp://localhost:2500",
    "fromAddress": "community@test.com"
  },
  // ...
}

Restarting Coral will be needed. Navigate to http://localhost:9000, click the "Monitor" tab. New emails received on this screen.

Design Language System (UI Components)

We use docz to document and develop our Design Language System. To start docz run:

# Make sure CSS types are generated.
# This is not required when `npm run watch` is already running.
npm run generate:css-types

# Run docz in development.
npm run docz -- dev

After compilation has finished you can access docz at http://localhost:3030/.

Configuration

The following environment variables can be set to configure the Coral Server. You can expose them in your shell via export NODE_ENV=development or by placing the variables in a .env file in the root of the project in a simple NODE_ENV=development format delimited by newlines.

  • NODE_ENV - Can be one of production or development. All production deployments should use production. Defaults to production when ran with npm run start and development when run with npm run start:development.
  • PORT - The port to listen for HTTP and Websocket requests. (Default 3000)
  • MONGODB_URI - The MongoDB database URI to connect to. (Default mongodb://127.0.0.1:27017/coral)
  • REDIS_URI - The Redis database URI to connect to. (Default redis://127.0.0.1:6379)
  • REDIS_OPTIONS - A JSON string with optional configuration options to be used when connecting to Redis as specified in the ioredis documentation. (Default: {})
  • SIGNING_SECRET - The shared secret to use to sign JSON Web Tokens (JWT) with the selected signing algorithm. 🚨 Don't forget to set this variable! 🚨 (Default: keyboard cat)
  • SIGNING_ALGORITHM - The signing algorithm to use for signing JWT's. (Default HS256).
  • LOGGING_LEVEL - The logging level that can be set to one of fatal, error, warn, info, debug, or trace. (Default info)
  • STATIC_URI - The URI that static assets can be accessed from. This URI can be to a proxy that uses this Coral server on PORT as the upstream. Disabled by default.
  • DISABLE_TENANT_CACHING - When true, all tenants will be loaded from the database when needed rather than keeping a in-memory copy in sync via published events on Redis. (Default false)
  • DISABLE_MONGODB_AUTOINDEXING - When true, Coral will not perform indexing operations when it starts up. This can be desired when you've already installed Coral on the target MongoDB, but want to improve start performance. (Default false)
  • LOCALE - Specify the default locale to use for all requests without a locale specified. (Default en-US)
  • ENABLE_GRAPHIQL - When true, it will enable the /graphiql even in production, use with care. (Default false)
  • CONCURRENCY - The number of worker nodes to spawn to handle web traffic, this should be tied to the number of CPU's available. (Default os.cpus().length)
  • DEV_PORT - The port where the Webpack Development server is running on. (Default 8080)
  • METRICS_USERNAME - The username for Basic Authentication at the /metrics and /cluster_metrics endpoint.
  • METRICS_PASSWORD - The password for Basic Authentication at the /metrics and /cluster_metrics endpoint.
  • CLUSTER_METRICS_PORT - If CONCURRENCY is more than 1, the metrics are provided at this port under /cluster_metrics. (Default 3001)

License

Coral is released under the Apache License, v2.0.

S
Description
A better commenting experience from Vox Media
Readme 39 MiB
Languages
TypeScript 82.5%
Fluent 9.2%
CSS 5%
FreeMarker 1.6%
JavaScript 0.9%
Other 0.7%