A
@eganonoa said in High Performance Back-end for Nextcloud Files:
@girish I've updated to 7.2.2 just now and cannot seem to get the binary to run with @reboot. I have tried in the crontab:
@reboot /app/code/config/notify_push.sh
and
@reboot sleep 60 /app/code/config/notify_push.sh (just in case a delay is necessary)
and watching the logs I can't seem get the binary to run.
Any thoughts on what I'm doing wrong.
Did you ever find a solution to that?
@andreasdueren Thanks! The script you link to is great and provide a full package with the NC Talk HPB, Collabora etc. But I wondered if we might have gone closer to an easy solution for just the Files HPB which seems to be a rather small and light component compared to all the other stuff in the script. While simple, that script still requires to set-up a whole other server just for that, which if you don't need the Talk HPB feels a bit heavy handed.
In this thread it looks like @girish and @eganonoa got very close to get the Files HPB working smoothly.
@girish Hi Girish, I wonder if nowadays there is a way to get this working? It seems like you all got quite far a long a while ago but I can't see any updates. Would be great to get it to work, especially client push! 
As the OP I must say that I had to finally give up in enabling full text search as it kept breaking searches. It works for a while but then breaks again and people get no results for very simple searches. Rerunning the script manually to reindex every time is not really a solution.
@rmdes said in Funkwhale - A modern, convivial and free music server:
its not an official cloudron app
Should it become one? @staff
I have had that happened with Mirotalk too,. Sometimes update get stuck. Happens less often these days but still sometimes. I either have to restart the app or remove and reinstall.
@imc67 said in Cloudron v9: huge disk I/O is this normal/safe/needed?:
I stopped about 25% of the apps at a certain moment with no significant result
I think @nebulon was suggesting to stop apps one by one to see if one particular app is causing the problem.
@Teiluj said in Stirling-PDF requires reinstallation:
However, it does not gives me clarity on where things stands with regards to OIDC/SSO enabled instances, and which are now subject to the change.
As far as I understand, the situation is that if you already have an oidc enable instance installed on your Cloudron, then you can keep it, but you won't get any more updates on it, that's all.
Any new install will have the newer version with all the new restrictions.
Just for info, another instance auto updated last night from 8.3.2 to 9.0.13 and something weird happened: I got the same error on the backup site (with two failed backup notifications) AND that backup site got duplicated into a new one but for some reasons as a tar archive instead of rsync like the original site. No idea what happened there.
@joseph how come as this been marked as solved? There have been no response and it clearly wasn't as of 9.0.12.
@robi I agree this isn't Ideal, especially when you have lots of notifications.
Same here when upgrading from 8.3.2 to Cloudron 9.0.12. Remounting storage solves it, but still not optimal as a default behaviour.
I agree Zulip would really be a great addition. Best out of all of them.
Oh that is sad...
Is there any follow-up on this by any chance? @jdaviescoates
@jdaviescoates so here is my config which works well and gets around the admin group issue.
In the OIDC NC app config:
Then you create a group folder per NC group, and when you add a user to Cloudron and add to a specific Cloudron group, it gets automatically added to the corresponding MC group and gets access to the group folder associated with that group.
In addition, in order not to confuse users with the NC login form I now disable other login methods using this command: occ config:app:set --value=0 user_oidc allow_multiple_user_backends
and set a custom end point to my Cloudron dashboard when people try to log out of Nextcloud:
Here is what I see when I press the update button manually:
Auto-updates are enabled, yet the app does not auto-update. And this is the case on two different instances. In fact it also does not update automatically from 32.0.0 to 32.0.1.
Yes the update now works directly from version 31.0.9 to 32.0.1. However, FYI, updating to 32.0.1 does not happen automatically and is still marked as a "pre-release and not considered stable yet". If this is intended just ignore me, but thought I'd let you know in case that was oversight (given that was not even the case when 32.0.0 got pushed).
@girish on my instances NC still tries to first update to 32.0.0 despite 32.0.1 having now been pushed.
@james Thanks for explaining how to package how own version, that's really good to know in general!
@shrey Just to say, I don't think the dev doesn't favour stable versions. Most versions are stable on the repo, it's just that there is major update coming (v1.0) and so they've released a few RC before release it stable, but that's pretty standard practice.
