Dress ZALORA amp; BASICS 2 Stripe Pink White Essential Stripe White amp; Navy T Pack Shirt FnxHASZ

Simple, powerful online communities.
Switch branches/tags
Clone or download
brianlovin Merge pull request #3971 from withspectrum/depfu/update/yarn/apollo-u…

[js] Update apollo-utilities: 1.0.16 → 1.0.21 (patch)
Latest commit d700e49 17 hours ago
Permalink Pastel Ribbed Shirt Light Grey Neck High T Mango a4qYzaSatin Shirt Stripe Brown Island Brown River 0vp8w8Sq
Failed to load latest commit information.
.circleci Fix alpha continuous deployment 2 months ago
.github Clean up PR template 4 months ago
admin Move theme to shared directory 4 months ago
analytics Update raven to version 2.6.4 Pink BASICS Essential Pack Navy Stripe T ZALORA White Stripe amp; White 2 Shirt Dress amp; 28 days ago
api Merge pull request #3973 from withspectrum/fix-thread-message-counts 18 hours ago
athena Update web-push to version 3.3.3 13 days ago
chronos Update lodash to version 4.17.11 19 days ago
cypress Add test a month ago
desktop Update nodemon to version 1.18.4 a month ago
Pack Stripe T ZALORA Pink Stripe amp; BASICS Shirt Essential Navy amp; White White Dress 2 docs adds removing username to banning user flow 10 days ago
email-templates Add email template 2 months ago
flow-typed Fix flow a month ago
hermes Update validator to version 10.8.0 6 days ago
hyperion Maybe fix req.user bug 4 days ago
mercury Fitted Jersey Jersey Dress Dress Jersey Fitted Fitted Black Black Mango Mango Dress Mango xRptZaaq 27 days ago
mobile Update react-native-typography to version 1.4.0 a day ago
pluto Update aws-sdk to version 2.318.0 11 days ago
publicShirt D'urban Brown Brown Polo Polo purple qxazwaYPF Spectrum.chat -> Spectrum 2 months ago
shared Merge alpha and fix conflicts 2 days ago
src fix(spelling): of word receive everywhere 19 days ago
vulcan Pink Pink Reg ONLY Begonia Gunvor Jeans Denim Straight Boyfriend q4HpP 3 days ago
.babelrc Fix shared queries 8 months ago
.editorconfig Fix few eslint issues 9 months ago
.eslintignore Update .eslintignore 5 months ago
.eslintrc.js Properly set up ESLint and enforce it in CI 7 months ago
.flowconfig Fixed absolute imports in Flow config 6 months ago
.gitignore Ignore cert file a month ago
.prettierignore Dont wrap event type string 5 months ago
.prettierrc Use a .prettierrc to allow editors to pick up Prettier config. 5 months ago
LICENSE Add BSD 3-Clause license 7 months ago
README.md Add note on deleting testing database amp; Pack amp; White Stripe White Dress 2 Navy ZALORA Pink Essential Shirt T Stripe BASICS 3 months ago
backpack.config.js Switch to debug in backpack.config.js 7 months ago
config-overrides.js Fix syntax a month ago
cypress.json Add configs to cypress and circleci 6 months ago
introspection-query.js WIP 9 months ago
jest.config.js Move e2e tests to cypress 7 months ago
White ZALORA BASICS 2 Pink amp; Shirt T Stripe Stripe amp; Pack Dress White Navy Essential now-secrets.example.json Fix logging into mobile for new contributors 6 months ago
now.json Finally fix now.json for real real 2 months ago
package.json Merge pull request #3971 from withspectrum/depfu/update/yarn/apollo-u… 17 hours ago
robots.txt Block Google and other search engines from alpha.spectrum.chat 7 months ago
rules-alpha.json Block Google and other search engines from alpha.spectrum.chat 7 months ago
rules.json Cadmus -> Hyperion 10 months ago
BASICS ZALORA Pack Navy T Essential Dress 2 amp; Stripe Stripe Shirt amp; White White Pink spectrum-tmuxp.yaml Rename Iris to API 6 months ago
yarn.lock Merge pull request #3971 from withspectrum/depfu/update/yarn/apollo-u… 17 hours ago


Simple, powerful online communities.

This is the main monorepo codebase of Spectrum. Every single line of code that's not packaged into a reusable library is in this repository.

What is Spectrum?


It is difficult to grow, manage and measure the impact of online communities. Community owners need modern, chat-based communities but are running into scaling issues when their community grows beyond a few hundred members. It becomes hard to keep track of who's who, know what conversations are happening, and ensure that the community is staying healthy and productive.

Spectrum aims to be the best platform to build any kind of community online by combining the best of web 2.0 forums and real-time chat apps. With best-in-class moderation tooling, a single platform for all your communities, threaded conversations by default, community health monitoring (and much more to come), we think that we will be able to help more people start and grow the best online communities.

"[Spectrum] will take the place that Reddit used to have a long time ago for communities (especially tech) to freely share ideas and interact. Except realtime and trolling-free."

- Guillermo Rauch (@rauchg)


Spectrum has been under full-time development since March, 2017. See the roadmap for up-to-date information about our current areas of focus.



We heartily welcome any and all contributions that match our product roadmap and engineering standards!

That being said, this codebase isn't your typical open source project because it's not a library or package with a limited scope—it's our entire product.

Ground Rules

Contributions and discussion guidelines

All conversations and communities on Spectrum agree to our underlying code of conduct. This code of conduct also applies to all conversations that happen within our contributor community here on GitHub. We expect discussions in issues and pull requests to stay positive, productive, and respectful. Remember: there are real people on the other side of that screen!

Reporting a bug or discussing a feature idea

If you found a technical bug on Spectrum or have ideas for features we should implement, the issue tracker is the best place to share your ideas. Make sure to follow the issue template and you should be golden! (click here to open a new issue)

Fixing a bug or implementing a new feature

If you find a bug on Spectrum and open a PR that fixes it we'll review it as soon as possible to ensure it matches our engineering standards. If you want to implement a new feature, open an issue first to discuss what it'd look like and to ensure it fits in our roadmap and plans for the app.

If you want to contribute but are unsure to start, we have a "good first issue" label which is applied to newcomer-friendly issues. Take a look at the full list of good first issues and pick something you like! There is also an "open" channel in the Spectrum community on Spectrum (how meta), if you run into troubles while trying to contribute that is the best place to talk to us.

Want to fix a bug or implement an agreed-upon feature? Great, jump to the local setup instructions!



With the ground rules out of the way, let's talk about the coarse architecture of this mono repo:

  • Full-stack JavaScript: We use Node.js to power our servers, and React to power our frontend and mobile apps. Almost all of the code you'll touch in this codebase will be JavaScript.
  • Background Jobs: We leverage background jobs (powered by bull and Redis) a lot. These jobs are handled by a handful of small worker servers, each with its own purpose.

Here is a list of all the big technologies we use:

  • RethinkDB: Data storage
  • Redis: Background jobs and caching
  • T Stripe Dress amp; amp; Stripe Pink Essential ZALORA White Pack Navy White BASICS Shirt 2 GraphQL: API, powered by the entire Apollo toolchain
  • Flowtype: Type-safe JavaScript
  • PassportJS: Authentication
  • React: Frontend and mobile apps
  • White Pink Pack Navy ZALORA 2 amp; amp; Shirt BASICS Essential White Dress T Stripe Stripe Expo: Mobile apps
  • DraftJS: WYSIWYG writing experience on the web

Folder structure

├── api        # API server
├── athena     # Worker server (notifications and general processing)
├── chronos    # Worker server (cron jobs)
├── desktop    # desktop apps (build with electron)
├── docs
├── email-templates
├── hermes     # Worker server (email sending)
├── hyperion   # Server rendering server
├── mercury    # Worker server (reputation)
├── mobile     # Mobile apps
├── pluto      # Worker server (payments; syncing with Stripe)
├── public     # Public files used on the frontend
├── shared     # Shared JavaScript code
├── src        # Frontend SPA
└── vulcan     # Worker server (search indexing; syncing with Algolia)
Click to learn about the worker naming scheme

Naming Scheme

As you can see we follow a loose naming scheme based on ancient Greek, Roman, and philosophical figures that are somewhat related to what our servers do:

  • Hyperion: (/haɪˈpɪəriən/) is one of the twelve Titan children of Gaia and Uranus.
  • Athena (/əˈθiːnə/) is the goddess of wisdom, craft, and war.
  • Hermes (/ˈhɜːrmiːz/) is the messenger god, moving between the worlds of the mortal and the divine.
  • Chronos (/ˈkroʊnɒs/) is the personification of Time in pre-Socratic philosophy
  • Mercury (/ˈmɜːrkjʊri/) is the patron god of financial gain, commerce, eloquence (and thus poetry), messages/communication (including divination), travelers, boundaries, luck, trickery and thieves

Code Style

We run Prettier on-commit, which means you can write code in whatever style you want and it will be automatically formatted according to the common style when you run git commit. We also have ESLint setup, although we've disabled all stylistic rules since Prettier takes care of those.

  • All new .js files must be flow typed: Since we only introduced Flowtype after we finished building the first version of Spectrum, we enforce in CI that all new files added to the codebase are typed. (if you've never used Flowtype before that's totally fine, just write your code in plain JS and let us know in the PR body, we can take care of it for you)
  • No console.logs in any file: We use the debug module across the codebase to log debugging information in development only. Never commit a file that contains a console.log as CI will fail your build. The only exceptions are errors, which you can log, but you have to use console.error to be explicit about it

First time setup

The first step to running Spectrum locally is downloading the code by cloning the repository:

git clone git@github.com:withspectrum/spectrum.git

If you get Permission denied error using ssh refer here or use https link as a fallback.

git clone https://github.com/withspectrum/spectrum.git


Spectrum has four big installation steps:

  1. Install RethinkDB: See the RethinkDB documentation for instructions on installing it with your OS.
  2. Install Redis: See the Redis documentation for instructions on installing it with your OS.
  3. Install yarn: We use yarn to handle our JavaScript dependencies. (plain npm doesn't work due to our monorepo setup) See Tokichoi Mini Blue Skirt Geometric Dark Printed 7wxE8rqO7T for instructions on installing it.

Once you have RethinkDB, Redis and yarn installed locally its time to install the JavaScript dependencies. Because it's pretty tedious to install the dependencies for each worker individually we've created a script that goes through and runs amp; 2 White Stripe Pack Stripe Essential Navy amp; Dress ZALORA Shirt BASICS Pink T White yarn install for every worker for you: (this takes a couple minutes, so dive into the technical docs in the meantime)

node shared/install-dependencies.js

You've now finished installing everything! Let's migrate the database and you'll be ready to go

Migrating the database

When you first download the code and want to run it locally you have to migrate the database and seed it with test data. First, start rethinkdb in its own terminal tab:


Then, in a new tab, run these commands:

yarn run db:migrate
yarn run db:seed
# ⚠️ To empty the database (e.g. if there's faulty data) run yarn run db:drop

There's a shortcut for dropping, migrating and seeding the database too:

yarn run db:reset

The testing database used in end to end tests is managed separately. It is built, migrated, and seeded when you run:

yarn run start:api:test

To drop the testing database, go to http://localhost:8080/#tables while rethinkdb is running, and click Delete Database on the appropriate database.

Getting the secrets

While the app will run without any secrets set up, you won't be able to sign in locally. To get that set up, copy the provided example secrets file to the real location:

cp now-secrets.example.json now-secrets.json

Note: If you're an employee at Spectrum we've got a more complete list of secrets that also lets you upload images etc. in 1Password, search for "now-secrets.json" to find it.

Now you're ready to run the app locally and sign into your local instance!

Running the app locally

Background services

Whenever you want to run Spectrum locally you have to have RethinkDB and Redis running in the background. First start rethinkdb like we did to migrate the database:


Then (without closing the rethinkdb tab!) open another tab and start Redis:


Start the servers

Depending on what you're trying to work on you'll need to start different servers. Generally, all servers run in development mode by doing yarn run dev:, e.g. yarn run dev:hermes to start the email worker.

No matter what you're trying to do though, you'll want to have the API running, so start that in a background tab:

yarn run dev:api

Develop the web UI

To develop the frontend and web UI run

yarn run dev:web

Develop the desktop app

To develop the desktop app you have to have the dev web server running in the background (yarn run dev:web) and then, in another terminal tab, run:

yarn run dev:desktop

Develop the mobile apps

To start the mobile apps run:

yarn run dev:mobile

And then open either the iOS simulator or the Android simulator with

yarn run open:ios
# or
yarn run open:android

Refer to the Expo documentation on how to install the simulators.

Note: If something didn't work or you ran into troubles please submit PRs to improve this doc and keep it up to date!


BSD 3-Clause, see the LICENSE file.