Hey there Nextcloud community.
weâre about to release an update to the Nextcloud snap containing a number of under-the-hood changes, specifically moving away from local Snapcraft plugins . This is a significant shift in how the snap is built, but users shouldnât notice any difference in functionality.
Thatâs why we kindly ask the community for some help kicking its tires.
If you want to give it a try, use the beta channel:
sudo snap install --beta nextcloud
And if you already have it installed, refresh to it:
sudo snap refresh --beta nextcloud
if youâre happy, revert back sudo snap revert nextcloud and remember its always good to have a backup before testing!
Weâve put together some smoke tests to help you really give it a workout:
âď¸đŚ Nextcloud packaged as a snap
Nextcloud packaged as a snap. Contribute to nextcloud/nextcloud-snap development by creating an account on GitHub.
Please test as much as you can, and let us know if you have any questions or run into any issues.
Thanks!
4 Likes
Iâve been running the Beta and refreshing to the latest (now 32.0.6snap2) with no issues.
Also no official measurements but it feels snappier probably due to the updated Redis.
Thank you!
4 Likes
Hey @user103773 thank you for supporting the snap
Thanks a lot for your feedback @user103773 !!
Can you share more info about your config? Basically, are you using the integrated https certificate generation ?
I have gone through several configs. but none had the integrated cert generation :
Currently running behind HAProxy reverse proxy with it handling http/2 & http/3, compression, and caching. It connects to Nextcloud simply through http. Certs renewed with GitHub - acmesh-official/acme.sh: A pure Unix shell script ACME client for SSL / TLS certificate automation
Previous config was HAProxy simply passed through the connection with my cert on Nextcloud. Certs also renewed using GitHub - acmesh-official/acme.sh: A pure Unix shell script ACME client for SSL / TLS certificate automation and not the integrated one. Worked without issue but only capable http/1.1.
A config before that was using Cloudflare tunnel. Also worked fine but the connection was slower with higher latency and there are limitations on file size as well.
Hey @user103773 , thanks for the quick reply
so youâre behind a reverse proxy too⌠any way of testing the integrated https certificate generation ?
Unfortunately no since this prod setup uses custom ports, wildcard cert that is used for other services on the domain, etc. HAProxy would also have to be reconfigured and break things for a while.
However, is there something else I can test for you?
no worries, weâre finding ways of testing included lets encrypt certsâŚ
weâll certainly reach out, thanks
@user103773
weâve released 32.0.6snap2 âŚ
Running on 32.0.6snap2 without issues so far.
Thank you for the development!