title: Rails app logic internationalization
body: <p>I'm develping a rails app that will have separate instances run in different countries. Internationalization takes care of the language issues, but when there are some minor logical changes I'm not sure how to approach. One example would be the payment methods - in each country different options will be shown to the users with different integrations. Another examples would be salaries -  taxes and social securities are completely different from country to country so we'll need to take this into account. </p>
  
  <p>The differences are not that many so in general I don't want to create a different git branch for each country, but I might be wrong about that. </p>
  
  <p>The solution I'm currently thinking of is to have a different environment for each country - "production_germany", "production_france" etc. and depending on that to load a different yml file with all the necessary variables that I'll be needing for this country. Then create some "Manager" class that will make decisions what special classes to load and what things to show on the views(wherever there are differences). For example I can have the salary calculation classes for germany in "salary_calculation/de" and for france in "salary_calculation/fr" and load only the ones I need.</p>
  
  <p>What would be your solution? </p>