By default, Rails applications build URLs based on the primary key -- the id column from the database. Imagine we have a Person model and associated controller. We have a person record for Bob Martin that has id number 6. The URL for his show page would be:
/people/6
But, for aesthetic or SEO purposes, we want Bob's name in the URL. The last segment, the 6 here, is called the "slug". Let's look at a few ways to implement better slugs.
The normal controller/view flow is to display a view template corresponding to the current controller action, but sometimes we want to change that. We use render in a controller when we want to respond within the current request, and redirect_to when we want to spawn a new request.
The render method is very overloaded in Rails. Most developers encounter it within the view template, using render :partial => 'form' or render @post.comments, but here we'll focus on usage within the controller.
| # 0 is too far from ` ;) | |
| set -g base-index 1 | |
| # Automatically set window title | |
| set-window-option -g automatic-rename on | |
| set-option -g set-titles on | |
| #set -g default-terminal screen-256color | |
| set -g status-keys vi | |
| set -g history-limit 10000 |
| # Русский перевод для https://github.com/plataformatec/devise/tree/v1.4.7 | |
| # Другие переводы на http://github.com/plataformatec/devise/wiki/I18n | |
| ru: | |
| errors: | |
| messages: | |
| expired: "устарела. Пожалуйста, запросите новую" | |
| not_found: "не найдена" | |
| already_confirmed: "уже подтверждена. Пожалуйста, попробуйте войти в систему" | |
| not_locked: "не заблокирована" |
It's pretty easy to do polymorphic associations in Rails: A Picture can belong to either a BlogPost or an Article. But what if you need the relationship the other way around? A Picture, a Text and a Video can belong to an Article, and that article can find all media by calling @article.media
This example shows how to create an ArticleElement join model that handles the polymorphic relationship. To add fields that are common to all polymorphic models, add fields to the join model.
| class Api::RegistrationsController < Api::BaseController | |
| respond_to :json | |
| def create | |
| user = User.new(params[:user]) | |
| if user.save | |
| render :json=> user.as_json(:auth_token=>user.authentication_token, :email=>user.email), :status=>201 | |
| return | |
| else |
| require 'active_support/core_ext/hash/keys' | |
| class Hash | |
| def recursively_symbolize_keys! | |
| self.symbolize_keys! | |
| self.values.each do |v| | |
| if v.is_a? Hash | |
| v.recursively_symbolize_keys! | |
| elsif v.is_a? Array | |
| v.recursively_symbolize_keys! |
| Create separate SSH key for your personal account and your company. Named them with different extensions in your .ssh folder. Upload them to your github account and finally create a config file for your SSH | |
| Create a config file in ~/.ssh/ | |
| vim config: | |
| # PERSONAL ACCOUNT Github | |
| Host github.com-COOL | |
| HostName github.com | |
| User git | |
| IdentityFile ~/.ssh/id_rsa_COOL |
| class ApplicationController < ActionController::Base | |
| ... | |
| private | |
| def after_sign_in_path_for(resource) | |
| if current_administrator && current_administrator.is_admin? | |
| [:admin, :admins] | |
| else | |
| root_path |
