KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#dsh #dsh-plugin #developer-tools #ai-agent #claude-code #codex #typescript #ai-agents #deepseek-harness #mcp #cli #rust

rails-directory-structure-guide

★ 324 Open GitHub ↗

A guide to understanding Ruby on Rails directory structure

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Rails Directory Structure Guide

There is a default directory structure that __Ruby on Rails__ comes with. The Rails guides go in depth in explaining the folder structure, but does not talk about the extra folders that commonly get added in Rails Apps.

The goal of this guide is to be a central place to learn about __ALL__ the folders that are used in Rails apps, _not just the ones that come by default (Marked with asterisk)_.

We will also go over explaining __RSpec__ folder structure and any additional folders.

## Directory Structure

- [app](#app)
	- [assets](#app_assets)
	- [*cells](#app_cells)
	- [channels](#app_channels)
	- [controllers](#app_controllers)
	- [*decorators](#app_decorators)
	- [*forms](#app_forms)
	- [helpers](#app_helpers)
	- [*inputs](#app_inputs)
	- [jobs](#app_jobs)
	- [mailers](#app_mailers)
	- [models](#app_models)
	- [*performers](#app_performers)
	- [*policies](#app_policies)
	- [*presenters](#app_presenters)
	- [*services](#app_services)
	- [*use_cases](#app_use_cases)
	- [*values](#app_values)
	- [*workers](#app_workers)
	- [views](#app_views)
- [bin](#bin)
- [config](#config)
	- [environments](#config_environments)
	- [initializers](#config_initializers)
	- [locales](#config_locales)
- [db](#db)
	- [migrate](#db_migrate)
- [lib](#lib)
	- [assets](#lib_assets)
	- [tasks](#lib_tasks)
- [log](#log)
- [public](#public)
- [test](#test)
	- [controllers](#test_controllers)
	- [fixtures](#test_fixtures)
	- [helpers](#test_helpers)
	- [integration](#test_integration)
	- [mailers](#test_mailers)
	- [models](#test_models)
- [spec](#spec)
	- [factories](#spec_factories)
	- [helpers](#spec_helpers)
	- [mailers](#spec_mailers)
	- [models](#spec_models)
	- [requests](#spec_requests)
	- [routing](#spec_routing)
	- [support](#spec_support)
	- [views](#spec_views)
- [tmp](#tmp)
- [vendor](#vendor)

---

### <a name="app"></a> app

It organizes your application components. It's got subdirectories that hold the views, controllers, models, and more that handle business logic.

### <a name="app_assets"></a> app/assets

Holds the assets for your application including images, stylesheets, and javascript.

### <a name="app_cells"></a> *app/cells

App cells are simple ruby classes that can render templates.

- [github](https://github.com/trailblazer/cells) Trailblazer framework
- [video](https://www.youtube.com/watch?v=qSxN4mlyQO8&t=1781s) RailsConf talk about trailblazer.

### <a name="app_channels"></a> app/channels

Contains channels used to setup connections with [ActionCable](http://guides.rubyonrails.org/action_cable_overview.html#channels).

### <a name="app_controllers"></a> app/controllers

Contains app [controllers](http://guides.rubyonrails.org/action_controller_overview.html).

### <a name="app_decorators"></a> *app/decorators

App decorators is a design pattern to remove view methods from models.

- [github](https://github.com/drapergem/draper) draper gem
- [article](https://medium.com/@dljerome/design-patterns-in-ruby-decorator-b7f2da4153b0) explanation of decorator pattern.
- [video](http://railscasts.com/episodes/286-draper) Railscast - using draper gem.
- [video](https://www.youtube.com/watch?v=bHpVdOzrvkE) RailsConf - decorators.

The [Draper Gem](https://github.com/drapergem/draper) is a popular choice to use to help with creating and using decorators.

### <a name="app_forms"></a> *app/forms

Form Object is a design pattern that encapsulates logic related to validating and persisting data. Using these can improve the way you implement complex forms.

- [article](https://www.sitepoint.com/7-design-patterns-to-refactor-mvc-components-in-rails/) about using form objects in rails.
- [video](http://railscasts.com/episodes/416-form-objects) Railscast - implementing form objects.

### <a name="app_helpers"></a> app/helpers

Contains app [helpers](http://guides.rubyonrails.org/action_view_overview.html#overview-of-helpers-provided-by-action-view).

### <a name="app_inputs"></a> *app/inputs

Simple form allows you to create custom input components and you can place them here.

- [github](https://github.com/plataformatec/simple_form) simple form gem.
- [github](https://github.com/plataformatec/simple_form/wiki/Adding-custom-input-components) create custom input component.

### <a name="app_jobs"></a> app/jobs

Contains app [jobs](http://guides.rubyonrails.org/v4.2/active_job_basics.html).

### <a name="app_mailers"></a> app/mailers

Contains app [mailers](http://guides.rubyonrails.org/action_mailer_basics.html).

### <a name="app_models"></a> app/models

Contains app [models](http://guides.rubyonrails.org/active_record_basics.html).

### <a name="app_performers"></a> *app/performers

Performers is another design pattern to abstract view methods from the model using modules.

- [github](https://github.com/jwipeout/performer-pattern) details on the _Performer Pattern_.

### <a name="app_policies"></a> *app/policies

Policies are plain old ruby objects that handle presentation logic.

- [github](https://github.com/elabs/pundit) Pundit gem.
- [article](http://www.eq8.eu/blogs/41-policy-objects-in-ruby-on-rails) implementing policy objects.

### <a name="app_presenters"></a> *app/presenters

Presenters is another design pattern to abstract view methods from the model using PORO.

- [article](http://nithinbekal.com/posts/rails-presenters/) about using presenters in rails.
- [article](https://gist.github.com/somebox/5a7ebf56e3236372eec4) comparing presenters to decorators.
- [video](http://railscasts.com/episodes/287-presenters-from-scratch) Railscast - implementing a presenter.

### <a name="app_services"></a> *app/services

Contains app services. A service object implements the user’s interactions with the application. It contains business logic that describe the connections with your domain objects.

- [article](https://www.netguru.co/blog/service-objects-in-rails-will-help) about using services in rails.
- [video](http://railscasts.com/episodes/398-service-objects) Railscast - implementing a service.
- [video](https://vimeo.com/106759024) domain driven Rails

### <a name="app_uploaders"></a> *app/uploaders

A uploader is a class that is used by CarrierWave gem to model an uploaded file.

- [github](https://github.com/carrierwaveuploader/carrierwave) CarrierWave gem.
- [video](https://www.youtube.com/watch?v=YpF_4uciMvg) Railscast - file uploading with CarrierWave.

### <a name="app_use_cases"></a> *app/use_cases

Use Cases is pretty much the same thing as services. They are designed to break up non-trivial business logic.

- [article](https://webuild.envato.com/blog/a-case-for-use-cases/) details on _use cases_.
- [video](https://www.youtube.com/watch?v=atFN0rReJfA) on her article above.

### <a name="app_values"></a> *app/values

Value objects are an abstraction where equality is based on internal fields instead of identity.

- [github](https://github.com/cultuurnet/valueobjects) ValueObjects gem
- [article](https://www.sitepoint.com/value-objects-explained-with-ruby/) discussion and examples.
- [video](https://www.youtube.com/watch?v=iTjurFO1l5Q) lecture on value objects.

### <a name="app_views"></a> app/views

Contains app [views](http://guides.rubyonrails.org/layouts_and_rendering.html).

### <a name="app_workers"></a> *app/workers

Workers are objects that allow you to run processes in the background. Remeber, it is recommended to use active job instead of your own workers so you can later switch out job runners without having to worry about api differences.

- [github](https://github.com/mperham/sidekiq) Sidekiq gem
- [github](https://github.com/resque/resque) Resque gem
- [article](https://ryanboland.com/blog/writing-your-first-background-worker/) writing workers.
- [video](https://www.youtube.com/watch?v=CStZg8ql9Vs) Sidekiq using active job.

---

### <a name="bin"></a> bin

Contains the rails script that starts your app and can contain other scripts you use to setup, update, deploy or run your application.

---

### <a name="config"></a> config

Configure your application's routes, database, and more. This is covered in more detail in [Configuring Rails Applications](http://guides.rubyonrails.org/configuring.html).

---

### <a name="db"></a> db

Contains your current database schema, as well as the database migrations.

---

### <a name="lib"></a> lib

Extended modules for your application.

---

### <a name="log"></a> log

Application log files.

---

### <a name="public"></a> public

The only folder seen by the world as-is. Contains static files and compiled assets.

---

### <a name="test"></a> test

Unit tests, fixtures, and other test apparatus. These are covered in [Testing Rails Applications](http://guides.rubyonrails.org/testing.html).

---

### <a name="spec"></a> spec

Alternative to test directory using BDD. [Rspec](http://guides.rubyonrails.org/testing.html) allows you to write an alternative syntax to Test Unit that reads more like a specification than a test.

---

### <a name="tmp"></a> tmp

Temporary files (like cache and pid files).

---

### <a name="vendor"></a> vendor

A place for all third-party code. In a typical Rails application this includes vendored gems.

rails-directory-structure-guide

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README