In Sinatra Best Practices: Part One we saw how to break up your Sinatra application into smaller bite-size pieces. Today, we’re going to explore testing, which will also compel us to address environment configuration.
While Sinatra’s one-file approach may work well for your one-off, smaller application – it can quickly become a mess as you add on multiple routes, route-handlers, helpers, and configuration. So what’s a programmer to do? In reading Sinatra’s documentation I’ve found a few morsels that have enabled us to split our otherwise-monolithic (I realize this …
What can we help you with?
Tell us a bit about your project, or just shoot us an email.