Dependencies decide whether your roadmap ships on time or keeps slipping. You see them when „simple” integrations drag on and security fixes hijack sprints. This article explains what dependency management is, why Product Managers should care, and how small process changes can remove hidden blockers. You will get a simple checklist and questions to use […]
Ruby on Rails (RoR) isn’t just a technology; it’s the launchpad for innovation. At Selleo, we’ve spent over fifteen years mastering this powerful web framework.
When our client—a fast-scaling HR and EdTech platform—approached us to rethink their infrastructure, their Ruby on Rails app was already carrying a significant load.
Using Ruby on Rails could be what you need to take your web app to the next level so stay tuned as we find out how to find and hire Ruby on Rails programmers.
In this article, I will blend the technical aspects of designing SaaS using the Ruby on Rails framework to prove it is a perfect choice for your project.
It is not unusual for a new technology to originate from a successfully developed project. For example, we can find the pattern in the story of a web framework for Python – Django, which was originally developed to manage a number of news-oriented sites for the LJworld company.
Thanks to a good combination of RSpec and Kameleon, we have managed to write an expressive end-to-end test as well as six supportive tests in no time at all.
In the last article we added a few GraphQL mutations to our test application. It is time to create automated tests for each of them. But first things first, we need to set up `RSpec` in order to write better specs.
The Ruby on Rails framework is powerful in many ways. One of its strong points is that Ruby on Rails is being shipped with ActiveRecord – an Object Relational Mapping system. ActiveRecord comes up with its own DSL, which lets you write Ruby code, which in turn is translated to SQL, allowing you to use database native features, including “locking”.
This guide will show you how to upgrade to Rails 6. We’ll cover the upgrade process in general and provide helpful tips to make your upgrade as smooth as possible.
Today we are going to add specs (again, we will focus only on the happy paths) for GraphQL queries. But there is one thing about the current implementation of the queries that I don’t like. We have everything defined in one file: `app/graphql/types/query_type.rb`
In this article, I would like to focus on adding GraphQL mutations. We will be working on the test application we created previously in this article. It might be helpful for you to know the structure, models, and types we are using so I encourage you to take a look.
Sep 17, 2020 ・3 min-read
SaaS Founder Starter Academy
Everything you need to know to successfully launch your SaaS app.