diff --git a/.github/workflows/codeql.yml b/.github/workflows/codeql.yml new file mode 100644 index 0000000..9f9b411 --- /dev/null +++ b/.github/workflows/codeql.yml @@ -0,0 +1,74 @@ +# For most projects, this workflow file will not need changing; you simply need +# to commit it to your repository. +# +# You may wish to alter this file to override the set of languages analyzed, +# or to provide custom queries or build logic. +# +# ******** NOTE ******** +# We have attempted to detect the languages in your repository. Please check +# the `language` matrix defined below to confirm you have the correct set of +# supported CodeQL languages. +# +name: "CodeQL" + +on: + push: + branches: [ "master" ] + pull_request: + # The branches below must be a subset of the branches above + branches: [ "master" ] + schedule: + - cron: '30 3 * * 2' + +jobs: + analyze: + name: Analyze + runs-on: ubuntu-latest + permissions: + actions: read + contents: read + security-events: write + + strategy: + fail-fast: false + matrix: + language: [ 'csharp', 'javascript' ] + # CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python', 'ruby' ] + # Learn more about CodeQL language support at https://aka.ms/codeql-docs/language-support + + steps: + - name: Checkout repository + uses: actions/checkout@v3 + + # Initializes the CodeQL tools for scanning. + - name: Initialize CodeQL + uses: github/codeql-action/init@v2 + with: + languages: ${{ matrix.language }} + # If you wish to specify custom queries, you can do so here or in a config file. + # By default, queries listed here will override any specified in a config file. + # Prefix the list here with "+" to use these queries and those in the config file. + + # Details on CodeQL's query packs refer to : https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs + # queries: security-extended,security-and-quality + + + # Autobuild attempts to build any compiled languages (C/C++, C#, Go, or Java). + # If this step fails, then you should remove it and run the build manually (see below) + - name: Autobuild + uses: github/codeql-action/autobuild@v2 + + # ℹī¸ Command-line programs to run using the OS shell. + # 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun + + # If the Autobuild fails above, remove it and uncomment the following three lines. + # modify them (or add more) to build your code if your project, please refer to the EXAMPLE below for guidance. + + # - run: | + # echo "Run, Build Application using script" + # ./location_of_script_within_repo/buildscript.sh + + - name: Perform CodeQL Analysis + uses: github/codeql-action/analyze@v2 + with: + category: "/language:${{matrix.language}}" diff --git a/.github/workflows/mercuryhealth-web-ci.yml b/.github/workflows/mercuryhealth-web-ci.yml new file mode 100644 index 0000000..c79e66d --- /dev/null +++ b/.github/workflows/mercuryhealth-web-ci.yml @@ -0,0 +1,35 @@ +# This is a basic workflow to help you get started with Actions + +name: mercuryhealth-web-ci + +# Controls when the action will run. Triggers the workflow on push or pull request +# events but only for the master branch +on: [push] + +# A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + # This workflow contains a single job called "build" + build: + # The type of runner that the job will run on + runs-on: ubuntu-latest + + # Steps represent a sequence of tasks that will be executed as part of the job + steps: + # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it + - uses: actions/checkout@v2 + + # Runs a single command using the runners shell + - name: Setup .NET Core SDK + uses: actions/setup-dotnet@v1.6.0 + with: + Dotnet-version: 3.1.101 + + - run: dotnet build -c Release + - run: dotnet test -c Release + - run: dotnet publish -c Release -o mercuryhealth-we + + - name: Deploy to Azure + uses: Azure/webapps-deploy@v1 + with: + publish-profile: ${{ secrets.AzureWebAppPublishProfile }} + package: ./mercuryhealth-we diff --git a/ClientApp/src/views/Home.vue b/ClientApp/src/views/Home.vue index a1f7700..681ae53 100644 --- a/ClientApp/src/views/Home.vue +++ b/ClientApp/src/views/Home.vue @@ -7,53 +7,8 @@ -

Hello, world!

-

Welcome to your new single-page application, built with:

-
    -
  • - ASP.NET Core and - C# for cross-platform server-side API code
    • -
  • - Vue.js for client-side code
    • -
  • - Vue CLI for building, bundling and adding or removing vue plugins
    • -
  • - Webpack internally used by Vue CLI
    • -
  • - Vuetify for layout and styling
    • -
- -

To help you get started, we've also set up:

-
    -
  • - Client-side navigation. For example, click Counter then Back to return here.
    • -
  • - Development server integration. In development mode, the development server from - vue-cli-service runs in the background automatically, so your client-side resources are dynamically built on - demand and the page refreshes when you modify any file.
    • -
  • - Efficient production builds. In production mode, development-time features are disabled, and the - webpack build tool produces minified static CSS and JavaScript files.
    • -
- -

Integrated Vue plugins:

-
    -
  • - Vue.js - reactive, component-oriented view layer for modern web interfaces.
    • -
  • - Vuetify - a reusable semantic component framework for Vue.js.
    • -
  • - Class Component - ES201X/Typescript class decorator for Vue components.
    • -
  • - Property Decorator - property decorators for Vue components
    • -
  • - Router - official router for Vue.js 2
    • -
  • - Vuex - state management for Vue.js
    • -
  • - Register Service Worker - script for registering service - worker with hooks for common events to simplify PWA development.
    • -
+

Hello! Greetings from Denmark

+

Welcome to our single-page application.