You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+72-3Lines changed: 72 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,15 +20,84 @@ If this is [`ipitio/backage`](https://github.com/ipitio/backage), all you have t
20
20
21
21
Otherwise, if this is a fork, you'd prefer an alternative method, or your packages weren't added to the [index](https://github.com/pkgforge-dev/backage/tree/index) after a day, enter the case-sensitive name of each missing user or organization on a new line at the top of `owners.txt`[here](https://github.com/pkgforge-dev/backage/edit/master/owners.txt) and make a pull request. Please submit just the name(s) -- ids, repos, and packages will be found automatically!
22
22
23
-
New packages won't be added until *all* existing ones are refreshed; you should also create an independent instance that'll update faster and more frequently, up to hourly. Simply fork just the `master` branch, enable Actions from its tab and all disabled workflows, and use the [Alternative URL](#alternative-url) when it changes. Your own packages will be picked up automatically! If you need to edit `owners.txt`, do so after the first run. This centralized repo will then serve as a backup for all subsets of packages not in `optout.txt`.
23
+
Otherwise, if this is a fork, you'd prefer an alternative method, or your packages weren't added to the [index](https://github.com/ipitio/backage/tree/index) after a day, enter the case-sensitive name of each missing user or organization on a new line at the top of `owners.txt`[here](https://github.com/ipitio/backage/edit/master/owners.txt) and make a pull request. Don't worry -- while my Contribution Graph is an uptime monitor of sorts, yours won't be. See the top of `bkg.sh` for details about available options, which must come last when passed to `update.sh`, as shown in `Self-Host`.
24
+
25
+
> [!TIP]
26
+
> You only need to add the name(s), IDs are fetched as needed.
27
+
28
+
New packages won't be added until *all* existing ones are refreshed; you should also create an independent instance that'll update faster and more frequently. Simply fork just the `master` branch, choose one of the following options, and use the [Alternative URL](#alternative-url) when it changes. This centralized repo will then serve as a backup for all subsets of packages not in `optout.txt`.
29
+
30
+
> [!IMPORTANT]
31
+
> Your own packages will be picked up automatically! If you need to edit `owners.txt`, do so after the first run.
32
+
33
+
<details>
34
+
<summary>With Actions</summary>
35
+
36
+
This will use a lot of minutes on GitHub-hosted runners, so you may want to use your own.
37
+
38
+
1. Enable Actions from its tab
39
+
2. Enable all disabled workflows
40
+
41
+
</details>
42
+
43
+
<details>
44
+
<summary>Self-Host</summary>
45
+
46
+
This is an example for `systemd`; adapt it to your needs. Please note:
47
+
48
+
- Docker needs to be installed
49
+
- You don't need to set `GITHUB_TOKEN` if you're logged in with `gh` or you'll first use your PAT to run (replace `*` with `https` or `ssh`):
Once the packages you're interested in have been added, replace the parameters with their respective values, scoping to your parsing needs, then access the latest data however you want. The format can be either `json` or `xml`. Use something like [shields.io/json](https://shields.io/badges/dynamic-json-badge) or [shields.io/xml](https://shields.io/badges/dynamic-xml-badge) to make badges like [this one](https://github.com/badges/shields/issues/5594#issuecomment-2157626147); you'll need the latter to evaluate expressions, like filters ([issue](https://github.com/ipitio/backage/issues/23)).
97
+
Once the packages you're interested in have been added, replace the parameters with their respective values, scoping to your parsing needs, then access the latest data however you want. The format can be either `json` or `xml`.
98
+
99
+
> [!NOTE]
100
+
> Use something like [shields.io/json](https://shields.io/badges/dynamic-json-badge) or [shields.io/xml](https://shields.io/badges/dynamic-xml-badge) to make badges like [this one](https://github.com/badges/shields/issues/5594#issuecomment-2157626147). You'll need the latter to evaluate expressions, like filters ([issue](https://github.com/ipitio/backage/issues/23)).
32
101
33
102
### Available Properties
34
103
@@ -164,7 +233,7 @@ As can packages in `owner[/repo]/.xml` files:
Copy file name to clipboardExpand all lines: src/lib/package.sh
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -144,7 +144,7 @@ update_package() {
144
144
fi
145
145
146
146
# calculate the overall downloads and size
147
-
size=$(sqlite3 "$BKG_INDEX_DB""select size from '$table_version_name' where id in (select id from '$table_version_name' order by id desc limit 1) order by date desc limit 1;")
147
+
size=$(sqlite3 "$BKG_INDEX_DB""select size from '$table_version_name' where size > 1 order by id desc, date desc limit 1;")
148
148
raw_all=$(sqlite3 "$BKG_INDEX_DB""select sum(downloads), sum(downloads_month), sum(downloads_week), sum(downloads_day) from '$table_version_name' where date in (select date from '$table_version_name' order by date desc limit 1);")
0 commit comments