I had written earlier how learning the language before the framework is more important.
It is important to know which parts is part of the language, and which comes from the framework.
This becomes more important when there are defacto web frameworks (rails in ruby, django in python, phoenix in elixir.. maybe more) For a newcomer who is learning both the language and framework together (or back to back, or worse learning the language via the framework tutorials :shudders: )
Continue Reading »
In a multi-tenant rails application, usually we extract the tenant, before we process it further. Sometimes, the process requires us to process the data in background (via Sidekiq) and because the background job also needs to query the DB, it also needs to set tenant.
Turns out, we can pass “some” data from the controller to the sidekiq job via ActiveSupport::CurrentAttributes While, sidekiq may need to set the tenant again (for more DB queries) but one can save at least one query (to find out the account itself)
Continue Reading »
I came across this from (now defunct) rails app site.
They seem to provide a lot of stuff in their open source version.
Seems like a good framework to get started on the side project or MVP
Other paid features are worth paying when your app starts making money.
I need to spend more time on digging deeper, and actually trying it out.
Some days ago, I came across a requirement where I needed to run some rails code at the end of deployment. We use the Capistrano tool for the deployment, and it has great support for hooks like after 'deploy:published', 'some_task'
Most of the examples show some system commands, since Capistrano is a deployment tool, and isn’t running rails.
But I didn’t know that, being new to rails ecosystem.
So at first, at just called a background job that needed to talk to third party system and get some data, once the rails server is up.
Continue Reading »