[PR]: Add Analytics and vercel setup. #14
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #13
I couldn't get
nextra-demo
to publish to Github Pages because it's not a fully static website (it hasmiddleware.ts
for authentication) - see https://nextjs.org/docs/app/building-your-application/deploying/static-exports#unsupported-features.So, I created a fork and deployed it to my personal Vercel account.
I know we can't deploy on Vercel as
dwyl
because you have to pay to be able to do it because this repo is inside an organization. But I believe this is going to be a pain to keep the Vercel site updated while PRs are being made to this repo, because my fork https://github.com/LuchoTurtle/nextra-demo will only be updated when PRs are pushed into itsmain
.I digress.
This works (I inclusively tested on
localhost
with https://analytics.dwyl.com and it's working fine).To appear on https://analytics.dwyl.com, we have to add nextra-demo-seven.vercel.app as a site to it and it will start tracking (after I deploy the site with these changes on my end once this PR is merged).