Do you want to go technical?


We have 15+ years of experience with legacy Rails 2.3.x code to the most recent Rails 4.2.x versions.

Upgrade - We made many Rails 2.x -> 3.x and 4.x and 3.x to 4.x upgrades with sophisticated gem updates or even gem patching.

Up-to-date maintenance - If you want to run on the latest stable Rails and gem versions, we commit to regularly apply the updates.

Legacy maintenance - Do you have a legacy project that you wouldn’t upgrade rather apply security patches and ensure stable running on current Rails version? We can maintain actual version and respond to your ad-hoc fix and feature requirements.


How would you access our development team

Slack (or Skype) - We create project rooms for instant messages.

Skype / Hangouts - We organize weekly and if required ad-hoc video calls for standups and screen shared presentations.

Jira / Bitbucket / GitHub / Codebase (or the client’s own) ticketing system - We have a prioritized and ordered list of tasks that clearly displays project status and contains communication details about a given feature.

Google Docs - Planning and documentation usually requires more flexibility than a ticketing system. We found Google Docs as a great and widely accessible collaboration tool for creating documentation or other frequently changed documents.


How would you access the latest code

GitHub / Bitbucket / Stash / Codebase (or the client’s own) git repository - We keep the project’s git repository in the hands of our client. The latest code is always up there organized into development, staging and production branches. Creating fix and feature branches allows us to apply completed features and accepted hotfixes in any order. We can fix a bug on production while we are testing a huge feature on staging.

Heroku / Engine Yard / custom created staging application with the latest code - We always create staging application(s) that work as a sandbox environment to demo and test the latest features. We deploy the new code to the production server only if our client is satisfied.


How we set up our development environments

Vagrant - We set up development virtual machines to simulate production environment as precisely as possible and to ease knowledge sharing between team members.

Data protection - We develop seed data for development and testing. In case real data is required for failure reproduction we always ask for authorization.


How we usually deploy

Simple git push - for managed hosts like Heroku

Multi-stage Capistrano deployments - We can setup custom configured deployment workflows for remote virtual machines.

No downtime / scheduled deployment with rollback ability