Deprecate some guides

Author: macobo

docs/proxy/guides/akamai.md

@@ -2,94 +2,8 @@
 title: Proxying Plausible through Akamai
 ---
 
-import useBaseUrl from '@docusaurus/useBaseUrl';
-
-Here's how to proxy Plausible through your own property on Akamai. The instructions assume you use the default paths ``/js/script.js`` and ``/api/event``. You can change these based on your preferences.
+We've removed old proxying instructions due to being out of date. [See our general proxying guide](/proxy/introduction).
 
 :::tip Don't want to manage your own proxy? We can handle it for you
 Our managed proxy lets you send analytics through your own domain name as a first-party connection. All you need to do is set up a CNAME record using the instructions we'll send you and update the snippet on your site. We'll take care of everything else. [Contact us for details](https://plausible.io/contact).
 :::
-
-## Step 1: Proxy Analytics Script
-
-This Rule Group serves incoming requests matching ``/js/script.js`` directly from the Akamai edge caches. In case of a cache miss the request is forwarded to ``plausible.io`` in a privacy-friendly way.
-
-### Add new Rule Group 
-
-In Akamai Property Manager add a new Rule Group ``Plausible (Script)`` with these settings:
-
-<img alt="In Akamai Property Manager add a new Rule Group" src={useBaseUrl('img/akamai-script-pm.jpg')} />
-
-### Set Criteria
-
-- Path matches one off: ``/js/script.js``
-
-### Add Behaviour: Caching
-
-- Caching Option: **Cache**
-- Force revalidation of stale objects: **Serve stale if unable to validate**
-- Maxage: ``6 hours``
-
-### Add Behaviour: Origin Server
-
-- Origin Type: **Your origin**
-- Origin Server Hostname: ``plausible.io``
-- Forward Host Header: **Origin Hostname**
-- Cache Key Hostname: **Origin Hostname**
-- Supports Gzip Compression: **Yes**
-- Send True Client IP Header: **No** _(Privacy: No need to expose IP)_
-- Verification Settings: **Choose your own**
-- ... _(Other settings can be left as is)_
-
-## Step 2: Proxy Event API
-
-This Rule Group forwards incoming requests matching ``/api/event`` to plausible.io. It adds extra headers (``X-Forwarded-Proto``, ``X-Forwarded-Host`` and ``X-Forwarded-For``) to the outgoing request, so your Plausible statistics are complete. For privacy & security reasons incoming cookies are removed before sending to ``plausible.io``.
-
-### Add new Rule Group 
-
-In Akamai Property Manager add a new Rule Group ``Plausible (Event API)`` with these settings:
-
-<img alt="Property Manager Rule to proxy the Event API" src={useBaseUrl('img/akamai-api-pm.jpg')} />
-
-### Set Criteria
-
-- Path matches one off: ``/api/event``
-
-### Add Behaviour: Origin Server
-
-- Origin Type: **Your origin**
-- Origin Server Hostname: ``plausible.io``
-- Forward Host Header: **Origin Hostname**
-- Cache Key Hostname: **Origin Hostname**
-- Supports Gzip Compression: **Yes**
-- Send True Client IP Header: **Yes**
-- True Client IP Header Name: ``X-Forwarded-For``
-- Verification Settings: **Choose your own**
-- ... _(Other settings can be left as is)_
-
-<img alt="Property Manager Rules to remove outgoing request headers and cookies" src={useBaseUrl('img/akamai-api-pm-headers.jpg')} />
-
-### Add Behaviour: Modify Outgoing Request Header
-
-- Action: **Add**
-- Header Name: ``X-Forwarded-Proto``
-- Header Value: ``{{builtin.AK_SCHEME}}``
-
-### Add Behaviour: Modify Outgoing Request Header
-
-- Action: **Add**
-- Header Name: ``X-Forwarded-Host``
-- Header Value: ``{{builtin.AK_HOST}}``
-
-### Add Behaviour: Modify Outgoing Request Header
-
-- Action: **Remove**
-- Header Name: ``cookie`` _(Privacy: No need to expose cookies to origin servers)_
-
-### Optional: 
-
-In case you are using SureRoute, please disable it:
-
-<img alt="In case you are using SureRoute, please disable it" src={useBaseUrl('img/akamai-script-sureroute.jpg')} />
-
-Thanks to [Tim Vereecke](https://www.scalemates.com/), Akamai's web performance architect, for these instructions!  

docs/proxy/guides/cloudfront.md

@@ -2,73 +2,8 @@
 title: Proxying Plausible through CloudFront
 ---
 
-import useBaseUrl from '@docusaurus/useBaseUrl';
-
-You can use CloudFront to proxy your Plausible Analytics requests. Here's the step-by-step process for creating a proxy.
+We've removed old proxying instructions due to being out of date. [See our general proxying guide](/proxy/introduction).
 
 :::tip Don't want to manage your own proxy? We can handle it for you
 Our managed proxy lets you send analytics through your own domain name as a first-party connection. All you need to do is set up a CNAME record using the instructions we'll send you and update the snippet on your site. We'll take care of everything else. [Contact us for details](https://plausible.io/contact).
 :::
-
-Step 0: Sign up for a free AWS account if you don't have an account already and create a CloudFront distribution. 
-
-## Step 1: Create new origin
-
-You need to create a new origin pointing to the Plausible server. In the CloudFront console, under your distribution, create a new origin by going into the "**Origins**" section and clicking on "**Create origin**".
-
-1. Set "**Origin domain**" to: `plausible.io`
-2. Set the "**Protocol**" policy to: `HTTPS Only`
-3. You do not need to change any of the other options on this screen
-4. Click on the "**Create origin**" button 
-
-## Step 2: Create behaviors
-
-Now you need to define two behaviors for when to use the new origin. In the CloudFront console, under your distribution, create a new behavior by going into the "**Behavior**" section and clicking on "**Create behavior**".
-
-Create a behavior for the analytics script:
-
-1. Set the "**Path pattern**" to: `/js/script.js` (you can also use `/js/script.*` to match [script extensions](https://plausible.io/docs/script-extensions))
-2. In "**Origin and origin groups**", choose the origin that you created in step 1
-3. Set "**Compress objects automatically**" to: `No`
-4. Set the "**Viewer protocol policy**" to: `HTTPS Only`
-5. Set the "**Allowed HTTP methods**" to: `GET, HEAD`
-6. In "**Cache key and origin requests**", choose "**Legacy cache settings**"
-7. You do not need to change any of the other options on this screen
-8. Click on the "**Create behavior**" button 
-
-And create a behavior for the event API:
-
-1. Set the "**Path pattern**" to: `/api/event`
-2. In "**Origin and origin groups**", choose the origin that you created in step 1
-3. Set "**Compress objects automatically**" to: `No`
-4. Set the "**Viewer protocol policy**" to: `HTTPS Only`
-5. Set the "**Allowed HTTP methods**" to: `GET, HEAD, OPTIONS, PUT, POST, PATCH, DELETE`
-6. In "**Cache key and origin requests**", use the "**Cache policy and origin request policy**"
-7. Set the "**Cache policy**" to: `CachingDisabled`
-8. Set the "**Origin request policy**" to: `UserAgentRefererHeaders`
-9. Set the "**Response headers policy**" to: `SimpleCORS`
-10. You do not need to change any of the other options on this screen
-11. Click on the "**Create behavior**" button 
-
-## Step 3: Integrate a new snippet into your site header
-
-With the origin and behaviours in place, you can replace your Plausible Analytics script tag in the Header (`<head>`) section of your site with the proxied snippet. This is how the new snippet should look like (make sure to edit it to have the correct domain name of your site):
-
-```html
-<script defer data-domain="yourdomain.com" src="/js/script.js"></script>
-```
-
-If you're not using the CloudFront with a custom domain, you'll also need to add a `data-api` attribute to tell the script where the data should be sent. This is how the new snippet should look like in that case (do make sure to edit it to the correct URL of your CloudFront distribution)
-
-```html
-<script defer data-domain="yourdomain.com" data-api="https://YOURDISTRIBUTION.cloudfront.net/api/event" src="https://YOURDISTRIBUTION.cloudfront.net/js/script.js"></script>
-```
-
-Using our extensions such as hash-based routing, revenue or outbound link click tracking? Change the file name from `script.js` to the script you want to use: `script.hash.js`, `script.revenue.js` or `script.outbound-links.js`. Want to use more than one extension? You can chain them like this: `script.hash.revenue.outbound-links.js`.
-
-Deploy these changes to your site. You can verify the proxy is working by opening your network tab. You should see a request to
-`https://yourdomain.com/js/script.js` with status 200 and another one to `https://yourdomain.com/api/event` with status 202.
-
-That's it! You're now counting your website stats using a proxy.
-
-Thanks to [@thomasjsn](https://github.com/thomasjsn) for contributing these instructions!

docs/proxy/guides/deno.md

@@ -2,85 +2,8 @@
 title: Proxying Plausible through Deno Deploy
 ---
 
+We've removed old proxying instructions due to being out of date. [See our general proxying guide](/proxy/introduction).
+
 :::tip Don't want to manage your own proxy? We can handle it for you
 Our managed proxy lets you send analytics through your own domain name as a first-party connection. All you need to do is set up a CNAME record using the instructions we'll send you and update the snippet on your site. We'll take care of everything else. [Contact us for details](https://plausible.io/contact).
 :::
-
-## Step 1: Deploy proxy code
-
-Start by getting a [Deno Deploy](https://deno.com/deploy) account if you don't have one already.
-
-There's a few ways to get code deployed on Deno Deploy. We'll cover two in this section:
-
-- Using Deno Deploy's web interface.
-- Using Deno's runtime CLI.
-
-In both cases, the <span id="proxy-script" style={{scrollMarginTop: "70px"}}>script</span> that you'll need to deploy will look something like this:
-
-```typescript
-const SCRIPT_PATH = "/pap/script.js"
-const EVENT_PATH = "/pap/event"
-
-Deno.serve((request, info) => {
-  if (request.url.endsWith(SCRIPT_PATH)) {
-    return fetch("https://plausible.io/js/plausible.js")
-  } else if (request.url.endsWith(EVENT_PATH)) {
-    const requestClone = new Request(request)
-    requestClone.headers.delete("Cookie")
-    requestClone.headers.set("X-Forwarded-For", info.remoteAddr.hostname)
-    return fetch("https://plausible.io/api/event", requestClone)
-  }
-  return new Response(null, { status: 404 })
-})
-```
-
-Notice that we remove the `Cookie` header as that could contain sensitive information that's best not shared. We also set the value of `X-Forwarded-For` with the user's IP. See the [events API](../../events-api#request-headers) page for more information on header requirements.
-
-Both `SCRIPT_PATH` and `EVENT_PATH` can and should be customised. They should match the paths you'll end up using in the `script` tag you'll add to the site you want analytics on.
-
-### Using Deno Deploy's web interface
-
-Log into Deno Deploy, navigate to the [Projects Overview](https://dash.deno.com/account/projects) page and click on the "New Playground" button:
-
-![Screenshot of Deno Deploy Projects Overview page](/img/proxy-deno-new-playground.png)
-
-This will deploy a new project and present an online text editor with the contents of your project's `main.ts` file. Paste the contents of the [proxy script](#proxy-script) provided above and click on "Save & Deploy":
-
-![Screenshot of Deno Deploy's playground page](/img/proxy-deno-save-and-deploy.png)
-
-### Using Deno's runtime CLI
-
-Assuming you have a local installation of the [Deno runtime](https://docs.deno.com/runtime/manual#install-deno), initialize a new project with the init command:
-
-```shell
-deno init proxy-project-folder
-```
-
-Inside that folder, create a file named `main.ts` with the contents of the [proxy script](#proxy-script) provided above.
-
-To deploy your proxy script, run the following from the project folder:
-
-```shell
-deno deploy
-```
-
-## Step 2: Add script tag to site
-
-After successful deployment, your proxy script will be served from a custom `deno.dev` subdomain. You can confirm that it's working by visiting the URL for the Plausible client-side script:
-
-```
-https://your-deno-subdomain.deno.dev/pap/script.js
-```
-
-If that works, you can go ahead and add the following [script tag](plausible-script.md) to the site you want analytics on:
-
-```html
-<script
-  defer
-  src="https://your-deno-subdomain.deno.dev/pap/script.js"
-  data-api="https://your-deno-subdomain.deno.dev/pap/event"
-  data-domain="your-domain.com"
-></script>
-```
-
-Your single proxy will work with multiple sites; you'll just need to update the `data-domain` attribute for each new site.

docs/proxy/guides/fastly.md

@@ -2,89 +2,8 @@
 title: Proxying Plausible through Fastly
 ---
 
-import useBaseUrl from '@docusaurus/useBaseUrl';
-
-You can use Fastly to proxy your Plausible Analytics requests. Here's the step-by-step process for creating a proxy.
+We've removed old proxying instructions due to being out of date. [See our general proxying guide](/proxy/introduction).
 
 :::tip Don't want to manage your own proxy? We can handle it for you
 Our managed proxy lets you send analytics through your own domain name as a first-party connection. All you need to do is set up a CNAME record using the instructions we'll send you and update the snippet on your site. We'll take care of everything else. [Contact us for details](https://plausible.io/contact).
 :::
-
-## Step 1: Create the Backend for Plausible
-
-First, set up a Plausible backend:
-
-1. Go to your Fastly service configuration
-2. Click on "**Origins**" or "**Hosts**"
-3. Click "**Create a host**"
-4. Fill in:
-
-* Name: `Plausible`
-* Address: `plausible.io`
-* Port: `443`
-* Enable SSL: `Checked`
-* Verify certificate: `Checked`
-* SNI hostname: `plausible.io`
-
-5. Set the timeouts:
-
-* First byte timeout: `15000` (15 seconds)
-* Between bytes timeout: `10000` (10 seconds)
-
-6. Save
-
-## Step 2: Create VCL Snippet
-
-Snippet 1: Plausible Request Routing (`vcl_recv`)
-
-1. Go to "**VCL Snippets**"
-2. Click "**Create snippet**"
-3. Fill in:
-
-* Name: `Plausible Request Routing`
-* Type: `recv (vcl_recv)`
-* Priority: `100` (or any number that ensures this runs before your other recv snippets)
-
-4. Add this VCL (Varnish Configuration Language):
-
-```
-vcl
-
-if (req.url ~ "^/plsbl/.*") {
-
-# Remove our prefix for the backend request
-set req.url = regsub(req.url, "^/plsbl", "");
-
-# Set the backend to Plausible
-set req.backend = F_Plausible;
-
-# Set host header to plausible.io
-set req.http.host = "plausible.io";
-
-return(pass);
-}
-```
-
-5. Save
-
-## Step 3: Integrate a new snippet into your site header
-
-You can now replace your Plausible Analytics script tag in the Header (`<head>`) section of your site with the proxied snippet. This is how the new snippet should look like (make sure to edit it to have the correct domain name of your site):
-
-```html
-<script defer data-domain="yourdomain.com" src="/js/script.js"></script>
-```
-
-In case of a subdirectory installation, you'll also need to add a `data-api` attribute to tell the script where the data should be sent.
-
-```html
-<script defer data-domain="yourdomain.com" data-api="/plsbl/api/event" src="/plsbl/js/script.js"></script>
-```
-
-Are you using our extensions such as hash-based routing, revenue or outbound link click tracking? Change the file name from `script.js` to the script you want to use: `script.hash.js`, `script.revenue.js` or `script.outbound-links.js`. Want to use more than one extension? You can chain them like this: `script.hash.revenue.outbound-links.js`.
-
-Deploy these changes to your site. You can verify the proxy is working by opening your network tab. You should see a request to `https://yourdomain.com/js/script.js` with status 200 and another one to `https://yourdomain.com/api/event` with status 202.
-
-That's it! You're now counting your website stats using a proxy.
-
-Thanks to Lynden Jones for creating this guide!