Did you know that MySQL initializes with a temporary server, which can make orchestrating a containerized app more complicated? Using a custom health check, we can work around this little quirk.
Duck typing is an effective way of decoupling and future-proofing code (and also settling stupid food debates).
Let's consider a couple common issues where Ruby on Rails applications might inadvertently reveal too much information--posing security risks.
When you're working on a Ruby on Rails application, the Model-View-Controller (MVC) pattern usually captures most of what you want the app does. But not everything fits neatly into MVC. Sometimes, you need to make decisions about where to put logic that doesn't quite belong in a model, view, or controller.
It shouldn't be this hard to write tests for API-connected functionality in a web app.
Dev containers are the cheat code to getting really old Rails apps running on modern hardware.
Most Rails apps don't (or shouldn't) need a full time person to keep them running.
Rails 7.2 introduces a clear maintenance policy with defined support timelines, making it easier for developers to plan upgrades-learn how this change impacts older versions and how Neomind can help keep your app secure and up-to-date.
Dev containers are a great augmentation to Docker containers when trying to get legacy Rails applications to run on modern hardware. This post explores my experiments getting a Rails 4.1 and Ruby 2.3 app running on an M1 Macbook Pro.
Some people don't think "sustainable software" means what I think it means. What would you call it?
We use optional analytics services to understand how people find and use this site. These stay off unless you accept. See our privacy and cookie policy.