This project was bootstrapped with Create React App.
Below you will find some information on how to perform common tasks.
You can find the most recent version of this guide here.
- Clone the Spruce Github repository
- Ask a colleague for their .cmdrc.json file and follow the instructions here
- Run
npm install
- Start a local evergreen server by doing the following:
- Clone the evergreen repo into your go path
- Run
make local-evergreen
- Run
npm run dev
. This will launch the app and point it at the local evergreen server you just ran.
Run npm run storybook
to launch storybook and view our shared components.
Follow these directions to enable query linting during local development so your Evergreen GraphQL schema changes are reflected in your Spruce query linting results.
- Symlink the standard definition language GraphQL schema used in your backend to a file named sdlschema in the root of the Spruce directory to enable query linting with ESlint like so
ln -s /path/to/schema sdlschema
- Run
npm run eslint
to see the results of query linting in your terminal or install a plugin to integrate ESlint into your editor. If you are using VSCode, we recommend ESLint by Dirk Baeumer.
env-cmd is used to configure build environments for production, staging and development. This file is git ignored because it contains API keys that we do not want to publish. It should be named .cmdrc.json
and placed in the config folder at the root of the project. This file is required to deploy Spruce to production and to staging. Ask a team member to send you their copy of the file, which should look like the following:
{
"devServer": {
"REACT_APP_GQL_URL": "http://localhost:9090/graphql/query"
},
"mockIntrospectSchema": {
"REACT_APP_GQL_URL": "http://localhost:9090/graphql/query",
"REACT_APP_ENABLE_GQL_MOCK_SERVER": "true"
},
"mockCustomSchema": {
"REACT_APP_SCHEMA_STRING": "type Patch {\n id: ID!\n description: String!\n project: String!\n githash: String!\n patchNumber: Int!\n author: String!\n version: String!\n status: String!\n createTime: Time!\n startTime: Time!\n finishTime: Time!\n variants: [String]!\n tasks: [String]!\n variantTasks: [VariantTask]!\n activated: Boolean!\n alias: String!\n }\n type Query {\n userPatches(userId: String!): [Patch]!\n }\n type StatusDetails {\n status: String!\n type: String!\n desc: String!\n }\n scalar Time\n type VariantTask {\n display_name: String!\n tasks: [String]!\n }\n"
},
"staging": {
"REACT_APP_API_URL": "https://evergreen-staging.corp.mongodb.com/api",
"REACT_APP_UI_URL": "https://evergreen-staging.corp.mongodb.com"
},
"prod": {
"REACT_APP_BUGSNAG_API_KEY": "this-is-the-api-key",
"REACT_APP_API_URL": "https://evergreen.mongodb.com/api",
"REACT_APP_UI_URL": "https://evergreen.mongodb.com",
"REACT_APP_NEW_RELIC_ACCOUNT_ID": "dummy-new-relic-account-id",
"REACT_APP_NEW_RELIC_AGENT_ID": "dummy-new-relic-agent-id",
"REACT_APP_NEW_RELIC_APPLICATION_ID": "dummy-new-relic-application-id",
"REACT_APP_NEW_RELIC_LICENSE_KEY": "dummy-new-relic-license-key",
"REACT_APP_NEW_RELIC_TRUST_KEY": "dummy-new-relic-trust-key"
}
}
A .cmdrc.json
file is required to deploy because it sets the environment variables that the application needs in production and staging environments. See Environment Variables section for more info about this file.
Run the deploy:prod
or deploy:staging
npm command
npm run deploy:prod
= deploy to https://spruce.mongodb.comnpm run deploy:staging
= deploy to http://evergreen-staging.spruce.s3-website-us-east-1.amazonaws.com/