ref: Various cleanup (#2355)

- Remove ORG_NAME and PROJECT_NAME as they create confusion
- Add ORG_INGEST_DOMAIN
- Remove useless config in webpack example

Author: dcramer

src/components/codeContext.tsx

@@ -7,11 +7,10 @@ type ProjectCodeKeywords = {
   SECRET_KEY: string;
   API_URL: string;
   PROJECT_ID: number;
-  PROJECT_NAME: string;
   PROJECT_SLUG: string;
   ORG_ID: number;
-  ORG_NAME: string;
   ORG_SLUG: string;
+  ORG_INGEST_DOMAIN: string;
   MINIDUMP_URL: string;
   UNREAL_URL: string;
   title: string;
@@ -51,11 +50,10 @@ const DEFAULTS: CodeKeywords = {
       SECRET_KEY: "exampleSecretKey",
       API_URL: "https://sentry.io/api",
       PROJECT_ID: 0,
-      PROJECT_NAME: "example-project",
       PROJECT_SLUG: "example-project",
       ORG_ID: 0,
-      ORG_NAME: "example-org",
       ORG_SLUG: "exmaple-org",
+      ORG_INGEST_DOMAIN: "o0.ingest.sentry.io",
       MINIDUMP_URL: "https://examplePublicKey@o0.ingest.sentry.io/0",
       UNREAL_URL: "https://examplePublicKey@o0.ingest.sentry.io/0",
       title: `example-org / example-project`,
@@ -115,11 +113,10 @@ export function fetchCodeKeywords() {
               SECRET_KEY: parsedDsn.secretKey,
               API_URL: formatApiUrl(parsedDsn),
               PROJECT_ID: project.id,
-              PROJECT_NAME: project.projectSlug,
               PROJECT_SLUG: project.projectSlug,
               ORG_ID: project.organizationId,
-              ORG_NAME: project.organizationSlug,
               ORG_SLUG: project.organizationSlug,
+              ORG_INGEST_DOMAIN: `o${project.organizationId}.ingest.sentry.io`,
               MINIDUMP_URL: formatMinidumpURL(parsedDsn),
               UNREAL_URL: formatUnrealEngineURL(parsedDsn),
               title: `${project.organizationSlug} / ${project.projectSlug}`,

src/docs/product/security-policy-reporting.mdx

@@ -18,13 +18,13 @@ The integration process consists of configuring the appropriate header with your
 To configure CSP reports in Sentry, you’ll need to send a header from your server describing your policy, as well specifying the authenticated Sentry endpoint:
 
 ```
-Content-Security-Policy: ...; report-uri https://o___ORG_ID___.ingest.sentry.io/api/___PROJECT_ID___/security/?sentry_key=___PUBLIC_KEY___
+Content-Security-Policy: ...; report-uri https://___ORG_INGEST_DOMAIN___/api/___PROJECT_ID___/security/?sentry_key=___PUBLIC_KEY___
 ```
 
 Alternatively you can setup CSP reports to simply send reports rather than actually enforcing the policy:
 
 ```
-Content-Security-Policy-Report-Only: ...; report-uri https://o___ORG_ID___.ingest.sentry.io/api/___PROJECT_ID___/security/?sentry_key=___PUBLIC_KEY___
+Content-Security-Policy-Report-Only: ...; report-uri https://___ORG_INGEST_DOMAIN___/api/___PROJECT_ID___/security/?sentry_key=___PUBLIC_KEY___
 ```
 
 For more information, see the article on [MDN](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy).
@@ -36,7 +36,7 @@ For more information, see the article on [MDN](https://developer.mozilla.org/en-
 To configure reports in Sentry, you’ll need to configure the Expect-CT a header from your server:
 
 ```
-Expect-CT: ..., report-uri="https://o___ORG_ID___.ingest.sentry.io/api/___PROJECT_ID___/security/?sentry_key=___PUBLIC_KEY___"
+Expect-CT: ..., report-uri="https://___ORG_INGEST_DOMAIN___/api/___PROJECT_ID___/security/?sentry_key=___PUBLIC_KEY___"
 ```
 
 For more information, see the article on [MDN](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Expect-CT).
@@ -48,7 +48,7 @@ For more information, see the article on [MDN](https://developer.mozilla.org/en-
 To configure HPKP reports in Sentry, you’ll need to send a header from your server describing your policy, as well specifying the authenticated Sentry endpoint:
 
 ```
-Public-Key-Pins: ...; report-uri="https://o___ORG_ID___.ingest.sentry.io/api/___PROJECT_ID___/security/?sentry_key=___PUBLIC_KEY___"
+Public-Key-Pins: ...; report-uri="https://___ORG_INGEST_DOMAIN___/api/___PROJECT_ID___/security/?sentry_key=___PUBLIC_KEY___"
 ```
 
 For more information, see the article on [MDN](https://developer.mozilla.org/en-US/docs/Web/HTTP/Public_Key_Pinning).

src/platforms/javascript/common/sourcemaps/index.mdx

@@ -63,7 +63,6 @@ module.exports = {
 
         // webpack specific configuration
         include: ".",
-        ignoreFile: ".sentrycliignore",
         ignore: ["node_modules", "webpack.config.js"],
       }),
     ],

src/platforms/javascript/common/sourcemaps/tools/webpack.mdx

@@ -32,7 +32,6 @@ module.exports = {
 
         // webpack specific configuration
         include: ".",
-        ignoreFile: ".sentrycliignore",
         ignore: ["node_modules", "webpack.config.js"],
       }),
     ],

src/platforms/javascript/common/sourcemaps/troubleshooting_js.mdx

@@ -1,7 +1,7 @@
 ---
 title: Troubleshooting
 redirect_from:
-- /platforms/javascript/sourcemaps/troubleshooting/
+  - /platforms/javascript/sourcemaps/troubleshooting/
 ---
 
 Source maps can sometimes be tricky to get going. If you’re having trouble:
@@ -104,7 +104,7 @@ You can alternately [use our API](/api/releases/post-organization-release-files/
 
 ```shell
 curl -X POST \
-  https://sentry.io/api/0/organizations/ORG_NAME/releases/VERSION/files/ \
+  https://sentry.io/api/0/organizations/ORG_SLUG/releases/VERSION/files/ \
   -H 'Authorization: Bearer AUTH_TOKEN' \
   -H 'content-type: multipart/form-data' \
   -F file=@script.min.js.map \