From bc27d886d4db1a02914969a76a3641c620906a4b Mon Sep 17 00:00:00 2001 From: cyril <38669260+cyrilbois@users.noreply.github.com> Date: Tue, 10 Sep 2024 18:07:52 +0200 Subject: [PATCH 1/2] Fix link to traffic_shaping.py in documentation/Throttle --- docs/documentation/throttle/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/documentation/throttle/index.md b/docs/documentation/throttle/index.md index 1b24ec5083..a6cc61337c 100644 --- a/docs/documentation/throttle/index.md +++ b/docs/documentation/throttle/index.md @@ -19,7 +19,7 @@ twitterdescription: **Throttle lets you *simulate slow network connections* on Linux and Mac OS X.** -Throttle uses *pfctl* on Mac and *tc* on Linux (you also need *ip* and *route* for Throttle to work on Linux) to simulate different network speeds and is inspired by [tylertreat/Comcast](https://github.com/tylertreat/Comcast), the [connectivity setting in the WPTAgent](https://github.com/WPO-Foundation/wptagent/blob/main/internal/traffic_shaping.py) and [sltc](https://github.com/sitespeedio/sltc). +Throttle uses *pfctl* on Mac and *tc* on Linux (you also need *ip* and *route* for Throttle to work on Linux) to simulate different network speeds and is inspired by [tylertreat/Comcast](https://github.com/tylertreat/Comcast), the [connectivity setting in the WPTAgent](https://github.com/catchpoint/WebPageTest.agent/blob/master/internal/traffic_shaping.py) and [sltc](https://github.com/sitespeedio/sltc). **What is Throttle good for?** From ee68c61bd24512c22dd5e72043242e290d6631f3 Mon Sep 17 00:00:00 2001 From: cyril <38669260+cyrilbois@users.noreply.github.com> Date: Tue, 10 Sep 2024 18:11:40 +0200 Subject: [PATCH 2/2] Add cyrilex to First party vs third party - /sitespeed.io/configuration/ --- docs/documentation/sitespeed.io/configuration/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/documentation/sitespeed.io/configuration/index.md b/docs/documentation/sitespeed.io/configuration/index.md index 70338a9c6b..5ee03e4600 100644 --- a/docs/documentation/sitespeed.io/configuration/index.md +++ b/docs/documentation/sitespeed.io/configuration/index.md @@ -162,7 +162,7 @@ By default we will categorise the current main domain as first party and the res docker run --rm -v "$(pwd):/sitespeed.io" sitespeedio/sitespeed.io:{% include version/sitespeed.io.txt %} --firstParty ".ryanair.com" https://www.ryanair.com/us/en/ ~~~ -This is a JavaScript regex and if you need help you should test it out at [https://regexr.com](https://regexr.com) to see that it will match. +This is a JavaScript regex and if you need help you should test it out at [https://regexr.com](https://regexr.com) or [cyrilex](https://extendsclass.com/regex-tester.html) to see that it will match. ### Output folder or where to store the result You can change where you want the data to be stored by setting the --outputFolder parameter. That is good in scenarios where you want to change the default behaviour and put the output in a specific location: