From 0b3cea55784716452c3eceddfc912d82b783697c Mon Sep 17 00:00:00 2001 From: Jose Emilio Labra Gayo Date: Sun, 21 Jan 2024 11:52:51 +0100 Subject: [PATCH] Removed dependabot and change name of github action to release --- .github/dependabot.yml | 62 ------------------- .../workflows/{asw2324.yml => release.yml} | 2 +- README.md | 2 +- 3 files changed, 2 insertions(+), 64 deletions(-) delete mode 100644 .github/dependabot.yml rename .github/workflows/{asw2324.yml => release.yml} (99%) diff --git a/.github/dependabot.yml b/.github/dependabot.yml deleted file mode 100644 index 86d2429e..00000000 --- a/.github/dependabot.yml +++ /dev/null @@ -1,62 +0,0 @@ -# To get started with Dependabot version updates, you'll need to specify which -# package ecosystems to update and where the package manifests are located. -# Please see the documentation for all configuration options: -# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates - -version: 2 -updates: - - package-ecosystem: "github-actions" # See documentation for possible values - directory: "/" # Location of package manifests - schedule: - interval: "monthly" - # Maintain the npm dependencies of the frontend - - package-ecosystem: "docker" # See documentation for possible values - directory: "/webapp" # Location of package manifests - schedule: - interval: "weekly" - ignore: # Ignore the non-LTS node versions (17/01/2024 >20) - - dependency-name: "node" - versions: ["21.x","22.x","23.x","24.x"] - - package-ecosystem: "npm" # See documentation for possible values - directory: "/webapp" # Location of package manifests - schedule: - interval: "weekly" - ignore: # Avoid puppeteer+jest version updates to avoid incompatibilities/problems in CI-CD - - dependency-name: "puppeteer*" - - dependency-name: "jest*" - # Maintain the npm dependencies of the GatewayService - - package-ecosystem: "docker" # See documentation for possible values - directory: "/gatewayservice" # Location of package manifests - schedule: - interval: "weekly" - ignore: # Ignore the non-LTS node versions (17/01/2024 >20) - - dependency-name: "node" - versions: ["21.x","22.x","23.x","24.x"] - - package-ecosystem: "npm" # See documentation for possible values - directory: "/gatewayservice" # Location of package manifests - schedule: - interval: "weekly" - # Maintain the npm dependencies of the authservice - - package-ecosystem: "docker" # See documentation for possible values - directory: "/users/authservice" # Location of package manifests - schedule: - interval: "weekly" - ignore: # Ignore the non-LTS node versions (17/01/2024 >20) - - dependency-name: "node" - versions: ["21.x","22.x","23.x","24.x"] - - package-ecosystem: "npm" # See documentation for possible values - directory: "/users/authservice" # Location of package manifests - schedule: - interval: "weekly" - # Maintain the npm dependencies of the userservice - - package-ecosystem: "docker" # See documentation for possible values - directory: "/users/userservice" # Location of package manifests - schedule: - interval: "weekly" - ignore: # Ignore the non-LTS node versions (17/01/2024 >20) - - dependency-name: "node" - versions: ["21.x","22.x","23.x","24.x"] - - package-ecosystem: "npm" # See documentation for possible values - directory: "/users/userservice" # Location of package manifests - schedule: - interval: "weekly" diff --git a/.github/workflows/asw2324.yml b/.github/workflows/release.yml similarity index 99% rename from .github/workflows/asw2324.yml rename to .github/workflows/release.yml index 41a4bad7..b861d578 100644 --- a/.github/workflows/asw2324.yml +++ b/.github/workflows/release.yml @@ -1,4 +1,4 @@ -name: CI for ASW2324 +name: Deploy on release on: release: diff --git a/README.md b/README.md index 29a71374..3fe2c0f1 100644 --- a/README.md +++ b/README.md @@ -51,7 +51,7 @@ For the deployment, we have several options. The first and more flexible is to deploy to a virtual machine using SSH. This will work with any cloud service (or with our own server). -Other options include using the container services that all the cloud services provide. This means, deploying our Docker containers directly. +Other options include using the container services that most cloud services provide. This means, deploying our Docker containers directly. We are going to use the first approach, creating a virtual machine in a cloud service and after installing docker and docker-compose, deploy our containers there using GitHub Actions and SSH.