new and app ls --status
closed as discussed on matrix, since better errorhandling is kidn of a rabbithole
new and app ls --status
hey @decentral1se, I tried to verify this issue, but think this health check is working correctly; it is considered unhealthy until the initial installation is complete, which is exactly the…
new and app ls --status
The new issue seems to be a separate problem. I tried to chase it down through the go-code, but it looks like the git clone indeed just fails (and the debug output that the clone was successful…
new and app ls --status
can reproduce the issue with a fresh install and a new .abra directory. It could be related to the IPv6 lookup; I tried to force IPv4 by disabling IPv6 on the loopback and wireless interfaces…
new and app ls --status
okay, and I can confirm the issue for the new command;
abra app new nextcloud
FATA unable to update catalogue: Get "https://git.coopcloud.tech/coop-cloud/recipes-catalogue-json.git/info…
new and app ls --status
I verified that 1.24.7 does not fix the issue, while 1.25.0 lists these breaking changes:
Return 201 Created for CreateVariable API responses (#34517) Add label 'state' to metric…
It is a bit offtopic but I really did not want to make a PR for a two-character change: the URL in README.md should be: https://hub.docker.com/r/gitea/gitea (it 404s without the /r, iirc this…
I'm assuming bumping to -latest is not a good idea; I assume a more recent version would work, but I lack the experience to test a potential upgrade (and I don't run a gitea myself).
originally I tried to merge the forked main into this main, but that failed -- that's what I get for not using feature branches :)