Webpacker can be an interesting alternative to the popular create-react-app tool. Learn how to use this gem to integrate Rails with React.
It’s been almost half a year since I started my job as an Intern Ruby on Rails Developer at Nopio (now a more experienced Junior) and I’ve decided to share some thoughts on how expectation compares with reality in regards to your first job in web development, and to offer some advice that may be helpful from someone who has been there.
Thankfully, there is a really useful Ruby gem called rack-rewrite that can handle all redirects for you. The implementation is really easy and doesn’t take a lot of time. The biggest advantage of this library is the fact that you can use it with pure Ruby application, without Rails.
Migrations in Rails are files, which are responsible for making any changes in the database and they convert a Ruby code into a SQL code.
For programmers, building a website from scratch requires maximum effort, skill and creativity. You definitely need the building process to flow with ease while you enjoy the work. Basically, this gives you ample time to ensure that you develop a website app with complete features and fewer issues. Gone are the days when you would spend months to build a web application. Ruby on Rails technology has made this absolutely easy for web developers. There are several gem versions that can be used to build web projects. It is just a matter of using the right gem to complete the relevant task on your Rails application. Find out the eleven commonly used gems in this article.
Single-Sign-On is a hot topic right now. Several applications such as Google, Facebook, and Github use it. Probably you’ve noticed on some pages a “Sign in with Google” or “Login with Facebook” button which enables a user to log in to a page without creating a new account. Once you click on the button, you are redirected to the application. This is referred to SSO; it’s a system which enables access to different pages/application using just one account, so you don’t need to care about multiple passwords and accounts.
Have you ever had the problem when you wanted to use an external API that didn’t have a ready-made library and you needed to write everything from scratch? You weren’t sure how everything should be split and separated in order to write readable and clear code? If you answered yes to any of these questions, this article is for you. I’ll show you how to write code that is responsible for connecting with the external API and how to split everything in order to write clear and maintainable code. It doesn’t matter if you use Rails or plain Ruby code, this code is flexible, so you can use it wherever you want.
I think a lot of you have faced a problem with your Rails application. It’s getting bigger and bigger, it’s really hard to maintain? You have too many models and they are too big? It’s really hard to find something in your code and you have duplicated it in many places? I think that it’s normal. By default, Rails gives us only three layers - models, controllers and views. Oh, I forgot, we also have helpers!
Have you ever dreamed about deploying your application to a server so you could show your friends or test how it would work in a production environment? Yeah, I remember when I wrote my first, simple web-application in Ruby on Rails and I wanted to deploy it somewhere. I was trying to find a good provider but a lot of hosting companies were only offering PHP support. So, basically, you were only able to deploy a WordPress or PHP application. Then I found one provider who claimed that with their servers, you could deploy your Ruby application with just one command, just like git push origin master and voila, everything is ready!