There is one hack, the memcached gem to get it to accept 4Mb key size. The memcached server can handle it but the old gem acted as a gatekeeper on this value. So a sed script changes the value. But that is the only one On Mon, 30 Oct 2023 at 15:56, Frank J. Cameron via ruby-talk < ruby-talk@ml.ruby-lang.org> wrote:
On Mon, Oct 30, 2023, at 10:16 AM, Peter Hickman via ruby-talk wrote:
So we build a container around 14.04, compiled ruby 1.8.7 and installed the necessary gems. Fired it up and pointed the load balancer at it. It is working just fine and we can finally breath. To be clear the container only contains the Rails app and the unicorn_rails application server, the rest of the stack, Nginx and the database, live in their own 22.04 containers
Now the odd part, despite the application running in production mode it logs like it is in development mode and the logs are bloated with all the database activity. The log files are a minimum 2/3 database logging. The old installation doesn't do this
Any chance that gem code may have been edited in-place to alter the database logging on the old server?
I know that's something I should never do, but I have done it a time or few. :-) ______________________________________________ ruby-talk mailing list -- ruby-talk@ml.ruby-lang.org To unsubscribe send an email to ruby-talk-leave@ml.ruby-lang.org ruby-talk info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-talk.ml.ruby-lang.org...