Book Image

Ruby on Rails Enterprise Application Development: Plan, Program, Extend

By : Elliot Smith, Rob Nichols
Book Image

Ruby on Rails Enterprise Application Development: Plan, Program, Extend

By: Elliot Smith, Rob Nichols

Overview of this book

<p><br />All businesses have processes that can be automated via computer applications, thereby reducing costs and simplifying everyday operations. This book demonstrates that a modern web application framework makes an ideal platform for such applications. It shows how the attributes that make the Rails framework so successful for Internet applications also provide great benefit within a business intranet. These attributes include easy roll-out and update of applications, centralized processing and data handling, simple maintenance, straightforward code development, and scalability.<br /><br />Ruby on Rails is an open-source web application framework ideally suited to building business applications, accelerating and simplifying the creation of database-driven websites. Often shortened to Rails or RoR, it provides a stack of tools to rapidly build web applications based on the Model-View-Controller design pattern.<br /><br />This book covers topics such as installing Ruby, Rubygems, and Rails on Windows, Linux, and Mac OS X; choosing and installing a database; installing an IDE for Rails development; setting up a Subversion repository to manage your code; creating a new Rails application; understanding Rails models; understanding controllers and views; improving user interfaces with Ajax; using Rails plugins to manage file uploads; using Capistrano to manage application deployment; techniques for scaling Rails applications, such as caching and using Apache to proxy through to the Mongrel server. The example application is straightforward to develop, easy to roll out, and simple to maintain.</p>
Table of Contents (16 chapters)
Ruby on Rails Enterprise Application Development
Credits
About the Authors
Preface
Index

Easy Access to the Application


Then Ken raises the first issue. "How am I going to get back to that web page?". Rory's first thought is to add a bookmark, but when he opens Ken's bookmarks his eyes are assaulted by a cascade of disorganized bookmarks. He should have realized that they would not be well managed when he saw Ken's desktop was packed full of shortcuts to applications and documents.

In general, users hate having to remember the URL to an application. So, if you want users to use your application regularly, you need to give them an easy way in.

Use Routes to Simplify the Entry Point URL

The URL Rory used to access the application during the demonstration was:

http://intranet.company.local/people/list

In fact, he missed a trick here. Because there is an index action in the people controller, and as discussed in Chapter 5, Rails will use that action to return content to the browser if no action is specified in the URL. So, Rory could have used:

http://intranet.company.local/people

However...