Bump @eslint/plugin-kit from 0.2.1 to 0.2.4 in /servers/execution/runner

CITATION.cff

@@ -1,34 +1,38 @@
 cff-version: 1.2.0
-message: "If you use this software, please cite it as below."
-authors:
-- family-names: "Talasila"
-  given-names: "Prasad"
-  orcid: "https://orcid.org/0000-0002-8973-2640"
 title: "Digital Twin as a Service"
-version: 0.3.0
-date-released: 2023-11-08
+version: 0.6.0
+date-released: 2024-11-11
 url: "https://github.com/into-cps-association/DTaaS"
+message: Please cite the following works when using this software.
 preferred-citation:
-  conference: "The 2023 IEEE International Conference on Digital Twin"
   authors:
-  - family-names: "Talasila"
-    given-names: "Prasad"
-    orcid: "https://orcid.org/0000-0002-8973-2640"
-  - family-names: "Gomes"
-    given-names: "Cláudio"
-    orcid: "https://orcid.org/0000-0000-0000-0000"
-  - family-names: "Mikkelsen"
-    given-names: "Peter Høgh"
-    orcid: "https://orcid.org/0000-0003-2321-758X"
-  - family-names: "Gil"
-    given-names: "Santiago"
-    orcid: "https://orcid.org/0000-0002-1789-531X"
-  - family-names: "Kamburjan"
-    given-names: "Eduard"
-    orcid: "https://orcid.org/0000-0002-0996-2543"
-  - family-names: "Larsen"
-    given-names: "Peter Gorm"
-    orcid: "https://orcid.org/0000-0002-4589-1500"
-  title: "Digital Twin as a Service (DTaaS): A Platform for Digital Twin Developers and Users"
-  month: 8
-  year: 2023
+    - family-names: Talasila
+      given-names: Prasad
+    - family-names: Gomes
+      given-names: Cláudio
+    - family-names: Vosteen
+      given-names: Lars B
+    - family-names: Iven
+      given-names: Hannes
+    - family-names: Leucker
+      given-names: Martin
+    - family-names: Gil
+      given-names: Santiago
+    - family-names: Mikkelsen
+      given-names: Peter H
+    - family-names: Kamburjan
+      given-names: Eduard
+    - family-names: Larsen
+      given-names: Peter G
+  doi: 10.1177/00375497241298653
+  identifiers:
+    - type: doi
+      value: 10.1177/00375497241298653
+  title: Composable digital twins on Digital Twin as a Service platform
+  date-published: 2024-01-01
+  year: 2024
+  journal: SIMULATION
+  publisher:
+    name: 'SAGE Publications Sage UK: London, England'
+  start: '00375497241298653'
+  type: article

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+Open new issue.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

README.md

@@ -39,14 +39,15 @@ if there is a suggestion to improve the software.
 If you find this repo useful for your research, please consider citing our paper:
 
 ```bibtex
-@INPROCEEDINGS{talasila2023dtaas,
-  author={Talasila, Prasad and Gomes, Cláudio and Mikkelsen, Peter Høgh and Arboleda, Santiago Gil and Kamburjan, Eduard and Larsen, Peter Gorm},
-  booktitle={2023 IEEE Smart World Congress (SWC)},
-  title={Digital Twin as a Service (DTaaS): A Platform for Digital Twin Developers and Users}, 
-  year={2023},
-  pages={1-8},
-  keywords={digital twins;physical twin;automation;life cycle;composition},
-  doi={10.1109/SWC57546.2023.10448890}}
+@article{talasila2024composable,
+author = {Prasad Talasila and Cl{\'a}udio Gomes and Lars B Vosteen and Hannes Iven and Martin Leucker and Santiago Gil and Peter H Mikkelsen and Eduard Kamburjan and Peter G Larsen},
+title ={Composable digital twins on Digital Twin as a Service platform},
+journal = {SIMULATION},
+pages = {00375497241298653},
+year={2024},
+doi = {10.1177/00375497241298653},
+publisher = {SAGE Publications Sage UK: London, England}
+}
 ```
 
 ## :hammer_and_wrench: Development Setup

SECURITY.md

@@ -6,7 +6,8 @@ We are currently providing security updates for:
 
 | Version | Supported          |
 | ------- | ------------------ |
-| 0.5.0   | :white_check_mark: |
+| 0.6.0   | :white_check_mark: |
+| 0.5.0   | :x:                |
 | 0.4.0   | :x:                |
 | 0.3.0   | :x:                |
 | 0.2.0   | :x:                |

deploy/services/gitlab/.env

@@ -1,2 +1,2 @@
-GITLAB_HOME='/Users/<Username>/DTaaS/deploy/services/gitlab'
+DTAAS_DIR='/Users/<username>/DTaaS'
 SERVER_DNS='foo.com'

deploy/services/gitlab/INTEGRATION.md

@@ -66,7 +66,7 @@ the following files:
    _deploy/config/client/env.local.js_.
 1. _deploy/docker/.env.local_ Add localpath and username.
 
-If the DTaaS application is hosted at <https://localhost>, then configure
+If the DTaaS application is hosted at <https://foo.com/>, then configure
 the following files:
 
 1. **DTaaS Client Authorization** token in

deploy/services/gitlab/README.md

@@ -29,7 +29,7 @@ Edit the `.env` file available in this directory to contain the following variab
 
 | Variable    | Example Value                                | Explanation                                                                                                                  |
 | :---------- | :------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------- |
-| GITLAB_HOME | '/home/Desktop/DTaaS/deploy/services/gitlab' | Full path to the DTaaS gitlab directory. This is an absolute path with no trailing slash.                                    |
+| DTAAS_DIR | '/Users/<username>/DTaaS' | Full path to the DTaaS directory. This is an absolute path with no trailing slash.                                    |
 | SERVER_DNS  | either `foo.com` or `localhost`                               | The server DNS, if you are deploying with a dedicated server. Remember not use _http(s)_ at the beginning of the DNS string. |
 
 **NOTE**: The DTaaS client uses the `react-oidc-context` node package, which
@@ -114,5 +114,7 @@ for further help.
 ## Pending Tasks
 
 This README helps with installation of Gitlab along side DTaaS application.
-But the OAuth2 integration between Gitlab and DTaaS will still be still pending.
-Follow the [INTEGRATION](./INTEGRATION.md) guide to setup the Gitlab integration.
+But the OAuth2 integration between Gitlab and DTaaS will still be pending.
+Follow the [integration guide](./INTEGRATION.md) and
+[runner setup guide](../runner/GITLAB-RUNNER.md) to setup the Gitlab
+integration.

deploy/services/gitlab/compose.gitlab.yml

@@ -15,9 +15,9 @@ services:
         nginx['redirect_http_to_https'] = false
         letsencrypt['enable'] = false
     volumes:
-      - '${GITLAB_HOME}/config:/etc/gitlab'
-      - '${GITLAB_HOME}/logs:/var/log/gitlab'
-      - '${GITLAB_HOME}/data:/var/opt/gitlab'
+      - '${DTAAS_DIR}/deploy/services/gitlab/config:/etc/gitlab'
+      - '${DTAAS_DIR}/deploy/services/gitlab/logs:/var/log/gitlab'
+      - '${DTAAS_DIR}/deploy/services/gitlab/data:/var/opt/gitlab'
     shm_size: '256m'
     labels:
       - "traefik.enable=true"