Consider running 'rails about` after Capistrano deployments

[eoinkelly]

rails about loads the rails app and dumps a bunch of useful info about it. It might be nice to have this info in CI output after deployments.

Example output:

About your application's environment
Rails version             7.0.4
Ruby version              ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [arm64-darwin21]
RubyGems version          3.3.20
Rack version              2.2.4
Middleware                Webpacker::DevServerProxy, ActionDispatch::HostAuthorization, Rack::Sendfile, ActionDispatch::Static, ActionDispatch::Executor, HandleBadEncodingMiddleware, ActiveSupport::Cache::Strategy::LocalCache::Middleware, Rack::Runtime, Rack::MethodOverride, ActionDispatch::RequestId, RequestStore::Middleware, ActionDispatch::RemoteIp, Rails::Rack::Logger, ActionDispatch::ShowExceptions, Sentry::Rails::CaptureExceptions, WebConsole::Middleware, ActionDispatch::DebugExceptions, Sentry::Rails::RescuedExceptionInterceptor, ActionDispatch::ActionableExceptions, ActionDispatch::Reloader, ActionDispatch::Callbacks, ActiveRecord::Migration::CheckPending, ActionDispatch::Cookies, ActionDispatch::Session::CookieStore, ActionDispatch::Flash, ActionDispatch::ContentSecurityPolicy::Middleware, ActionDispatch::PermissionsPolicy::Middleware, Rack::Head, Rack::ConditionalGet, Rack::ETag, Rack::TempfileReaper, Warden::Manager, ActionDispatch::Flash, Flipper::Middleware::SetupEnv, Warden::JWTAuth::Middleware, Flipper::Middleware::Memoizer, Rack::Attack
Application root          /path/to/your/repo
Environment               development
Database adapter          postgresql
Database schema version   20221024221215

[robotdana]

it should happen after the deployment is complete so it doesn't slow a deployment & it if it does fail it should do so in a way that doesn't make it look like the deploy failed.

i don't think it will take any more time than running any rake task because it's just getting the rails environment up