attempt to fix the /up error in production

Gemfile

@@ -22,7 +22,7 @@ gem 'remote_syslog_logger', '1.0.4'
 
 # gem 'locomotivecms_search', path: '../../search'
 
-gem 'locomotivecms', github: 'locomotivecms/engine', ref: '055c488b'
+gem 'locomotivecms', github: 'locomotivecms/engine', ref: 'e6fb512c'
 gem 'locomotivecms_steam', github: 'locomotivecms/steam', ref: '4386db6', require: false
 gem 'locomotivecms_common', github: 'locomotivecms/common', ref: 'c78da158', require: false
 # gem 'locomotivecms_search', github: 'locomotivecms/search', ref: '35e5813'

Gemfile.lock

@@ -23,8 +23,8 @@ GIT
 
 GIT
   remote: https://github.com/locomotivecms/engine.git
-  revision: 055c488bcaaba9bc465aeb93d869fdb8ede6ec53
-  ref: 055c488b
+  revision: e6fb512c08f7108eb024b7e56b8f4f153570f78e
+  ref: e6fb512c
   specs:
     locomotivecms (4.2.0.alpha2)
       actionmailer-with-request (~> 0.5.0)

config/deploy.yml

@@ -87,9 +87,10 @@ env:
 #     accesslog.format: json
 
 # Configure a custom healthcheck (default is /up on port 3000)
-# healthcheck:
-#   path: /healthz
-#   port: 4000
+healthcheck:
+  # path: /healthz
+  # port: 4000
+  interval: 5s
 
 # Bridge fingerprinted assets, like JS and CSS, between versions to avoid
 # hitting 404 on in-flight requests. Combines all files from new and old

config/environments/production.rb

@@ -99,4 +99,5 @@
   end
 
   config.hosts << 'localhost:3000' # required when running within a Docker container (Kamal)
+  config.hosts << '127.0.0.1:3000'
 end

config/routes.rb

@@ -2,7 +2,7 @@
 
   # Reveal health status on /up that returns 200 if the app boots with no exceptions, otherwise 500.
   # Can be used by load balancers and uptime monitors to verify that the app is live.
-  get 'up' => 'rails/health#show', as: :rails_health_check
+  get '/up', to: 'rails/health#show', as: :rails_health_check
 
   # Demo site
   get '/locomotive/demo', to: 'demo#show'