lure/lure-updater
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 3 Wiki Activity

Move lure-updater to updater.lure.sh
All checks were successful
ci/woodpecker/manual/woodpecker Pipeline was successful
Details

Browse Source
This commit is contained in:
Elara 2023-10-07 11:50:57 -07:00
parent d5775b9fa2
commit e429c904d4
4 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.goreleaser.yaml
View File

@ -29,7 +29,7 @@ blobs:
folder: "/" folder: "/"
release: release:
gitea: gitea:
owner: Elara6331 owner: lure
name: lure-updater name: lure-updater
gitea_urls: gitea_urls:
api: 'https://gitea.elara.ws/api/v1/' api: 'https://gitea.elara.ws/api/v1/'

4
README.md
View File

@ -1,12 +1,12 @@
# LURE Updater # 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 ### 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`. 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`.

2
lure-updater.example.toml
View File

@ -1,5 +1,5 @@
[git] [git]
repoURL = "https://github.com/Elara6331/lure-repo.git" repoURL = "https://github.com/lure-sh/lure-repo.git"
repoDir = "/etc/lure-updater/repo" repoDir = "/etc/lure-updater/repo"
[git.commit] [git.commit]
# The name and email to use in the git commit # The name and email to use in the git commit

2
template.nomad
View File

@ -58,7 +58,7 @@ job "lure-updater" {
tags = [ tags = [
"traefik.enable=true", "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", "traefik.http.routers.lure-updater.tls.certResolver=letsencrypt",
] ]
} }