v0.3.0 — settings by scope

What's Changed

• Put the how-to on the page the banner sends people to by @nitinhayaran in #14
• Split the console by what each thing actually belongs to by @nitinhayaran in #16
• Call this 0.3.0 by @nitinhayaran in #17

Full Changelog: v0.2.1...v0.3.0

Updating to this release

Your Edgemetry is its own repository — the deploy button imported this one
rather than forking it, so GitHub gives you no Sync fork button.

In your copy: Actions → Update Edgemetry → Run workflow, then merge the
pull request it opens. Merging is what deploys. Your data and your Cloudflare
configuration are untouched — they live in D1 and in Cloudflare, not in the
repository.

No such workflow? Your copy predates it, and needs one manual update to get
it. From a clone of your repository:

git remote add upstream https://github.com/hayaran/Edgemetry.git
git fetch upstream main
git reset --hard upstream/main
git reset --soft origin/main
git commit -m "Update Edgemetry"
git push

That takes upstream's files as one ordinary commit on your own history, which
is what makes it apply cleanly to a repository that shares no history with
this one. It replaces every tracked file, so read the diff first if you have
edited any.

Full detail in the README