From e429c904d41113d7977fd499e9d0043bfef5d459 Mon Sep 17 00:00:00 2001 From: Elara Musayelyan Date: Sat, 7 Oct 2023 11:50:57 -0700 Subject: [PATCH] Move lure-updater to updater.lure.sh --- .goreleaser.yaml | 2 +- README.md | 4 ++-- lure-updater.example.toml | 2 +- template.nomad | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/.goreleaser.yaml b/.goreleaser.yaml index 67169b8..2dd1c03 100644 --- a/.goreleaser.yaml +++ b/.goreleaser.yaml @@ -29,7 +29,7 @@ blobs: folder: "/" release: gitea: - owner: Elara6331 + owner: lure name: lure-updater gitea_urls: api: 'https://gitea.elara.ws/api/v1/' diff --git a/README.md b/README.md index bc4a301..75ad8df 100644 --- a/README.md +++ b/README.md @@ -1,12 +1,12 @@ # LURE Updater -Modular bot that automatically checks for upstream updates and pushes new packages to [lure-repo](https://github.com/Elara6331/lure-repo). +Modular bot that automatically checks for upstream updates and pushes new packages to [lure-repo](https://github.com/lure-sh/lure-repo). --- ### How it works -Since LURE is meant to be able to install many different types of packages, this bot accepts [plugins](https://gitea.elara.ws/Elara6331/updater-plugins) in the form of [Starlark](https://github.com/bazelbuild/starlark) files rather than hardcoding each package. These plugins can schedule functions to be run at certain intervals, or when a webhook is received, and they have access to persistent key/value storage to keep track of information. This allows plugins to use many different ways to detect upstream updates. +Since LURE is meant to be able to install many different types of packages, this bot accepts [plugins](https://gitea.elara.ws/lure/updater-plugins) in the form of [Starlark](https://github.com/bazelbuild/starlark) files rather than hardcoding each package. These plugins can schedule functions to be run at certain intervals, or when a webhook is received, and they have access to persistent key/value storage to keep track of information. This allows plugins to use many different ways to detect upstream updates. For example, the plugin for `discord-bin` repeatedly polls discord's API every hour for the current latest download link. It puts the link in persistent storage, and if it has changed since last time, it parses the URL to extract the version number, and uses that to update the build script for `discord-bin`. diff --git a/lure-updater.example.toml b/lure-updater.example.toml index 8604914..da16945 100644 --- a/lure-updater.example.toml +++ b/lure-updater.example.toml @@ -1,5 +1,5 @@ [git] - repoURL = "https://github.com/Elara6331/lure-repo.git" + repoURL = "https://github.com/lure-sh/lure-repo.git" repoDir = "/etc/lure-updater/repo" [git.commit] # The name and email to use in the git commit diff --git a/template.nomad b/template.nomad index 06882d2..997c1c9 100644 --- a/template.nomad +++ b/template.nomad @@ -58,7 +58,7 @@ job "lure-updater" { tags = [ "traefik.enable=true", - "traefik.http.routers.lure-updater.rule=Host(`updater.lure.elara.ws`)", + "traefik.http.routers.lure-updater.rule=Host(`updater.lure.sh`)", "traefik.http.routers.lure-updater.tls.certResolver=letsencrypt", ] }