Merge branch 'master' into ai-community-answers

README.md

@@ -100,15 +100,26 @@ Additional environment variables are needed to develop the merch store:
 
 Currently, these environment variables are excluded from Vercel preview builds to disable merch store node creation and speed up build times on non-merch related PRs.
 
+### Dynamic open graph images
+
+To develop a dynamic open graph image:
+
+1. Run `yarn build` with both the `ASHBY_API_KEY` and `GITHUB_API_KEY` set.
+1. In `gatsby/onPostBuild.ts`, temporarily comment out the following:
+    ```
+    if (process.env.VERCEL_GIT_COMMIT_REF !== 'master') return
+    ```
+1. Find the generated open graph image in `public/og-images/`
+
 ## Contributing
 
 We <3 contributions big and small. In priority order (although everything is appreciated) with the most helpful first:
 
 - Ask a [question in our community](https://posthog.com/questions)
 - Submit [bug reports and give us feedback in the app](https://app.posthog.com/home#supportModal)! 
-- Vote on features or get early access to beta functionality in our [roadmap](https://posthog.com/roadmap)
+- Vote on features or get early access to beta functionality in our [roadmap](https://posthog.com/roadmap)
 - Open a PR
-    - Read [our instructions above](#quick-start) on developing PostHog.com locally
+    - Read [our instructions above](#quick-start) on developing PostHog.com locally
     - Read more [detailed instructions in our manual](https://posthog.com/handbook/engineering/posthog-com/developing-the-website)
     - For basic edits, go to the file in GitHub and click the edit button (pencil icon)
 - Open [an issue](https://github.com/PostHog/posthog.com/issues/new) or [content idea](https://github.com/PostHog/posthog.com/issues/new?assignees=andyvan-ph&labels=content&template=blog-post-idea-template.md&title=%7BContent+type%7D+-+%7Btitle%7D)

contents/blog/how-we-improved-feature-flags-resiliency.md

@@ -20,7 +20,7 @@ Contrast it with the PostHog interface not loading, where the problem is constra
 
 Further, flags are very sensitive to latency. If it takes 5 seconds for your flags to evaluate, that holds up your customer's application for 5 seconds. You can't wait to load them asynchronously, either, as you need this result to determine what to show. Your business logic depends on the flag.
 
-This is why the [Feature Success team](/teams/feature-success) has spent the last few months making PostHog's feature flags fast and resilient. Our goal was to ensure that:
+This is why the [Feature Flags team](/teams/feature-flags) has spent the last few months making PostHog's feature flags fast and resilient. Our goal was to ensure that:
 
 1. Neither the SDKs that query flags, nor the API interface, should go down if the PostHog interface does
 2. Latency-sensitive flags resolve in 50ms or less. 

contents/blog/posthog-vs-ga4.mdx

@@ -201,7 +201,7 @@ With PostHog, it's free to get started, with a generous monthly allowance of eve
 
 ### Can I migrate from Google Analytics to PostHog?
 
-Yes, see our [Google Analytics to PostHog migration guide](/migrate/google-analytics) for more details.
+Yes, see our [Google Analytics to PostHog migration guide](/docs/migrate/google-analytics) for more details.
 
 ### Does PostHog block bots by default?
 

contents/blog/what-is-a-growth-engineer.md

@@ -126,7 +126,7 @@ Growth engineers help your overall business by helping all products grow faster.
 
 We've seen this from our growth team. Building cross-product features, like billing, has improved our overall business and user experience. These features don't fit into a specific product team's responsibility and would be missed out on if growth engineers didn't exist.
 
-Growth engineers likely won't help you find traction, they need products to connect and optimize to thrive. Once you have traction, it might be the right time to hire a growth engineer to fuel rapid growth.
+Growth engineers likely won't help you find traction, they need products to connect and optimize to thrive. Once you have traction, it might be the right time to hire a [growth engineer](/newsletter/think-like-a-growth-engineer) to fuel rapid growth.
 
 From our experience, we'd recommend the technical and entreprenuerial growth engineer, this often arises in former founders. Later-stage teams often find success with larger growth teams, and more marketing-focused roles, but we haven't made it that far yet. 
 

contents/docs/advanced/proxy.mdx

@@ -28,6 +28,7 @@ Options for deploying a reverse proxy include:
 - [Netlify](/docs/advanced/proxy/netlify)
 - [Next.js rewrites](/docs/advanced/proxy/nextjs)
 - [Next.js middleware](/docs/advanced/proxy/nextjs-middleware)
+- [nginx](/docs/advanced/proxy/nginx)
 - [Vercel](/docs/advanced/proxy/vercel)
 - [Nuxt](/docs/advanced/proxy/nuxt)
 

contents/docs/advanced/proxy/nginx.mdx

@@ -0,0 +1,54 @@
+---
+title: Using nginx as a reverse proxy
+sidebar: Docs
+showTitle: true
+---
+
+import RegionWarning from "../_snippets/region-warning.mdx"
+
+<RegionWarning />
+
+You can use nginx as a reverse proxy. To do this, first create a `Dockerfile` to build a nginx container:
+
+```dockerfile
+FROM nginx:alpine
+COPY nginx.conf /etc/nginx/nginx.conf
+```
+
+Next, create the `nginx.conf` file with the reverse proxy configuration. The following checks the `Referer` header to ensure the request is coming from your domain (set as `hogbook.com` in this case), then proxies the request to PostHog Cloud US. Change `us` to `eu` to proxy to our EU Cloud.
+
+```nginx.conf
+# The main context
+events {
+    worker_connections 1024;
+}
+
+http {
+    server {
+        listen 8080;  # Set the port to 8080
+
+        server_name _;  # Accept requests for any domain
+
+        # Check Referer header
+        # Change hogbook to your domain as needed to ensure requests only come from your domain
+        set $valid_referer 0;
+        if ($http_referer ~* "^https?://(localhost|([a-zA-Z0-9-]+)\.hogbook\.com)") {
+            set $valid_referer 1;
+        }
+
+        if ($valid_referer = 0) {
+            return 403;  # Return forbidden if the Referer header is invalid
+        }
+
+        location /static/ {
+            proxy_pass https://us-assets.i.posthog.com/static/;
+            proxy_set_header Host us-assets.i.posthog.com;
+        }
+
+        location / {
+            proxy_pass https://us.i.posthog.com/;
+            proxy_set_header Host us.i.posthog.com;
+        }
+    }
+}
+```

contents/docs/ai-engineering/tutorials.mdx

@@ -13,6 +13,7 @@ Got a question which isn't answered below? Head to [the community forum](/questi
 - [How to set up LLM analytics for ChatGPT](/tutorials/chatgpt-analytics)
 - [How to monitor generative AI calls to AWS Bedrock](/tutorials/monitor-aws-bedrock-calls)  
 - [How to compare AWS Bedrock prompts](/tutorials/compare-aws-bedrock-prompts)
+- [How to compare AWS Bedrock foundational models](/tutorials/compare-aws-bedrock-foundational-models)
 
 ## Using LLMs in analytics
 

contents/docs/api/projects/create_2.mdx

@@ -0,0 +1,3 @@
+In most cases, we recommend using a single project across your product, but if you want to programmatically create multiple projects, this is the endpoint for you.
+
+To get your organization ID, use the `/api/organizations/@current` endpoint or check the endpoint directly on [US Cloud](https://us.posthog.com/api/organizations/@current) or [EU Cloud](https://eu.posthog.com/api/organizations/@current).

contents/docs/api/projects/list_2.mdx

@@ -0,0 +1,3 @@
+Returns a list of projects in your organization.
+
+To get your organization ID, use the `/api/organizations/@current` endpoint or check the endpoint directly on [US Cloud](https://us.posthog.com/api/organizations/@current) or [EU Cloud](https://eu.posthog.com/api/organizations/@current).

contents/docs/billing/common-questions.md

@@ -14,7 +14,11 @@ You can check our doc on [estimating usage and costs](/docs/billing/estimating-u
 
 ### How do I update billing information or see previous months' invoices or usage?
 
-Go to your organization's [billing settings](https://app.posthog.com/organization/billing) and click "Manage card details" to be brought to Stripe where you can update your credit card, billing information, and see your invoice history.
+Go to your organization's [billing settings](https://app.posthog.com/organization/billing) and click **Manage card details and view past invoices** to be brought to Stripe where you can update your credit card, billing information, and see your invoice history.
+
+You can also download invoices or receipts from here by clicking on them under **Invoice history**.
+
+![Invoices](https://res.cloudinary.com/dmukukwp6/image/upload/Clean_Shot_2024_09_19_at_16_44_05_2x_1c2cc687c2.png)
 
 ### Can I set a billing limit?
 

contents/docs/cdp/_snippets/feedback-questions.mdx

@@ -1,6 +1,6 @@
 ### What if I have feedback on this destination?
 
-We love feature requests and feedback. Please [tell us what you think](http://app.posthog.com/home#supportModal)..
+We love feature requests and feedback. Please [tell us what you think](https://us.posthog.com/#panel=support%3Afeedback%3Aapps%3Alow%3Atrue)..
 
 ### What if my question isn't answered above?
 

contents/docs/cdp/_snippets/posthog-maintained.mdx

@@ -1,3 +1,3 @@
 ### Who maintains this?
 
-This is maintained by PostHog. If you have issues with it not functioning as intended, please [let us know](http://app.posthog.com/home#supportModal)!
+This is maintained by PostHog. If you have issues with it not functioning as intended, please [let us know](https://us.posthog.com/#panel=support%3Asupport%3Aapps%3A%3Atrue)!

contents/docs/cdp/_snippets/requirements.mdx

@@ -1,5 +1,3 @@
 ## Requirements
 
-Using this requires either PostHog Cloud with the [data pipeline add-on](https://us.posthog.com/organization/billing), or a self-hosted PostHog instance running [version 1.30.0](/blog/the-posthog-array-1-30-0) or later.
-
-Self-hosting and not running 1.30.0? Find out [how to update your self-hosted PostHog deployment](/docs/runbook/upgrading-posthog).
+Using this requires either PostHog Cloud with the [data pipelines add-on](https://us.posthog.com/organization/billing), or a self-hosted PostHog instance running a recent version of the Docker image.