AxiomQ

At the beginning of their career many new Rails developers put complex presentation logic directly into the templates, that looks something like this: At that point, that kind of solution seems reasonable, but after awhile they all ask the same question: Is this the right place for such a code? Of course, the answer is

Important Things You Need To Improve About Your Web Business

Regardless whether your business is a thriving IT startup or you just run a small local business, you feel the need to make your presence felt online. Having a website or even trading online is a must today. However, merely having a web business is far from enough: you must improve it constantly, and here

Desktop computers

So… You have just founded your own firm, defined the product or the service you are selling, and even did some market research to see who your potential buyers are. The only thing needed before the money starts pouring in is the trivial issue of web development. Well, things might just not be as simple

AxiomQ

We created AxiomQ by merging two companies. Both of them had their own sites. To keep search engines happy we need to setup 301 redirects. Unfortunately, one site was running on Github Pages which doesn’t support 301 redirects. The solution was to create a simple Rack app, use rack-rewrite gem to redirect traffic, and deploy

AxiomQ

Recently we were working on a Rails project where we needed to import data from legacy database.In the next few steps I will describe how we did it. In database.yml we specified information for interaction with legacy data. In models directory, we added a legacy directory to which we will later add all legacy models.

Closure actions were introduced in Ember v.1.13.0 and they brought a lot of improvements over old action handling mechanism in Ember. These improvements enabled Ember to adopt new data flow model called – Data Down Actions Up (DDAU) that simplified communication between parent and child components. What are closure actions? Closure actions are based on

Most modern web app deployments have automated scripts that perform all tasks needed to deploy the app. They handle all the dirty details, while the developer just needs to do something simple like cap deploy. In other words, usually you don’t need to access the remote servers directly. However, sometimes you run into one-time tasks

While working on different projects and in different environments, we often need to export a dump from one database and then import it into another. A while ago Slobodan wrote how to export and import a mySQL dump, and here is a guide how do it for PostgreSQL. Export a PostgreSQL database dump To export

Starting with v9.2, PostgreSQL added native JSON support which enabled us to take advantage of some benefits that come with NoSQL database within a traditional relational database such as PostgreSQL. While working on a Ruby on Rails application that used PostgreSQL database to store data, we came a across an issue where we needed to

I recently worked on a Rails project, which had parts of pages in different languages. That may be a problem if you have already translated their entire text to all required languages. You can even be tempted to hardcode parts of the text into other languages. Fortunately, there is an elegant way to solve that