Moving from green-coding-berlin got green-coding-solutions

ArneTR · ArneTR · commit 88f43d8db672 · 2025-05-10T10:12:20.000+02:00
diff --git a/config/_default/menus/menus.en.toml b/config/_default/menus/menus.en.toml
@@ -19,7 +19,7 @@
 [[social]]
   name = "GitHub"
   pre = "<svg xmlns=\"http://www.w3.org/2000/svg\" width=\"20\" height=\"20\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\" class=\"feather feather-github\"><path d=\"M9 19c-5 1.5-5-2.5-7-3m14 6v-3.87a3.37 3.37 0 0 0-.94-2.61c3.14-.35 6.44-1.54 6.44-7A5.44 5.44 0 0 0 20 4.77 5.07 5.07 0 0 0 19.91 1S18.73.65 16 2.48a13.38 13.38 0 0 0-7 0C6.27.65 5.09 1 5.09 1A5.07 5.07 0 0 0 5 4.77a5.44 5.44 0 0 0-1.5 3.78c0 5.42 3.3 6.61 6.44 7A3.37 3.37 0 0 0 9 18.13V22\"></path></svg>"
-  url = "https://github.com/green-coding-berlin"
+  url = "https://github.com/green-coding-solutions"
   post = "v0.1.0"
   weight = 10
 
diff --git a/config/_default/menus/menus.nl.toml b/config/_default/menus/menus.nl.toml
@@ -23,7 +23,7 @@
 [[social]]
   name = "GitHub"
   pre = "<svg xmlns=\"http://www.w3.org/2000/svg\" width=\"20\" height=\"20\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\" class=\"feather feather-github\"><path d=\"M9 19c-5 1.5-5-2.5-7-3m14 6v-3.87a3.37 3.37 0 0 0-.94-2.61c3.14-.35 6.44-1.54 6.44-7A5.44 5.44 0 0 0 20 4.77 5.07 5.07 0 0 0 19.91 1S18.73.65 16 2.48a13.38 13.38 0 0 0-7 0C6.27.65 5.09 1 5.09 1A5.07 5.07 0 0 0 5 4.77a5.44 5.44 0 0 0-1.5 3.78c0 5.42 3.3 6.61 6.44 7A3.37 3.37 0 0 0 9 18.13V22\"></path></svg>"
-  url = "https://github.com/green-coding-berlin"
+  url = "https://github.com/green-coding-solutions"
   post = "v0.1.0"
   weight = 10
 
diff --git a/config/_default/params.toml b/config/_default/params.toml
@@ -69,7 +69,7 @@ alertText = "Introducing the Doks child theme, several DX + UX updates, and more
 # repoHost [Github | Gitea | GitLab | Bitbucket | BitbucketServer ] is used for building the edit link based on git hoster
 repoHost = "GitHub"
 #repoHost = "Gitea"
-docsRepo = "https://github.com/green-coding-berlin/documentation"
+docsRepo = "https://github.com/green-coding-solutions/documentation"
 docsRepoBranch = "master"
 docsRepoSubPath = ""
 editPage = false
diff --git a/content/en/docs/cluster/accuracy-control.md b/content/en/docs/cluster/accuracy-control.md
@@ -20,7 +20,7 @@ cluster:
     ...
     control_workload:
       name: "Measurement control Workload"
-      uri: "https://github.com/green-coding-berlin/measurement-control-workload"
+      uri: "https://github.com/green-coding-solutions/measurement-control-workload"
       filename: "usage_scenario.yml"
       branch: "main"
       comparison_window: 5
diff --git a/content/en/docs/contributing/example-applications-contribution.md b/content/en/docs/contributing/example-applications-contribution.md
@@ -7,7 +7,7 @@ weight: 201
 toc: true
 ---
 
-We welcome everybody to provide example applications with a Pull Requests on [GitHub](https://github.com/green-coding-berlin/example-applications)
+We welcome everybody to provide example applications with a Pull Requests on [GitHub](https://github.com/green-coding-solutions/example-applications)
 
 Please be aware that in order to achieve the most gain for the community and
 the goal to keep measurements reproducible and comparable we provide some
@@ -31,7 +31,7 @@ If your application uses of one the service below, please use the recommended co
 
 ### Interacting with Web Applications
 
-- [Our Puppeteer Containers](https://github.com/green-coding-berlin/example-applications/tree/main/puppeteer-firefox-chrome)
+- [Our Puppeteer Containers](https://github.com/green-coding-solutions/example-applications/tree/main/puppeteer-firefox-chrome)
 
 ### Web Applications
 
@@ -45,4 +45,4 @@ to overlay an existing filesystem.
 - We recommend using [PHP Official + Apache](https://hub.docker.com/_/php) &raquo; Please use the tag: `php:8.0-apache`.
 
 To see an example where we use this container and also add some PHP modules / Apache modules have a look
-at our [PHP-Apache Example Application](https://github.com/green-coding-berlin/example-applications/tree/main/apache-mariadb-php)
+at our [PHP-Apache Example Application](https://github.com/green-coding-solutions/example-applications/tree/main/apache-mariadb-php)
diff --git a/content/en/docs/contributing/green-metrics-tool-contribution.md b/content/en/docs/contributing/green-metrics-tool-contribution.md
@@ -9,6 +9,6 @@ toc: true
 
 ## We are very happy to accept any contributions to the framework! 🥳🎉😍
 
-Please send all pull requests to our [`main` branch](https://github.com/green-coding-berlin/green-metrics-tool/tree/dev).
+Please send all pull requests to our [`main` branch](https://github.com/green-coding-solutions/green-metrics-tool/tree/dev).
 
 If you have any questions to not hesitate to send us an email: [info@green-coding.io](mailto:info@green-coding.io)
diff --git a/content/en/docs/frontend/customization.md b/content/en/docs/frontend/customization.md
@@ -14,7 +14,7 @@ The Dashboard and the graphs that are shown are customizable in the metrics they
 When installing the tool we provide a basic configuration that you can find in the 
 generated `frontend/js/helpers/config.js` .
 
-For comparison, here is the template file that is checked into the repository: [config.js.example](https://github.com/green-coding-berlin/green-metrics-tool/blob/main/frontend/js/helpers/config.js.example)
+For comparison, here is the template file that is checked into the repository: [config.js.example](https://github.com/green-coding-solutions/green-metrics-tool/blob/main/frontend/js/helpers/config.js.example)
 
 The first part of the file should not be modified, as these variables are set by the install script:
 
diff --git a/content/en/docs/frontend/libraries-and-components.md b/content/en/docs/frontend/libraries-and-components.md
@@ -80,4 +80,4 @@ it looked way nicer.
 
 So if you plan on measurements < 30 Minutes than ApexCharts might be a good choice for a frontend charting library.
 Please checkout our old release where we still used the library if you need a
-starting point how to integrate it: [Release v0.1-beta](https://github.com/green-coding-berlin/green-metrics-tool/releases/tag/v0.1-beta)
+starting point how to integrate it: [Release v0.1-beta](https://github.com/green-coding-solutions/green-metrics-tool/releases/tag/v0.1-beta)
diff --git a/content/en/docs/help/troubleshooting.md b/content/en/docs/help/troubleshooting.md
@@ -54,7 +54,7 @@ This is due to a current bug with the reading of the XML output of the powermetr
 
 Easiest fix: Just try the run again. The error happens seldomly and is random.
 
-[Please consult this ticket for current status of the bugfix](https://github.com/green-coding-berlin/green-metrics-tool/issues/286)
+[Please consult this ticket for current status of the bugfix](https://github.com/green-coding-solutions/green-metrics-tool/issues/286)
 
 ## Submodule issues
 
@@ -80,7 +80,7 @@ This is because a container has exited during the run of the GMT or you are runn
 
 A way to do this with the GMT directly without changing your containers would be the `command` command. See [usage_scenario.yml →]({{< relref "/docs/measuring/usage-scenario" >}}) 
 
-An example where we use this command to keep a container alive is here: https://github.com/green-coding-berlin/example-applications/blob/main/idle/usage_scenario.yml
+An example where we use this command to keep a container alive is here: https://github.com/green-coding-solutions/example-applications/blob/main/idle/usage_scenario.yml
 
 ## Stderr on {metric_provider.__class__.__name__} was NOT empty
 
diff --git a/content/en/docs/installation/calibration.md b/content/en/docs/installation/calibration.md
@@ -15,7 +15,7 @@ we have the `sleep_time_after_job` parameter in the [`config.py`](/docs/installa
 where you can set how long to sleep between jobs.
 
 To find out this value we have a script `tools/calibrate.py` in the Green Metrics Tool
-[repo](https://github.com/green-coding-berlin/green-metrics-tool). On the system that you want to run your benchmarks on
+[repo](https://github.com/green-coding-solutions/green-metrics-tool). On the system that you want to run your benchmarks on
 you can execute this script to get the cool down period. The script is called with `python3 calibrate.py`
 
 You can then either get the script to set the correct value for you or set it yourself.
diff --git a/content/en/docs/installation/installation-linux.md b/content/en/docs/installation/installation-linux.md
@@ -34,7 +34,7 @@ Also we trigger a `apt-upgrade`. If you do not want that upgrade or a different
 sudo apt update && \
 sudo apt upgrade -y && \
 sudo apt install -y curl git make gcc python3 python3-pip python3-venv && \
-git clone https://github.com/green-coding-berlin/green-metrics-tool ~/green-metrics-tool && \
+git clone https://github.com/green-coding-solutions/green-metrics-tool ~/green-metrics-tool && \
 cd ~/green-metrics-tool
 
 ```
@@ -45,7 +45,7 @@ cd ~/green-metrics-tool
 ```bash
 sudo dnf upgrade -y && \
 sudo dnf install -y curl git make gcc python3 python3-devel && \
-git clone https://github.com/green-coding-berlin/green-metrics-tool ~/green-metrics-tool && \
+git clone https://github.com/green-coding-solutions/green-metrics-tool ~/green-metrics-tool && \
 cd ~/green-metrics-tool
 ```
 
diff --git a/content/en/docs/installation/installation-macos.md b/content/en/docs/installation/installation-macos.md
@@ -15,7 +15,7 @@ We have tested the tool on Intel as well as on Apple Silicon chips. Results may
 ## Downloading and installing required packages
 
 ```bash
-git clone https://github.com/green-coding-berlin/green-metrics-tool ~/green-metrics-tool
+git clone https://github.com/green-coding-solutions/green-metrics-tool ~/green-metrics-tool
 ```
 
 ## Docker
diff --git a/content/en/docs/measuring/best-practices.md b/content/en/docs/measuring/best-practices.md
@@ -104,7 +104,7 @@ You can either use our service with a free tier or set the cluster up yourself.
 into a heat limiting.
 - Also you should take waiting times between test runs to make sure that the system has cooled down again and your 
 energy measurements are not false-high. A good number for this has emerged in our testing which is **180 s**. However on 
-a 30+ core machine this value might be higher. We are currently working on a [calibration script](https://github.com/green-coding-berlin/green-metrics-tool/issues/355) to determine this exact 
+a 30+ core machine this value might be higher. We are currently working on a [calibration script](https://github.com/green-coding-solutions/green-metrics-tool/issues/355) to determine this exact
 value for a particular system.
 
 If you are using a standard cronjob mechanism to trigger the GMT you can use the `post-test-sleep` to force a fixed sleep time.
diff --git a/content/en/docs/measuring/configuration.md b/content/en/docs/measuring/configuration.md
@@ -49,7 +49,7 @@ cluster:
     shutdown_on_job_no: False
     control_workload:
       name: "Measurement control Workload"
-      uri: "https://github.com/green-coding-berlin/measurement-control-workload"
+      uri: "https://github.com/green-coding-solutions/measurement-control-workload"
       filename: "usage_scenario.yml"
       branch: "main"
       comparison_window: 5
@@ -134,7 +134,7 @@ For the rest please see [installation →]({{< relref "/docs/cluster/installatio
 Some metric providers have unique configuration params:
 
 - PsuEnergyAcXgboostSystemProvider
-  + Please look at the always current documentation to understand what values to plug in here: [XGBoost SPECPower Model documentation](https://github.com/green-coding-berlin/spec-power-model)
+  + Please look at the always current documentation to understand what values to plug in here: [XGBoost SPECPower Model documentation](https://github.com/green-coding-solutions/spec-power-model)
 
 Also note that some providers are deactivated by default, because they either need
 additional configuration parameters, extra hardware or a specially configured system.
diff --git a/content/en/docs/measuring/containerizing-applications.md b/content/en/docs/measuring/containerizing-applications.md
@@ -192,7 +192,7 @@ services:
 
 In order to simulate a client we need a container running a headless browser.
 
-We choose Puppeteer and provide an example container to build here: [https://github.com/green-coding-berlin/example-applications/tree/main/puppeteer-firefox-chrome](https://github.com/green-coding-berlin/example-applications/tree/main/puppeteer-firefox-chrome)
+We choose Puppeteer and provide an example container to build here: [https://github.com/green-coding-solutions/example-applications/tree/main/puppeteer-firefox-chrome](https://github.com/green-coding-solutions/example-applications/tree/main/puppeteer-firefox-chrome)
 
 You can also download the container directly from docker hub here: [Docker Hub](https://hub.docker.com/r/greencoding/puppeteer-chrome)
 
@@ -254,7 +254,7 @@ Afterwards run the measurements.
 
 An example how to run a measurement locally can be found here: [Measuring locally →]({{< relref "measuring-locally" >}})
 
-To see all final files in an example of what we introduced here go to the [Example app](https://github.com/green-coding-berlin/simple-example-application)
+To see all final files in an example of what we introduced here go to the [Example app](https://github.com/green-coding-solutions/simple-example-application)
 
 ### Help / Debugging
 If you run into any errors see the [Debugging →]({{< relref "debugging" >}}) page.
diff --git a/content/en/docs/measuring/measuring-service.md b/content/en/docs/measuring/measuring-service.md
@@ -15,8 +15,7 @@ If you do not have that, please check out the relevant links given.
 Our hosted service is available at [https://metrics.green-coding.io/](https://metrics.green-coding.io/)  
 and you can [request a measurement of your application](https://metrics.green-coding.io/request.html).
 
-You can supply the GitHub link to our provided [easy example application](https://github.com/green-coding-berlin/simple-example-application) and wait for  
-an email to arrive to view a report.
+You can supply the GitHub link to our provided [easy example application](https://github.com/green-coding-solutions/simple-example-application) and wait for an email to arrive to view a report.
 
 This example highlights that in order to measure an application you really need to only have a repository with a [usage_scenario.yml →]({{< relref "usage-scenario" >}}) file.
 
diff --git a/content/en/docs/measuring/metric-providers/psu-energy-xgboost-machine.md b/content/en/docs/measuring/metric-providers/psu-energy-xgboost-machine.md
@@ -10,7 +10,7 @@ weight: 216
 
 It estimates the total machine energy consumption (AC Power) based on training
 data from the [SPECPower database](https://www.spec.org/power_ssj2008).
-The underlying XGBoost model can be found [on our GitHub](https://github.com/green-coding-berlin/spec-power-model).
+The underlying XGBoost model can be found [on our GitHub](https://github.com/green-coding-solutions/spec-power-model).
 
 ### Classname
 
@@ -56,7 +56,7 @@ In the `config.yml` file the *CpuUtilizationProcfsSystemProvider* must also be a
     - Takes no arguments
 
 If you want to run the provider directly we advise that you rather check
-out it's main repository: [XGBoost SPECPower Model documentation](https://github.com/green-coding-berlin/spec-power-model)
+out it's main repository: [XGBoost SPECPower Model documentation](https://github.com/green-coding-solutions/spec-power-model)
 
 The provider reads the `/tmp/green-metrics-tool/cpu_utilization_procfs_system.log` file
 from the *CpuUtilizationProcfsSystemProvider* in order to keep overhead low and
diff --git a/content/en/docs/measuring/sci.md b/content/en/docs/measuring/sci.md
@@ -23,7 +23,7 @@ The actual ticks for the unit of work (*R*) are captured from the containers and
 
 ### Setup in usage_scenario
 
-Please see an example how to configure in our [example applications repository for SCI apps](https://github.com/green-coding-berlin/example-applications/tree/main/green-software-foundation-sci).
+Please see an example how to configure in our [example applications repository for SCI apps](https://github.com/green-coding-solutions/example-applications/tree/main/green-software-foundation-sci).
 
 A simple integration for an CLI based application might for instance look like this:
 
@@ -52,7 +52,7 @@ If you have an API or similar the output might not happen on the CLI directly, b
 
 ### Setup in config.yml
 
-An [example configuration](https://github.com/green-coding-berlin/green-metrics-tool/blob/main/config.yml.example) for the `config.yml` is provided when the Green Metrics Tool is installed.
+An [example configuration](https://github.com/green-coding-solutions/green-metrics-tool/blob/main/config.yml.example) for the `config.yml` is provided when the Green Metrics Tool is installed.
 The values for the respective variables have to be either defined to best knowledge (like lifetime for instance) and / or
 from official databases like:
 - [https://dataviz.boavizta.org/manufacturerdata](https://dataviz.boavizta.org/manufacturerdata)
@@ -96,15 +96,15 @@ The components of the SCI are attributed by the GMT as follows:
 
 We provide quite some example applications that showcase how the SCI can be measured with the Green Metrics Tool for APIs, CLI tools etc.
 
-[Example applications on GitHub](https://github.com/green-coding-berlin/example-applications/tree/main/green-software-foundation-sci)
+[Example applications on GitHub](https://github.com/green-coding-solutions/example-applications/tree/main/green-software-foundation-sci)
 
-[Example data with runs](https://metrics.green-coding.io/?uri=green-coding-berlin/example-applications&filename=green-software)
+[Example data with runs](https://metrics.green-coding.io/?uri=green-coding-solutions/example-applications&filename=green-software)
 
 ## Caveats and future work
 
 At the moment the SCI is only measured in the *RUNTIME* phase and no sub-phase measurement is possible.
 
 Future work will include making the SCI an actual *Metric Provider* and thus allowing to capture it in every phase, optionally with having different dimensions per phase even.
 
-The work on this task is tracked in [this GitHub Issue](https://github.com/green-coding-berlin/green-metrics-tool/issues/451). We would love to get some contributions on this if you are willing to help :)
+The work on this task is tracked in [this GitHub Issue](https://github.com/green-coding-solutions/green-metrics-tool/issues/451). We would love to get some contributions on this if you are willing to help :)
 
diff --git a/content/en/docs/prologue/example-applications.md b/content/en/docs/prologue/example-applications.md
@@ -25,7 +25,7 @@ All of our example applications have the same structure:
 - *...* is either a file, a folder or missing.
   + It contains supplemental files that are needed to build the `Dockerfile` and / or to make a bind-volume for the `compose.yml` be missing /will be a file / will be a folder.
 
-Please check out our [repository of example applications on GitHub](https://github.com/green-coding-berlin/example-applications)
+Please check out our [repository of example applications on GitHub](https://github.com/green-coding-solutions/example-applications)
 
 ## Demoing the example application (optional)
 
diff --git a/content/en/docs/prologue/introduction.md b/content/en/docs/prologue/introduction.md
@@ -54,7 +54,7 @@ get to know the flexibility of our tool to measure your application.
 The app you submit to our hosted service must conform  
 to the [usage scenario specification]({{< relref "/docs/measuring/usage-scenario" >}})  and be [containerized]({{< relref "/docs/measuring/containerizing-applications" >}}).
 
-After that you can look at our [Example Apps Repository](https://github.com/green-coding-berlin/example-applications) to see some prepared apps that can be directly measured.
+After that you can look at our [Example Apps Repository](https://github.com/green-coding-solutions/example-applications) to see some prepared apps that can be directly measured.
 
 
 ## Help: FAQ / Troubleshooting
diff --git a/layouts/index.html b/layouts/index.html
@@ -7,7 +7,7 @@ <h1 class="mt-0">{{ .Title }}</h1>
     <div class="col-lg-9 col-xl-8 text-center">
       <p class="lead">{{ .Params.lead | safeHTML }}</p>
       <a class="btn btn-primary btn-lg px-4 mb-2" href="/docs/{{ if .Site.Params.options.docsVersioning }}{{ .Site.Params.docsVersion }}/{{ end }}prologue/introduction/" role="button">Get Started</a>
-      <p class="meta">Open-source AGPLv3 Licensed. <a href="https://github.com/green-coding-berlin/green-metrics-tool">GitHub</a></p>
+      <p class="meta">Open-source AGPLv3 Licensed. <a href="https://github.com/green-coding-solutions/green-metrics-tool">GitHub</a></p>
     </div>
   </div>
 </section>
