The New Relic Partner Enablement Microsite is here to enable partners with their practical New Relic knowledge.
Public site is intended to be the default access
We would love to have you contribute content to the microsite. We are accepting pull requests.
npm i to install the dependencies
gatsby develop to run this repository locally - http://localhost:8000
npm build to build the gatsby site
First, have had a local build. Then:
pip install awscli
aws configureModify package.json to include the name of your s3 bucket.
That is essentially all! There are also Gatsby docs - npm package is already included in this repo.
That's pretty much it! Then npm run build && npm run deploy
Following the above instructions and being a member of the AWS ES Org (no need to change s3 bucket).
If you're a Relic wishing to submit new content, you should enter a pull request and not perform a remote build.
The s3 bucket has an associated Cloudfront distribution which in turn has a Route 53 hosted zone and record. Changes to the bucket will directly go to the hosted zone.
Slack'ing gspencer is the preferred approach - but you can do a remote build if Gary is out and you really need to.
New Relic hosts and moderates an online forum where customers can interact with New Relic employees as well as other customers to get help and share best practices. Like all official New Relic open source projects, there's a related Community topic in the New Relic Explorers Hub. You can find this project's topic/threads here:
We encourage your contributions to improve [project name]! Keep in mind when you submit your pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. You only have to sign the CLA one time per project. If you have any questions, or to execute our corporate CLA, required if your contribution is on behalf of a company, please drop us an email at opensource@newrelic.com.
As noted in our security policy, New Relic is committed to the privacy and security of our customers and their data. We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals.
If you believe you have found a security vulnerability in this project or any of New Relic's products or websites, we welcome and greatly appreciate you reporting it to New Relic through HackerOne.
The New Relic Partner Enablement Microsite is licensed under the Apache 2.0 License.
The NR1 App Buildert also uses source code from third-party libraries. You can find full details on which libraries are used and the terms under which they are licensed in the third-party notices document.