Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warn admin about outdated Collabora versions #4349

Open
juliusknorr opened this issue Dec 17, 2024 · 4 comments
Open

Warn admin about outdated Collabora versions #4349

juliusknorr opened this issue Dec 17, 2024 · 4 comments
Labels
1. to develop Waiting for a developer enhancement New feature or request

Comments

@juliusknorr
Copy link
Member

We notice quite often that users update their Nextcloud but have no information that there is a new Collabora version available (both patch updates but also major versions).

On the Nextcloud side we can send notifications to admins and also warn them prominently in the admin overview.

While Collabora has a hint about new versions it is only shown to admins when they use collabora which might not happen often and therefore might be unseen.

My proposal would be to extend this in the richdocuments app:

  • Regularly check if there is a new Collabora version available
  • Notify admins about it
  • Show a warning in the admin overview of Nextcloud

We can read the currently installed version from capabilities of Collabora but there is no way I'm aware to know about the latest published version in machine readable form (both for CODE and COOL releases).

@pedropintosilva Not sure who to ping, but it would be nice to just have some endpoint that we can query that will tell us the latest version tag for CODE / COOL.

@juliusknorr juliusknorr added enhancement New feature or request 1. to develop Waiting for a developer labels Dec 17, 2024
@pedropintosilva
Copy link
Contributor

I agree. I wonder if this could be integral part of the #4041

@pedropintosilva
Copy link
Contributor

Nevertheless, I wonder if we don't already have a url that gives us that or if it wouldn't be beneficial to have one but probably @timar knows best

@juliusknorr
Copy link
Member Author

I agree. I wonder if this could be integral part of the #4041

Not sure how this should be related

@github-project-automation github-project-automation bot moved this to 🧭 Planning evaluation (don't pick) in 📝 Office team Dec 20, 2024
@juliusknorr juliusknorr moved this from 🧭 Planning evaluation (don't pick) to 📄 To do (~10 entries) in 📝 Office team Dec 20, 2024
@juliusknorr
Copy link
Member Author

For CODE I could imagine we just fetch https://www.collaboraoffice.com/repos/CollaboraOnline/CODE-deb/Packages and get the coolwsd version. But for enterprise packages it would not be feasible to use a real repository URL.

@timar A possibly simple solution I imagine might be to just write a simple text file containing the version during the build and just put them somewhere next to the repos. Maybe that can even be automated in the build scripts (I assume you have some in place for that 😁 )

Then we could hardcode urls like this in the richdocuments app to check for the latest release and compare with the ones that online returns in the capabilities

https://www.collaboraoffice.com/repos/latest-version-code
https://www.collaboraoffice.com/repos/latest-version-cool

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. to develop Waiting for a developer enhancement New feature or request
Projects
Status: 📄 To do (~10 entries)
Development

No branches or pull requests

2 participants