We have been developing, supporting and maintaining Ruby on Rails web applications for over 10 years here at Foxsoft. In that time we’ve learned a few things about how best to approach securing and maintaining applications for the long term.
As developers, there are some better practices that, if followed, will make your future life more comfortable as you continue to develop the application.
Nobody likes paying for insurance, but we do want the certainty and peace of mind that it provides. In the event of an incident, we’re glad that we’re covered and able to resume normality as quickly as possible.
Upgrading a Rails application is almost never the top priority for a company, but over time it pays to remain up to date. You ensure that bugs and security vulnerabilities get fixed. Plus, new features make future feature development quicker and easier.
If your Ruby on Rails application has been around for more than a few years or so then here are 3 actions you should take.
Here are 6 things you should check you have covered so when the proverbial hits the fan, you’re not the one running for cover.
Unless you’ve had your head under a rock for the past few years, you will likely have noticed the increase in SaaS (Software-as-a-Service) companies. Most software vendors have begun moving towards a subscription model. It makes sense.
“We build good quality software!” – says every software developer.
Unlike any physical product, software doesn’t need to be “finished”. It can begin to be useful immediately, the moment a single function is complete.
Anyone who tells you they write bug-free code is a liar—they just haven’t found them all yet.