WIP: Nextcloud and Nginx up version #30
No reviewers
Labels
No Label
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/nextcloud#30
Loading…
Reference in New Issue
No description provided.
Delete Branch "javielico/nextcloud:main"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two main changes:
Added version numbers for most stable latest releases.
Looks fab, one last tiny suggested change!
@ -84,3 +84,3 @@
cron:
image: nextcloud:24.0.6-fpm
image: nextcloud:stable-fpm
Would it be OK to switch this to
25.0.1
as well?@3wordchant does it makes sense to use the alpine versions as well instead of the debian ones? Just purely due to the fact that they will use less resources.
💯
@ -1 +1,88 @@
/.envrc
I'd prefer to leave these out if possible? It seems pretty boilerplate-ish and most of these files won't end up in such a repository. Also, it raises the questions, why doesn't such a
gitignore
config feature in all the other recipes? You can add this stuff to your own personal globalgitignore
?@ -79,3 +79,3 @@
order: start-first
labels:
- "coop-cloud.${STACK_NAME}.version=2.1.4+24.0.6-fpm"
- "coop-cloud.${STACK_NAME}.version=2.1.6+25.0.1-fpm"
Is
24.x
->25.x
a major bump for the Nextcloud image? Might wanna check this once over?Will do some tests from my end, not sure if you want to test anything at your end too before merging.
I peeped the Nextcloud changelog and it doesn't look like anything major happened in those two releases. Personally happy for this to remain a "patch" version upgrade on the Co-op Cloud side as long as an upgrade or two goes smoothly.
Perfect, I will perform a few tests this week coming and report back, it will be good if you can also test from your end and see if you're also happy with the result of the switchover to V25.
@javielico Some thoughts: that sounds like a nice idea. That might require some testing and changes in other files e.g. in the entrypoint or may have some unforseen consequences, so I would rather perhaps open up an issue to see if there is feedback on it. Several folks rely on the recipe as it is now. Opening up another PR with just those changes would be good too.
Good point, I just thought I'd mention it thinking about the future not necessarily to change it now.
Nextcloud and Nginx up versionto WIP: Nextcloud and Nginx up versionI suppose we can close this issue now that newest version has been merged, just to double check have you also updated the Nginx version @decentral1se?
Ah @javielico apologies, I forgot this PR was open already... I didn't upgrade the Nginx version, so maybe this PR could be re-worked to do that? Or I could pick it up next time. As you like!
Pull request closed