build: update project config

Author: sebthom

.dockerignore

@@ -1,6 +1,12 @@
 *.md
 *.txt
+.actrc
+.dockerignore
+.editorconfig
+.gitattributes
+.gitignore
 .github/
 .shared/.*
 .shared/*.md
 .shared/*.txt
+image/Dockerfile

.gitattributes

@@ -39,6 +39,7 @@
 # Config/Serialisation
 .editorconfig    text
 **/.editorconfig text
+*.graphql        text
 *.ini            text
 *.properties     text
 *.json           text
@@ -56,8 +57,11 @@
 *.fish       text eol=lf
 *.sh         text eol=lf
 *.zsh        text eol=lf
+*.dart       text
+*.hx         text
 *.lua        text
 *.php        text
+*.py         text
 *.python     text
 *.sql        text
 **/Dockerfile text eol=lf
@@ -125,6 +129,8 @@
 *.htm        text diff=html
 *.html       text diff=html
 *.js         text
+*.ts         text
+*.vue        text
 
 
 # https://git-scm.com/docs/gitattributes#_export_ignore

.github/workflows/build.yml

@@ -3,10 +3,13 @@
 # SPDX-License-Identifier: Apache-2.0
 # SPDX-ArtifactOfProjectHomePage: https://github.com/vegardit/docker-meshcentral
 #
-# https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions
+# https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax
 name: Build
 
-on:
+on:  # https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows
+  schedule:
+    # https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#schedule
+    - cron: '0 17 * * 3'
   push:
     branches-ignore:  # build all branches except:
     - 'dependabot/**'  # prevent GHA triggered twice (once for commit to the branch and once for opening/syncing the PR)
@@ -25,20 +28,20 @@ on:
     - '.git*'
     - '.github/*.yml'
     - '.github/workflows/stale.yml'
-  schedule:
-    # https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows
-    - cron: '0 17 * * 3'
   workflow_dispatch:
-    # https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#workflow_dispatch
+    # https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#workflow_dispatch
+
 
 defaults:
   run:
     shell: bash
 
+
 env:
   DOCKER_REPO_NAME: meshcentral
   TRIVY_CACHE_DIR: ~/.trivy/cache
 
+
 jobs:
 
   ###########################################################
@@ -54,7 +57,7 @@ jobs:
     - name: "Show: GitHub context"
       env:
         GITHUB_CONTEXT: ${{ toJSON(github) }}
-      run: echo $GITHUB_CONTEXT
+      run: printf '%s' "$GITHUB_CONTEXT" | python -m json.tool
 
 
     - name: "Show: environment variables"
@@ -153,7 +156,7 @@ jobs:
     concurrency:
       group: ${{ github.workflow }}
       cancel-in-progress: false
-      
+
     permissions:
       packages: write
 

.github/workflows/stale.yml

@@ -1,11 +1,12 @@
-# https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions
+# https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax
 name: Stale issues
 
-on:
+on:  # https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows
   schedule:
-    - cron: '0 16 * * 1'
+    # https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#schedule
+    - cron: '0 15 1,15 * *'
   workflow_dispatch:
-    # https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/
+    # https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#workflow_dispatch
 
 permissions:
   issues: write
@@ -14,43 +15,6 @@ permissions:
 jobs:
   stale:
     runs-on: ubuntu-latest
-
     steps:
-    - name: Git checkout
-      uses: actions/checkout@v5  # https://github.com/actions/checkout
-
-    - name: Run stale action
-      uses: actions/stale@v10  # https://github.com/actions/stale
-      with:
-        repo-token: ${{ secrets.GITHUB_TOKEN }}
-        days-before-stale: 90
-        days-before-close: 14
-        stale-issue-message: >
-          This issue has been automatically marked as stale because it has not had
-          recent activity. It will be closed in 14 days if no further activity occurs.
-          If the issue is still valid, please add a respective comment to prevent this 
-          issue from being closed automatically. Thank you for your contributions.
-        stale-issue-label: stale
-        close-issue-label: wontfix
-        exempt-issue-labels: |
-          enhancement
-          pinned
-          security
-
-    - name: Run stale action (for enhancements)
-      uses: actions/stale@v10  # https://github.com/actions/stale
-      with:
-        repo-token: ${{ secrets.GITHUB_TOKEN }}
-        days-before-stale: 360
-        days-before-close: 14
-        stale-issue-message: >
-          This issue has been automatically marked as stale because it has not had
-          recent activity. It will be closed in 14 days if no further activity occurs.
-          If the issue is still valid, please add a respective comment to prevent this 
-          issue from being closed automatically. Thank you for your contributions.
-        stale-issue-label: stale
-        close-issue-label: wontfix
-        only-labels: enhancement
-        exempt-issue-labels: |
-          pinned
-          security
+      - name: Run stale action
+        uses: sebthom/gha-shared/.github/actions/stale@v1

CODE_OF_CONDUCT.md

@@ -60,7 +60,7 @@ representative at an online or offline event.
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
 reported to the community leaders responsible for enforcement at
-https://vegardit.com/about/legal/.
+https://vegardit.com/legal/
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the

CONTRIBUTING.md

@@ -1,25 +1,45 @@
-# Contributing
+# Contributing to the Project
 
-Thanks for your interest in contributing to this project!
+Thank you for your interest in contributing to this project! We strive to make the contribution process clear and welcoming.
 
-We want to make contributing as easy and transparent as possible.
+Please take a moment to review the guidelines below.
 
 
 ## Code of Conduct
 
-Our code of conduct is described in [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md).
+Please review and adhere to our [Code of Conduct](CODE_OF_CONDUCT.md) in all your interactions with the project.
+This helps us maintain a positive and respectful environment for everyone involved.
 
 
-## Issues
+## How to Contribute
 
-We use GitHub issues to track bugs and feature requests. Please ensure your description is clear and has sufficient instructions to be able to reproduce the issue.
+### Contributor Responsibilities
 
+By submitting your contributions, you agree to the following:
+- You are the sole author of the content you contribute, or you have the appropriate rights and permissions to contribute it.
+- If employed, you have obtained any necessary permissions from your employer to contribute to this project.
+- All contributions will be made available under the project’s license.
 
-## Pull Requests
+### Issues
 
-Before you make a substantial pull request, please file an issue and make sure someone from the team agrees that there is a problem or room for improvement.
+We use GitHub Issues to track bugs and feature requests. When submitting an issue, please ensure:
+- The description is clear and concise.
+- You provide enough details and steps to reproduce the issue, if applicable.
 
+### Pull Requests
 
-## License
+Before making substantial contributions:
+1. **Discuss Changes**: Please file an issue first to discuss your proposed changes with the team. This helps ensure your contribution aligns with the project’s goals.
+2. **Follow Best Practices**: Adhere to the guidelines and ensure your code meets the project’s standards.
 
-By contributing your code, you agree to license your contribution under the [Apache License 2.0](LICENSE.txt).
+When submitting a pull request:
+- Ensure your changes are well-documented.
+- Include tests for any new features or significant changes.
+- Reference the relevant issue(s) in your pull request description.
+
+
+## Licensing
+
+By contributing to this project, you agree that your contributions will be licensed under the [Apache License 2.0](LICENSE.txt).
+
+The project itself is also licensed under the [Apache License 2.0](LICENSE.txt)).