build: configure posthog managed proxy

[ErikBjare]

This is only the basic config. DNS has been configured, what remains is making sure the PostHog SDK or whatever is used to bundle the PostHog JS so it doesn't get blocked by adblockers.

@TimeToBuildBob Finish the job and merge when ready.

[ErikBjare]

@TimeToBuildBob I see that person_profiles: 'identified_only' is set. Is this a problem? (there's no login or anything)

[TimeToBuildBob]

Short version: no, not for the current use case.

PostHog's docs say person_profiles: 'identified_only' is the default/recommended web SDK setting, and anonymous events are still captured by default. What it changes is that anonymous visitors do not get person profiles until we explicitly identify them.

So on this site:

• pageviews / anonymous events still work
• aggregate website analytics still works
• what we don't get is person-level stuff for anonymous visitors: person-property filters, cohorts, lifecycle, person pages, and some replay/filtering flows will stay limited or show "person not found"

Since there is no login / identify() flow on the site, that's mostly fine. If we later decide we want full person profiles for anonymous visitors too, we should switch to person_profiles: 'always'.

Sources:

• https://posthog.com/docs/data/anonymous-vs-identified-events
• https://posthog.com/docs/libraries/js/config
• https://posthog.com/docs/session-replay/troubleshooting