Forking the Github repo

You can connect your Render.com server instance to the USDR repo for the Cares-Reporter project, or you can fork the Cares-Reporter project and connect your Render.com server instance to your fork.

Benefits:

You control when updates happen to your instance.

You can make custom changes unique to your state.

Downside:

USDR's improvements don't happen automatically to your instance - you have to do a merge by hand.

How-to:

1. Fork the USDR Cares-Reporter repo
2. Configure the USDR Cares-Reporter repo as the upstream - see https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/syncing-a-fork
3. Configure notifications so you know when to update your fork - see https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository