On 11/25/25 1:44 PM, Nicholas D Steeves wrote:
Hi,
On Sun, 27 Oct 2024 15:27:15 -0700 Dan Helfman <[email protected]> wrote:
On 10/27/24 12:13 AM, [email protected] wrote:
On Sun, 18 Feb 2024 08:37:15 -0800 Dan Helfman <[email protected]> wrote:
An alternative would be to release the documentation already built for
the tag being released. For instance as an extra tarbal in the release
page.
What do you think?
I'd prefer not to migrate to Sphinx, but what I did was put a tarball of
the generated HTML for the docs into the packages repository of
borgmatic. You can find it here:
https://projects.torsion.org/borgmatic-collective/borgmatic/packages
If you click on borgmatic-docs, you'll see that the URL has the version
number in it, so you should be able to fetch it programmatically for a
particular version.
I hope that helps. Please let me know if you have any feedback on this.
This approach appears to make it impossible for uscan to find the
documentation tarball. Kaliko requested that the documentation tarball
is published on the same page as the borgmatic release tarball
(similarly to how gpg signature are published for a release), because
this uses Gitea's release tracking interface.
To be fair, maybe I was unsuccessful at defeating what appears to be an
anti-scraping feature, or alternatively I was unsuccessful at storing in
a variable
the version scraped from the Gitea API for the source code, and then
using that to write a URL to target a specifically correlated
documentation tarball.
Regards,
Nicholas
Okay, try now:
https://projects.torsion.org/borgmatic-collective/borgmatic/releases ...
See borgmatic-docs.tar.gz
Dan
