Skip to content

What are engines? #4

Open
Open

Description

@adamakhtar

@codereading/readers

Seeing as this is the first project to use Rails Engines it be a good start to understand exactly what an engine is.

How does an independent engine hook into a rails app? How does it get access to the rails apps db, params etc.

What other ways are there to create a project for rails use and how do they differ? Why would you choose one way over another?

I.e. why an engine and not just a simple gem. When should you use a vendored plugin?

Just some questions swimming in my mind.

Activity

  1. chamnap commented on Aug 30, 2012

    @chamnap
    Member

    As fas as I know, a rails engine is a way to share app controllers, models, and views to other apps. In rails 3, every rails app is also engine and can be bundled as a gem as well.

    There are two types of rails engines: mountable and full engine. Mountable engine is designed to be namespaced controllers, models,... For example, a forem engine, add forum to any existing rails applications. Some engines use the existing application layout (forem) or use its own layout (spree). A full engine is to augment something to an existing rails app.

    Vendored plugins are deprecated in Rails 4.0, and I think people will stop using that.

  2. agis commented on Aug 30, 2012

    @agis
  3. samnang commented on Sep 2, 2012

    @samnang
    Member

    Engines can be considered miniature applications that provide functionality to their host applications. A Rails application is actually just a “supercharged” engine, with the Rails::Application class inheriting a lot of its behaviour from Rails::Engine.

    I found few interesting links:
    http://edgeguides.rubyonrails.org/engines.html (I'm not sure why this page doesn't list in RailsGuides Index)
    http://gregmoreno.wordpress.com/2012/05/29/create-your-own-rails-3-engine/
    http://stackoverflow.com/questions/6118905/rails-3-1-engine-vs-mountable-app
    http://www.astjohn.ca/2011/08/06/rails-31-engines-mountable-or-full-part-1
    http://www.astjohn.ca/2011/08/07/rails-31-engines-mountable-or-full-part-2

    I'm still not so clear what are the benefit to create full engines instead mountable engines? Because I think most of the time we need mountable engines.

  4. samnang commented on Sep 2, 2012

    @samnang
    Member

    Just found Ryan Bigg's talk about Engines https://vimeo.com/41952172

  5. orlando commented on Sep 3, 2012

    @orlando

    @samnang 👍 thanks for the video

  6. adamakhtar commented on Sep 6, 2012

    @adamakhtar
    MemberAuthor

    Excellent resources everyone +1. These will be of a great help to newcomers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions