Skip to content

Conversation

7-zete-7
Copy link
Contributor

Due to dunglas/mercure#939 and the deprecation message, it makes sense to apply the Mercure configuration changes.

See:

Due to dunglas/mercure#939 and the deprecation message, it makes sense to apply the edits to update the Mercure configuration.

See https://github.com/dunglas/mercure/blob/main/docs/UPGRADE.md#017
@7-zete-7
Copy link
Contributor Author

It might be more correct to replace it with the new configuration format

 {$SERVER_NAME:localhost} {
 	# ...
 	mercure {
+ 		# Transport to use (default to Bolt)
+		transport bolt {
+			path /data/mercure.db
+		}

However, this is already the default value. Backward compatibility (configuration via the environment variable MERCURE_TRANSPORT_URL) will also be broken.

@dunglas
Copy link
Owner

dunglas commented Mar 27, 2025

Simplifying the config is ok. MERCURE_TRANSPORT_URL BC is handled directly by Mercure.

@dunglas dunglas merged commit 46fa840 into dunglas:main Mar 27, 2025
2 checks passed
@7-zete-7
Copy link
Contributor Author

7-zete-7 commented Mar 27, 2025

I was too hasty with the default value. I found out that Mercure's default path option is ./bolt.db. To keep the value the same, the MERCURE_TRANSPORT_URL environment variable must be explicitly set.

See https://github.com/dunglas/mercure/blob/6e73d7278ceb43c7cfd941089fe7bf984617a515/bolt.go#L88-L90

maxhelias pushed a commit that referenced this pull request Mar 27, 2025
This should return the path that was changed in #766.
@7-zete-7 7-zete-7 deleted the patch-1 branch April 8, 2025 09:27
gatiengnv pushed a commit to gatiengnv/stravinsight that referenced this pull request Apr 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants