WIP: pr-15.2.0 - Updating to nextcloud 34.0.2 and EuroOffice #112

2026-08-11T20:51:08Z

ineiti commented

2026-08-11 20:51:08 +00:00

Adding EuroOffice as a compose file

The version bump is directly to 15.2.0+34.0.2, as there were two versions, 15.0.0 and 15.1.0, which have been yanked.

Adding EuroOffice as a compose file The version bump is directly to 15.2.0+34.0.2, as there were two versions, 15.0.0 and 15.1.0, which have been yanked.

ineiti added 1 commit 2026-08-11 20:51:08 +00:00

Updating to nextcloud 34.0.2 and EuroOffice 13ca1b0c20

Adding EuroOffice as a compose file

ineiti referenced this pull request

2026-08-11 20:51:27 +00:00

pr-15.0.0 - Updating to nextcloud 34.0.2 #100

ineiti referenced this pull request

2026-08-11 20:51:40 +00:00

pr-15.1.0 - Adding EuroOffice as a compose file #101

ineiti changed title from ~~Updating to nextcloud 34.0.2 and EuroOffice~~ to WIP: pr-15.2.0 - Updating to nextcloud 34.0.2 and EuroOffice

2026-08-11 20:52:07 +00:00

ineiti referenced this pull request

2026-08-11 20:53:14 +00:00

Updating to the latest nextcloud version #102

dannygroenewegen commented

2026-08-13 10:46:02 +00:00

Looks good! I also wanted to try this out at some point. The integration is fine, but I think Euro-Office should be in its own recipe. To match the existing Collabora and Onlyoffice. I would also like to run Euro-Office once for multiple Nextcloud instances, so a separate recipe would be a better fit for that. Also happy to co-maintain for the if I keep using this.

dannygroenewegen requested changes 2026-08-13 11:01:58 +00:00

compose.eurooffice.yml

						
				@@ -0,0 +2,4 @@

				services:

				  app:

				    secrets:

				      - eurooffice_jwt

dannygroenewegen commented

2026-08-13 10:48:15 +00:00

Secret length should be max 12, see this.

Secret length should be max 12, see [this](https://docs.coopcloud.tech/maintainers/handbook/#r015-long-secret-names).

compose.eurooffice.yml

						
				@@ -0,0 +77,4 @@

				      # docservice starts against an empty DB, errors on missing task_result /

				      # doc_changes, never binds its port, and gets healthcheck-killed in a loop.

				      - source: eurooffice_createdb

				        target: /docker-entrypoint-initdb.d/createdb.sql

dannygroenewegen commented

2026-08-13 10:53:46 +00:00

Looks like this is fixed in v9.3.3. See closed issue Euro-Office/DocumentServer#124, fixed by #304.

Looks like this is fixed in v9.3.3. See closed issue [Euro-Office/DocumentServer#124](https://github.com/Euro-Office/DocumentServer/issues/124), fixed by [#304](https://github.com/Euro-Office/DocumentServer/pull/304).

compose.eurooffice.yml

						
				@@ -0,0 +110,4 @@

				configs:

				  entrypoint_eurooffice:

				    name: ${STACK_NAME}_entrypoint_eurooffice_${ENTRYPOINT_EUROOFFICE_VERSION}

dannygroenewegen commented

2026-08-13 10:54:39 +00:00

Like secrets, configs also have this character limit. We should also try to limit this to 12 chars.

ineiti commented

2026-08-14 08:58:45 +00:00

Thanks for the comments - I'll create a separate recipe then for Eurooffice. What do we want to do with those who (unfortunately) installed 15.1? Add a mention in the next release that Eurooffice will be removed?

Also, whom do I ask to create a new recipe? I'm not allowed to add new recipes to the coop-cloud org.

Thanks for the comments - I'll create a separate recipe then for Eurooffice. What do we want to do with those who (unfortunately) installed 15.1? Add a mention in the next release that Eurooffice will be removed? Also, whom do I ask to create a new recipe? I'm not allowed to add new recipes to the coop-cloud org.

dannygroenewegen commented

2026-08-14 09:30:18 +00:00

Thanks for the comments - I'll create a separate recipe then for Eurooffice. What do we want to do with those who (unfortunately) installed 15.1? Add a mention in the next release that Eurooffice will be removed?

I think a release note describing euro-office can be enabled by deploying the euro-office recipe, with a link to the repo, and following the section in the readme.

Also, whom do I ask to create a new recipe? I'm not allowed to add new recipes to the coop-cloud org.

I'm not aware of any clear process for this. I think ask in the Tech channel on Matrix to make the euro-office repo and euro-office-maintainers team with us in it.

> Thanks for the comments - I'll create a separate recipe then for Eurooffice. What do we want to do with those who (unfortunately) installed 15.1? Add a mention in the next release that Eurooffice will be removed? I think a release note describing euro-office can be enabled by deploying the euro-office recipe, with a link to the repo, and following the section in the readme. > Also, whom do I ask to create a new recipe? I'm not allowed to add new recipes to the coop-cloud org. I'm not aware of any clear process for this. I think ask in the Tech channel on Matrix to make the euro-office repo and euro-office-maintainers team with us in it.

👍 1

You are not authorized to merge this pull request.

This pull request can be merged automatically.

This pull request is marked as a work in progress.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin pr-15.2.0+34.0.2-fpm:pr-15.2.0+34.0.2-fpm

git checkout pr-15.2.0+34.0.2-fpm

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/nextcloud#112