We are a freelance developer that have been building software systems since 2000, that caters to small business enterprise in the local market, until recently we have innovated our tools and equipment and upgraded to Ruby on Rails. We, still apply our methodology with process flow improvements to the design of newer systems we develop.

Rails Application deployment is quite complicated to some, so we have devised a solution by shipping it embeded to a portable linux server similar to Raspberry Pi or thin clients, making it possible for non-tech business owners to implement it easily on their business infrastructure via simply hooking it up to a router and start using it on the fly.

We can also help you build your own custom Rails Application to fit your business requirements, Get in touch with us so we can start building your project for you.

Ruby on Rails

Ruby on Rails is intended to emphasize Convention over Configuration (CoC), and the Don't Repeat Yourself (DRY) principle. "Convention over Configuration" means a developer only needs to specify unconventional aspects of the application. For example, if there is a class Sale in the model, the corresponding table in the database is called sales by default. It is only if one deviates from this convention, such as calling the table "products sold", that the developer needs to write code regarding these names. Generally, Ruby on Rails conventions lead to less code and less repetition.[37] "Don't repeat yourself" means that information is located in a single, unambiguous place. For example, using the ActiveRecord module of Rails, the developer does not need to specify database column names in class definitions. Instead, Ruby on Rails can retrieve this information from the database based on the class name. "Fat models, skinny controllers" means that most of the application logic should be placed within the model while leaving the controller as light as possible. Source: www.wikipedia.org .