Today I discovered a fantastic tool for managing my Docker containers based on docker-compose.yml files — it’s called Dockge.
Dockge isn’t just another wrapper around Docker — it genuinely impressed me. It has a beautiful, modern interface, works fast, and most importantly, makes it super easy to start, stop, and monitor services in a stack. Some highlights:
At the time of writing, AI integration in RubyMine is still lacking.
As a workaround, we can use two tools in tandem:
To make this setup efficient, it would be great to synchronize these tools.
For example, when we open a file in RubyMine, the same file could also be opened automatically in Cursor AI.
In complex Ruby on Rails applications, it’s common to route requests based on dynamic conditions, such as the value of a query parameter. One powerful way to handle such cases is to use custom routing constraints. This article demonstrates how to route the same endpoint to different controllers based on the subject_type parameter.
Suppose we want to handle updates to details of various animal types—dogs, cats, and mice—through a single endpoint like:
![Featured image for Hidden Performance Trap in Rails: Avoid nil in .where(id: [...])](/rails-where-id-nil-performance-trap/rails-nil-performance-trap.png)
