Skip to content

Commit

Permalink
no idea why I put that line about testing puppeteer in prod
Browse files Browse the repository at this point in the history
  • Loading branch information
solderq35 authored Oct 20, 2023
1 parent 2d5d7c1 commit 8749804
Showing 1 changed file with 0 additions and 1 deletion.
1 change: 0 additions & 1 deletion website/docs/webscraper_tutorial.md
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,6 @@ See [this page on Cloudwatch](./cloudwatch.md) as well for more information
- [https://github.com/OSU-Sustainability-Office/energy-dashboard/blob/master/backend/dependencies/nodejs/models/meter.js#L141](https://github.com/OSU-Sustainability-Office/energy-dashboard/blob/master/backend/dependencies/nodejs/models/meter.js#L141)
- [https://github.com/OSU-Sustainability-Office/energy-dashboard/blob/master/backend/app/meter.js#L88](https://github.com/OSU-Sustainability-Office/energy-dashboard/blob/master/backend/app/meter.js#L88)
- `API_PWD` in automated-jobs env file = `AQUISUITE_PWD` value that the energy-dashboard backend expects as part of the payload
- Again, should push backend energy-dashboard changes to production if you need to test upload with puppeteer
- AWS ECR and ECS
- Inspect Element > Network > see the network request sent starting with “data…”
- **If you just want to make an update to the webscraper, you just need to push changes to ECR and not ECS. ECS should be configured to pick up the latest ECR revision anyways**
Expand Down

0 comments on commit 8749804

Please sign in to comment.