Skip to content

Commit

Permalink
Update publish
Browse files Browse the repository at this point in the history
- Fix language
- Update relative links
  • Loading branch information
alexronquillo committed Apr 28, 2021
1 parent 816a029 commit 166a3b4
Showing 1 changed file with 13 additions and 5 deletions.
18 changes: 13 additions & 5 deletions src/markdown-pages/build-apps/serve-publish-subscribe/publish.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ nr1 nerdpack:uuid --generate --force

<Callout variant="tip">

Read the [`nr1 nerdpack:uuid`](../../../explore-docs/nr1-nerdpack#nr1-nerdpackuuid) documentation to learn more. Or, view the `nr1` help page:
Read the [`nr1 nerdpack:uuid`](/explore-docs/nr1-nerdpack#nr1-nerdpackuuid) documentation to learn more. Or, view the `nr1` help page:

```sh
nr1 nerdpack:uuid --help
Expand Down Expand Up @@ -152,7 +152,7 @@ Because you're going to view a published Nerdpack, rather than a locally served

Navigate to **Apps**:

![Navigate to Apps page](../../../images/serve-publish-subscribe/nav-to-apps.png)
![Navigate to the Apps page](../../../images/serve-publish-subscribe/nav-to-apps.png)

Whether you published a New Relic One application or a custom visualization, you'll find your project under **Apps**.

Expand Down Expand Up @@ -180,7 +180,7 @@ Only apps and visualizations with tagged versions are shown under **New Relic On

Sometimes, when you publish your Nerdpack, you may come across issues. Whether you can't publish your Nerdpack due to some issue with your code or you can't find your Nerdpack in the catalog, consider some common solutions for resolving these issues.

### Debug your application
### Debug your command

When you attempt to publish your Nerdpack, carefully read the output of your `nr1` command. You may receive success output, including:

Expand All @@ -189,7 +189,15 @@ When you attempt to publish your Nerdpack, carefully read the output of your `nr
[output] {green}✔{normal} Tagged {purple}ab123c45-678d-9012-efg3-45hi6jkl7890{normal} version {blue}1.0.0{normal} as {blue}STABLE{normal}.
```

However, the output may show some errors in your Nerdpack instead. It may also help you to view more verbose output. Use the `--verbose` command to show more content:
However, the output may show some errors in your Nerdpack instead. For example:

```sh
[output] Publishing Nerdpack DemoApp ({purple}ab123c45-678d-9012-efg3-45hi6jkl7890{normal})
[output] {error}›{normal} Error: There is already a Nerdpack with given id & version.
[output] {error}›{normal} Code: 409
```

It may also help you to view more verbose output. Use the `--verbose` command to show more content:

```sh
nr1 nerdpack:publish --verbose
Expand Down Expand Up @@ -229,6 +237,6 @@ Read our [`nr1 nerdpack:tag`](/explore-docs/nr1-nerdpack#nr1-nerdpacktag) docume

## Check your local profile

With `nr1`, you can [set a default New Relic profile](../../../explore-docs/nr1-common#nr1-profiles). This profile is used for all commands unless otherwise specified with the command's `--profile` option. When you publish your Nerdpack, only users who can access your account can see your published Nerdpack.
With `nr1`, you can [set a default New Relic profile](/explore-docs/nr1-common#nr1-profiles). This profile is used for all commands unless otherwise specified with the command's `--profile` option. When you publish your Nerdpack, only users who can access your account can see your published Nerdpack.

So, if you don't find your app or visualization in New Relic but you know it's published, compare your local profile with the profile you're using in the browser to make sure they're the same.

0 comments on commit 166a3b4

Please sign in to comment.