From e08ba7efbe6eb912ab7d6e179154146164796a50 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Javi=20Mart=C3=ADn?= Date: Mon, 15 Apr 2024 14:43:36 +0200 Subject: [PATCH] Use JSON to serialize messages The new serializer can decrypt legacy messages using the `marshal` serializer, so there's no risk of losing data when upgrading. Since we aren't using applications with several servers, where upgrading some servers might cause issues on the servers that aren't upgraded yet, we're enabling the option. [1] See comments in pull request 42846 in https://github.com/rails/rails --- config/initializers/new_framework_defaults_7_1.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/initializers/new_framework_defaults_7_1.rb b/config/initializers/new_framework_defaults_7_1.rb index f350b00a9..eca6cac20 100644 --- a/config/initializers/new_framework_defaults_7_1.rb +++ b/config/initializers/new_framework_defaults_7_1.rb @@ -128,7 +128,7 @@ Rails.application.config.active_record.query_log_tags_format = :sqlcommenter # servers, first deploy without changing the serializer, then set the serializer # in a subsequent deploy. #++ -# Rails.application.config.active_support.message_serializer = :json_allow_marshal +Rails.application.config.active_support.message_serializer = :json_allow_marshal ### # Enable a performance optimization that serializes message data and metadata