Rails 4. Web Application Development
Here is a new edition of the best-selling Agile web development with Rails , written by Sam Ruby - head of the Apache Software Foundation and Atom format developer, Dave Thomas - author of the book Programming Ruby and David Hansson - creator of Rails technology. Rails is an environment that facilitates the development, deployment, and maintenance of web applications. In the time since its first release, Rails has gone from a little-known technology to a global phenomenon and has become exactly the medium that they choose to create so-called "Web 2.0 applications." This book, which has long become a desktop for learning Ruby on Rails, is intended for all programmers who are going to create and deploy modern web applications. From the first part of the book, you'll get an introduction to the Ruby language and general information about the Rails environment itself. Next, using the example of creating an online store, you will learn the concepts underlying Rails. The third part covers the entire Rails ecosystem: its functions, capabilities, and additional modules. The updated edition of the book describes work with Rails generation 4 and Ruby 1.9 and 2.0.
The book on the website of the publisher PETER
')
Table of contents
Excerpt
This book is intended for programmers who are eyeing the creation and deployment of web applications. These include application programmers who have not previously worked with Rails (and possibly even strangers to Ruby), and programmers who are familiar with the basics, but who want to come to a deeper understanding of the Rails environment.
Some knowledge of HTML, Cascading Style Sheets (CSS) and JavaScript, in other words, we are talking about the ability to understand the source code of web pages. You do not need to be experts on this topic; the most difficult thing to do is to transfer the program material of this book into files, the entire volume of which can be downloaded.
From time to time you will come across box "David says ...". In them is David Heinemeier
Hanson (David Heinemeier Hansson) will share with you valuable information about Rails - give explanations and recommendations, show tricks, etc. Since he is the creator of Rails, you should not skip these sidebars if you want to study this environment professionally.
Sometimes a certain mythical developer named Joe appears in the book, asking questions about the substance of the material being studied, to which we respond.
This book is not a Rails reference guide.
Our experience suggests that reference manuals for most people cannot serve as textbooks. Instead, we showed most of the modules and many of their methods, either in examples or in textual descriptions in the context of using these components and working together.
You will not find here hundreds of pages with listings of API functions. There are good reasons for this - you get all the relevant documentation every time you install Rails, and it will undoubtedly be newer than the material presented in this book. If you install Rails using RubyGems (which follows our recommendations), you just need to start the gem documentation server (using the gem_server command), and you can access the description of all the Rails API functions by typing localhost : 8808 in the address bar. The creation of additional documentation and manuals will be discussed in Chapter 18, in the section “Place for Documentation”.
In addition, you will see that Rails itself helps you by creating answers that clearly identify any errors found, as well as showing ways that tell you not only where the error was detected, but also how to get to it. An example can be seen in Figure 10.3. If you need more information, look at section 10.2 “Step D2: error handling” to see how you can insert instructions for keeping a logbook.
The book on the website of the publisher PETER
')
Table of contents
Excerpt
Who is this book for?
This book is intended for programmers who are eyeing the creation and deployment of web applications. These include application programmers who have not previously worked with Rails (and possibly even strangers to Ruby), and programmers who are familiar with the basics, but who want to come to a deeper understanding of the Rails environment.
Some knowledge of HTML, Cascading Style Sheets (CSS) and JavaScript, in other words, we are talking about the ability to understand the source code of web pages. You do not need to be experts on this topic; the most difficult thing to do is to transfer the program material of this book into files, the entire volume of which can be downloaded.
David says ...
From time to time you will come across box "David says ...". In them is David Heinemeier
Hanson (David Heinemeier Hansson) will share with you valuable information about Rails - give explanations and recommendations, show tricks, etc. Since he is the creator of Rails, you should not skip these sidebars if you want to study this environment professionally.
Joe asks ...
Sometimes a certain mythical developer named Joe appears in the book, asking questions about the substance of the material being studied, to which we respond.
This book is not a Rails reference guide.
Our experience suggests that reference manuals for most people cannot serve as textbooks. Instead, we showed most of the modules and many of their methods, either in examples or in textual descriptions in the context of using these components and working together.
You will not find here hundreds of pages with listings of API functions. There are good reasons for this - you get all the relevant documentation every time you install Rails, and it will undoubtedly be newer than the material presented in this book. If you install Rails using RubyGems (which follows our recommendations), you just need to start the gem documentation server (using the gem_server command), and you can access the description of all the Rails API functions by typing localhost : 8808 in the address bar. The creation of additional documentation and manuals will be discussed in Chapter 18, in the section “Place for Documentation”.
In addition, you will see that Rails itself helps you by creating answers that clearly identify any errors found, as well as showing ways that tell you not only where the error was detected, but also how to get to it. An example can be seen in Figure 10.3. If you need more information, look at section 10.2 “Step D2: error handling” to see how you can insert instructions for keeping a logbook.
Source: https://habr.com/ru/post/215675/
All Articles