Gain insights into Ruby on Rails fundamentals, creating projects, deploying, CRUD operations, user authentication, and session management. Build foundational skills to develop complex applications.

working4.tar.gz

default

hello

crud migration

crud CR

crud app1

redd

testing

votable_fix

CRUD new1

In this course, you will learn the fundamentals of Ruby on Rails to build your own application.

You will start by learning how to create a new project, deploy to a Rails server, and the Rails design pattern. After that, you’ll learn how to perform CRUD operations, handle user authentication, and manage sessions.

Once you finish this course, you’ll have the foundations in place to build more complex applications to add to your portfolio.

Introduction to Ruby on Rails

# Model-View-Controller
In our introduction to Rails, we said that Rails uses the Model-View-Controller (MVC) architecture. But what is that exactly, and why do we need it?

MVC is a design pattern that separates the program logic into three interconnected elements. Essentially, it enforces a separation between the data in the application (such as user information) and the code used to display it. Rails uses the
#concept=thin_client#thin client#concept#
 approach to the MVC architecture, which places almost the entire model, view, and controller logic on the server-side. 




**User**: The user (via a browser) opens a connection to the server and sends a *request*. The *request* is received by the web server and then passed on to the *controller*. The *controller* is responsible for responding to the *request* and converting it to commands for the *view* and the *model*.

**Controller**: A controller is responsible for making sense of the *request* and determining the appropriate response. In some cases, it will render a view immediately. Otherwise, it will fetch or save data to the model and render the updated view by creating an HTML output. A *router* decides which controller receives which request.

**Model**: A model is a **Ruby** object that is responsible for communicating with a database. It provides structure to the application's data and mechanisms to manage the records contained within the database.

**View**: A view is a template that is converted to HTML and is returned back to the browser where the *request* originated from. The view gets rendered onto the web page that is displayed to the *user*.



A high-level overview of the Model-View-Controller architecture.

Introduction to Ruby on Rails

CRUD on Rails

Your First Rails Application!

Comments

Testing

Conclusion

Rails Design Pattern

Model-View-Controller