SearXNG update

[jdaviescoates]

@xarp said in SearXNG update:

despite fixes pushed weeks ago.

To be fair, that was pushed 10 days ago, not weeks ago.

But still, I agree, it would be good to get an update! (that last one was on 30 Sept which was indeed 3 weeks ago).

[girish]

I am making a new package. But since they don't make releases, there is no easy way for us to keep track of when to make a new package.

[jdaviescoates]

@girish said in SearXNG update:

I am making a new package.

Great, thanks @girish

But since they don't make releases, there is no easy way for us to keep track of when to make a new package.

Is there anyway to automate checking for changes once a day using Change Detection or something? (or perhaps that'd create too much work?).

Once a week at minimum? Or everything 3 days or something? (given the Cloudron website says "We publish latest releases within days")

[girish]

@jdaviescoates yeah, I think it makes sense to check every 2 weeks or so. I don't want to make a new package for every commit

[jdaviescoates]

@girish tbh I've no idea what is involved in making a new package, but presumably it's not trivial, so fair enough.

[xarp]

@girish I have a great idea.

Directly under "Check for Updates" in the app settings page, there could be a "Notify" button. And perhaps a field for allowing any optional comments to be sent to the team with the notification.

[archos]

Hi, sorry to open a closed thread, but I don't want to start a new one.
Is it possible to update the apps every month?
And just a question. The application is updated to SearXNG version 01b5b9cb8, but at the bottom of the site, where the source code and public instances are version 1.0.0 users think that we don't update the search engine. Thank you very much for the information, maybe I have to set something and the instance will show the correct version.

[girish]

@archos thanks for the reminder, updated.

Really need a to way to deal with these rolling releases...

[archos]

Thank you very much for the update. Not a problem at all, I understand that not everything is easy.

[robi]

@girish said in SearXNG update:

Really need a to way to deal with these rolling releases...

Try the change detection app with a notification..

[necrevistonnezr]

@girish The same applies for TT-RSS, btw.

[nebulon]

I guess the issue mainly with rolling releases is, that we can't quite update the app on every new change upstream, but have to do this maybe in a fixed interval or n amount of changes upstream.

[archos]

@nebulon And would it be possible to set it to show the installed version at the bottom of the app? We still have version 1.0.0.
It looks like the app is not updated.
Thank you very much for the information.

[girish]

@archos good idea, I am updating SearX now to show version like below:

[girish]

@archos updated.

[archos]

That's great, thank you so much for the quick update.

[taisau]

it's been a month, time again to update?

[nebulon]

Updated now to latest master

[girish]

OK, I have put a reminder for ourselves via a cron pattern for twice a month. In any case wants something like this, put this into the cron section of the app:

0 7 1,15 * * "==> Sending reminder to update apps" && swaks --server "${CLOUDRON_MAIL_SMTP_SERVER}" -p "${CLOUDRON_MAIL_SMTP_PORT}" --from "${CLOUDRON_MAIL_FROM}" --h-Subject "Check if SearXNG needs to be updated" --auth-user "${CLOUDRON_MAIL_SMTP_USERNAME}" --auth-password "${CLOUDRON_MAIL_SMTP_PASSWORD}" --to notification@domain.com --body "This is cron reminder to update SearXNG package if needed" --silent 2