docs: load Plausible on invoke.ai (custom), not ghpages

[Pfannkuchensack]

Summary

Plausible was being injected on the ghpages target, which redirects to invoke.ai and therefore never serves analytics. Flip the conditional so the script loads on the actual production custom-domain build.

Merge Plan

This only applies to the invoke.ai website.

Checklist

• The PR has a short but descriptive title, suitable for a changelog
• Tests added / updated (if applicable)
• ❗Changes to a redux slice have a corresponding migration
• Documentation added / updated (if applicable)
• Updated What's New copy (if doing a release after this PR)

[joshistoast]

Wouldn't this show plausible on local?

[Pfannkuchensack]

Right now it is not working on invoke.ai and yes that would also show on local.

[joshistoast]

The best approach may be setting an env variable in the deploy action ENABLE_ANALYTICS to true, and checking that in the config.

Something along the lines of:

const enableAnalytics = process.env.ENABLE_ANALYTICS === 'true';

That way only a deployment would get tracked, unless of course someone strips the config condition, runs a build and bombards the endpoint.

UPDATE: I'd assume plausible only accepts requests from the configured domain? If so then I don't think what I said above matters too much.

[joshistoast]

No notes on the rest, made a code suggestion for keeping analytics on manual pushes