Abra should be able to show which apps have new versions available #130

New Issue

decentral1se · 2021-09-09T12:57:48Z

decentral1se commented

2021-09-09 12:57:48 +00:00

coop-cloud/abra#12

> https://git.coopcloud.tech/coop-cloud/abra/issues/12

femmefaytale added the

enhancement

label 2021-09-09 13:28:06 +00:00

decentral1se added this to the Command-line tool sustainability milestone 2021-09-09 14:24:36 +00:00

decentral1se added this to the Beta release (software) project 2021-09-17 05:42:43 +00:00

decentral1se commented

2021-09-20 16:27:19 +00:00

I was thinking that it might make sense to make --status the default on abra app ls and roll in #150, an async-aware table output for good UI/UX for slow load times. Then once we have a handle on the new versioning stuff re: #120 we could easily show a "update available" flag when checking.

I was thinking that it might make sense to make `--status` the default on `abra app ls` and roll in https://git.coopcloud.tech/coop-cloud/organising/issues/150, an async-aware table output for good UI/UX for slow load times. Then once we have a handle on the new versioning stuff re: https://git.coopcloud.tech/coop-cloud/organising/issues/120 we could easily show a "update available" flag when checking.

decentral1se self-assigned this 2021-09-20 16:46:17 +00:00

decentral1se commented

2021-09-30 11:45:03 +00:00

I just ran the following to wipe all old versioning from the recipe repos:

#!/bin/bash
for d in */ ; do
    cd "$HOME/.abra/apps/$d" && \
    echo "$d" && \
    git fetch -a && \
    git push origin --delete $(git tag -l) && \
    git tag -d $(git tag -l)
done

We can start working with the new scheme now.

I just ran the following to wipe all old versioning from the recipe repos: ```bash #!/bin/bash for d in */ ; do cd "$HOME/.abra/apps/$d" && \ echo "$d" && \ git fetch -a && \ git push origin --delete $(git tag -l) && \ git tag -d $(git tag -l) done ``` We can start working with the new scheme now.

decentral1se commented

2021-09-30 13:03:32 +00:00

Next steps:

Finish documenting provisionally how we handle versions
Publish two versions of Gitea (current config + upgrade)
Implement logic to show current deployed version + available ones in catalogue

This will be really great to finish.

Next steps: - Finish documenting provisionally how we handle versions - Publish two versions of Gitea (current config + upgrade) - Implement logic to show current deployed version + available ones in catalogue This will be really great to finish.

decentral1se commented

2021-10-05 18:56:17 +00:00

And then there was one 👀