Senhordim

/* Brazilian initialisation for the jQuery UI date picker plugin. */
/* Written by Leonildo Costa Silva (leocsilva@gmail.com). */
jQuery(function($){
        $.datepicker.regional['pt-BR'] = {
                closeText: 'Fechar',
                prevText: '<Anterior',
                nextText: 'Próximo>',
                currentText: 'Hoje',
                monthNames: ['Janeiro','Fevereiro','Março','Abril','Maio','Junho',
                'Julho','Agosto','Setembro','Outubro','Novembro','Dezembro'],

seyhunak

unless Rails.env.production?
  connection = ActiveRecord::Base.connection
  connection.tables.each do |table|
    connection.execute("TRUNCATE #{table}") unless table == "schema_migrations"
  end

  sql = File.read('db/import.sql')
  statements = sql.split(/;$/)
  statements.pop

jbonney

require 'mina/bundler'
require 'mina/rails'
require 'mina/git'
require 'mina/rvm'

# Usually mina focuses on deploying to one host and the deploy options are therefore simple.
# In our case, there is a number of possible servers to deploy to, it is therefore necessary to
# specify the host that we are targeting.
server = ENV['server']
# Since the same host can have multiple applications running in parallel, it is necessary to

victorlcampos

== InfoDic FREE
https://play.google.com/store/apps/details?id=br.walisson.inglesparainformaticafree#?t=W251bGwsMSwxLDIxMiwiYnIud2FsaXNzb24uaW5nbGVzcGFyYWluZm9ybWF0aWNhZnJlZSJd

samuelpismel

#encoding: utf-8

pt-BR:
  views:
    pagination:
      first: "« Primeira"
      last: "Última »"
      previous: "‹ Anterior"
      next: "Próxima ›"
      truncate: "…"

brenes

# We have to remove validations on email, as it's no longer needed.
# Based on a solution found at http://stackoverflow.com/questions/7545938/how-to-remove-validation-using-instance-eval-clause-in-rails
Model.class_eval do
  _validators.reject!{ |key, _| key == :field }


  _validate_callbacks.each do |callback|
    callback.raw_filter.attributes.delete :field
  end

daltonjorge

Active Record

É um design pattern que o Rails implementa a partir da gem ActiveRecord.

Serve para conectar a camada Model da aplicação com tabelas do database, para assim criar um modelo de domínio persistível, onde a lógica (Model) e dados (BD) são apresentados em uma única solução.

Já persiste no BD:

obj.create

them0nk

#Model 

@user.should have(1).error_on(:username) # Checks whether there is an error in username 
@user.errors[:username].should include("can't be blank")  # check for the error message 

#Rendering
response.should render_template(:index)

#Redirecting 
response.should redirect_to(movies_path)

samqiu

#!/usr/bin/ruby
require 'rss'

# Usage
# $ ./railscasts.rb http://railscasts.com/subscriptions/YOURRAILSCASTRSS/\/
#     episodes.rss
# OR
# $ ./railscasts.rb

p 'Downloading rss index'

jcasimir

Friendly URLs

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.