ComputerSurge/shields
3
0
Fork 0
Code Pull Requests 1 Activity

Add support for private [npm] packages (#2187)

Browse Source
This commit is contained in:
Ted Janeczko
2018-10-20 03:06:36 -04:00
committed by Pierre-Yves B
parent 32b123671c
commit a6fe16c5d1
3 changed files with 22 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
doc/self-hosting.md
View File

@@ -144,10 +144,12 @@ will have access to your private repositories.
When a `gh_token` is specified, it is used in place of the Shields token
rotation logic.
You can also give your self-hosted Shields installation access to private npm
packages by [generating an npm token] and using that for the `npm_token` value.
[github rate limit]: https://developer.github.com/v3/#rate-limiting
[personal access tokens]: https://github.com/settings/tokens
[generating an npm token]: https://docs.npmjs.com/getting-started/working_with_tokens
Separate frontend hosting
-------------------------
@@ -189,9 +191,9 @@ In order to enable integration with [Sentry](https://sentry.io), you need your o
### How to obtain the Sentry DSN
1. [Sign up](https://sentry.io/pricing/) for Sentry
1. Log in to Sentry
1. Create a new project for Node.js
1. You should see [Sentry DSN](https://docs.sentry.io/quickstart/#configure-the-dsn) for your project. Sentry DSN can be found by navigating to \[Project Name] -> Project Settings -> Client Keys (DSN) as well.
2. Log in to Sentry
3. Create a new project for Node.js
4. You should see [Sentry DSN](https://docs.sentry.io/quickstart/#configure-the-dsn) for your project. Sentry DSN can be found by navigating to \[Project Name] -> Project Settings -> Client Keys (DSN) as well.
Start the server using the Sentry DSN. You can set it:
- by `SENTRY_DSN` environment variable