* added storyURL and storyID
* added story scraping section
* fixed typo on sso
* rebaseing on latest release/4 branch
* updated version on slack docs
* added Contributing a Translation section to developing
* fixing typos
* updated v5 config page, reorder list, add toc
* added cli sect, fixed contact menu link
* updated talk to coral on contact page
* added a new v5 auth section
* added session length to auth docs
* added an admin settings page to v5
* added v5 css section
* added a v5 notifications section
* updated faq and troubleshooting, moved out of v4 menu
* added migrating to v5 and moved migrating section out of v4
* added plugins note to migration pg
* fix: linting and extra HTML
* change sidebar migrating v5 to v5.0+
Co-Authored-By: Wyatt Johnson <wyattjoh@gmail.com>
* downtime being likely is too optimistic, it will be required
Co-Authored-By: Wyatt Johnson <wyattjoh@gmail.com>
* rewords plugins note on migrating to v5
Co-Authored-By: Wyatt Johnson <wyattjoh@gmail.com>
* tag code block as html
Co-Authored-By: Wyatt Johnson <wyattjoh@gmail.com>
* added link to contributing
* rephrased openid connect description
* fixed link to contributing
* correcting descriptions of email auth behavior
Co-Authored-By: Wyatt Johnson <wyattjoh@gmail.com>
* Adding link to css classnames
Co-Authored-By: Wyatt Johnson <wyattjoh@gmail.com>
* renamed new auth to Social and Email Authentication
* pulled extra line breaks
Co-authored-by: Wyatt Johnson <accounts+github@wyattjoh.ca>
* Update version-5-installation.md
The command `npm run start` doesn't work locally following these directions, but `npm run start:development` does. Based on the package.json commands, the `:development` command seems reasonable:
```
"start": "NODE_ENV=production node dist/index.js",
"start:development": "NODE_ENV=development CONCURRENCY=${CONCURRENCY:-1} TS_NODE_PROJECT=./src/tsconfig.json ts-node-dev --inspect --transpile-only --no-notify -r tsconfig-paths/register ./src/index.ts",
```
Here's the output I received from `npm run start`:
```
Hanss-MBP:talk [redacted]$ npm run start
> @coralproject/talk@5.4.0 start /Users/[redacted]/workspace/talk
> NODE_ENV=production node dist/index.js
{"name":"coral","clusterNode":"master","hostname":"[redacted].com","pid":25656,"level":50,"err":{"message":"SIGNING_SECRET is required in production environments","name":"Error","stack":"new Server (src/core/server/index.ts:126:15)\nObject.createCoral [as default] (src/core/index.ts:10:10)\nbootstrap (src/index.ts:76:20)\nObject.bootstrap (src/index.ts:109:1)\nModule._compile (internal/modules/cjs/loader.js:959:30)\nObject.Module._extensions..js (internal/modules/cjs/loader.js:995:10)\nModule.load (internal/modules/cjs/loader.js:815:32)\nFunction.Module._load (internal/modules/cjs/loader.js:727:14)\nFunction.Module.runMain (internal/modules/cjs/loader.js:1047:10)\ninternal/main/run_main_module.js:17:11\n"},"msg":"can not bootstrap server","time":"2019-12-20T23:27:38.314Z","src":{"file":"/Users/[redacted]/workspace/talk/src/index.ts","line":104,"func":"error"},"v":0}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @coralproject/talk@5.4.0 start: `NODE_ENV=production node dist/index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @coralproject/talk@5.4.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/[redacted]/.npm/_logs/2019-12-20T23_27_38_335Z-debug.log
```
* fix: expanded on docs
Co-authored-by: Wyatt Johnson <accounts+github@wyattjoh.ca>
