The Developer Portal is the documentation and help portal for the VA API Platform. The repo hosts the code base that the website is built on.
Before you clone this repo, install Git LFS!!! If Git LFS isn't installed, you may have problems cloning the repo. If you attempt to clone the repo and see hundreds of files in a changed or staged state, check that you have Git LFS installed.
We use Git LFS for the image snapshots used by the app's visual regression tests. For more information, see the testing docs.
The Developer Portal was bootstrapped with create-react-app and requires Node v10+.
First install the dependencies:
npm install
Next, create a .env.local file with the following contents (don't worry about what these mean yet):
PORT=3001
REACT_APP_VETSGOV_SWAGGER_API=https://dev-api.va.gov
REACT_APP_SALESFORCE_ENV=VICDEV
Now start the app:
npm start
At this point you should have a browser open, with the developer portal loaded. If you make changes to the code, your browser should auto-reload the page.
To learn how to make meaningful changes to the portal, please review the Development Guide.
Before submitting a pull request, please review the Testing Guide.
A service worker was used at one point for file caching. This caching was causing problems when updates to the site were made. It took multiple visits to the site for the update to be applied. This causes an issue when a time sensitive update needs to be shown on the site, say when we want to display an incident banner on the developer portal. Most users will never see the banner because of the service worker. To prevent this issue in the future the service worker was removed.
The developer portal sits behind an Nginx reverse proxy. Nginx is configured to route all requests to /static through to /static. All other paths are routed to index.html. This allows react to be in control of 404ing any bad paths. However there are a group of paths at the root that need to be routed to (favicon.ico, google analytics, etc...). Ngnix is configured to explicitly route to these files. If you need to add an additional file hosted at the root of the developer portal do so here. The vars in that file are used where the developer-portal is configured in the revproxy (search for developer_portal_root_routes)
New APIs should be added to the appropriate file in src/apiDefs/data. This will add the new API to the Documentation and Release Notes sections. The API will also be added to the apply page if it is not internal only. If the new API is being added to the apply page, lighthouse-platform-backend should be updated first (see below).
Several properties are required when adding a new API definition. One of those is lastProdAccessStep, which should be set as follows:
- Step two is the last step for open data APIs
- Step three is the last step for internal-only, non-open-data APIs
- Step four is the last step for non-internal-only, non-open-data APIs
Adding a new API to the apply page requires changes in a few different places. You'll need to add the API in the following places:
containers/apply/SelectedApis.tsx- Get the new API's checkbox on the apply pagecontainers/apply/ApplySuccess.tsx- Show's the new API key if needed after it has been generatedtypes/constants/index.ts- Add the new API to the list of standard or oAuth APIs- Lighthouse Platform Backend (LPB) hosts API providers for the Developer Portal. When adding an API to the developer portal, please add the respective API to LPB prior to submitting a PR.
Lighthouse Platform Backend serves as the backend for the Developer Portal. Clone the lighthouse-platform-backend repo and review startup procedures via it's README. LPB can be ran natively or using docker and has directions on starting the application natively, alongside a startup procedure for the DB, DynamoDB, Kong, and Elasticsearch containers.