acts_as_citable 1.0.1
Sign up to get free protection for your applications and to get access to all the features.
- data/MIT-LICENSE +20 -0
- data/README.rdoc +3 -0
- data/Rakefile +38 -0
- data/lib/acts_as_citable/base.rb +87 -0
- data/lib/acts_as_citable/mime_types.rb +4 -0
- data/lib/acts_as_citable/renderers.rb +32 -0
- data/lib/acts_as_citable/version.rb +3 -0
- data/lib/acts_as_citable.rb +1 -0
- data/lib/tasks/acts_as_citable_tasks.rake +4 -0
- data/test/acts_as_citable_test.rb +81 -0
- data/test/dummy/README.rdoc +261 -0
- data/test/dummy/Rakefile +7 -0
- data/test/dummy/app/assets/javascripts/application.js +15 -0
- data/test/dummy/app/assets/javascripts/test.js +2 -0
- data/test/dummy/app/assets/stylesheets/application.css +13 -0
- data/test/dummy/app/assets/stylesheets/test.css +4 -0
- data/test/dummy/app/controllers/application_controller.rb +3 -0
- data/test/dummy/app/controllers/test_controller.rb +9 -0
- data/test/dummy/app/helpers/application_helper.rb +2 -0
- data/test/dummy/app/helpers/test_helper.rb +2 -0
- data/test/dummy/app/models/inherited_record.rb +3 -0
- data/test/dummy/app/models/record.rb +4 -0
- data/test/dummy/app/models/record_changed_field.rb +6 -0
- data/test/dummy/app/views/layouts/application.html.erb +14 -0
- data/test/dummy/config/application.rb +59 -0
- data/test/dummy/config/boot.rb +10 -0
- data/test/dummy/config/database.yml +20 -0
- data/test/dummy/config/environment.rb +5 -0
- data/test/dummy/config/environments/development.rb +37 -0
- data/test/dummy/config/environments/production.rb +67 -0
- data/test/dummy/config/environments/test.rb +37 -0
- data/test/dummy/config/initializers/backtrace_silencers.rb +7 -0
- data/test/dummy/config/initializers/inflections.rb +15 -0
- data/test/dummy/config/initializers/mime_types.rb +5 -0
- data/test/dummy/config/initializers/secret_token.rb +7 -0
- data/test/dummy/config/initializers/session_store.rb +8 -0
- data/test/dummy/config/initializers/wrap_parameters.rb +14 -0
- data/test/dummy/config/locales/en.yml +5 -0
- data/test/dummy/config/routes.rb +59 -0
- data/test/dummy/config.ru +4 -0
- data/test/dummy/db/development.sqlite3 +0 -0
- data/test/dummy/db/migrate/20130221210429_create_records.rb +10 -0
- data/test/dummy/db/migrate/20130221214225_create_record_changed_fields.rb +10 -0
- data/test/dummy/db/schema.rb +30 -0
- data/test/dummy/db/test.sqlite3 +0 -0
- data/test/dummy/log/development.log +3150 -0
- data/test/dummy/log/test.log +6674 -0
- data/test/dummy/public/404.html +26 -0
- data/test/dummy/public/422.html +26 -0
- data/test/dummy/public/500.html +25 -0
- data/test/dummy/public/favicon.ico +0 -0
- data/test/dummy/script/rails +6 -0
- data/test/dummy/test/fixtures/record_changed_fields.yml +9 -0
- data/test/dummy/test/fixtures/records.yml +9 -0
- data/test/dummy/test/functional/test_controller_test.rb +20 -0
- data/test/dummy/test/unit/helpers/test_helper_test.rb +4 -0
- data/test/dummy/test/unit/record_changed_field_test.rb +7 -0
- data/test/dummy/test/unit/record_test.rb +11 -0
- data/test/test_helper.rb +26 -0
- metadata +340 -0
data/MIT-LICENSE
ADDED
@@ -0,0 +1,20 @@
|
|
1
|
+
Copyright 2013 YOURNAME
|
2
|
+
|
3
|
+
Permission is hereby granted, free of charge, to any person obtaining
|
4
|
+
a copy of this software and associated documentation files (the
|
5
|
+
"Software"), to deal in the Software without restriction, including
|
6
|
+
without limitation the rights to use, copy, modify, merge, publish,
|
7
|
+
distribute, sublicense, and/or sell copies of the Software, and to
|
8
|
+
permit persons to whom the Software is furnished to do so, subject to
|
9
|
+
the following conditions:
|
10
|
+
|
11
|
+
The above copyright notice and this permission notice shall be
|
12
|
+
included in all copies or substantial portions of the Software.
|
13
|
+
|
14
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
|
15
|
+
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
|
16
|
+
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
|
17
|
+
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
|
18
|
+
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
|
19
|
+
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
|
20
|
+
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
|
data/README.rdoc
ADDED
data/Rakefile
ADDED
@@ -0,0 +1,38 @@
|
|
1
|
+
#!/usr/bin/env rake
|
2
|
+
begin
|
3
|
+
require 'bundler/setup'
|
4
|
+
rescue LoadError
|
5
|
+
puts 'You must `gem install bundler` and `bundle install` to run rake tasks'
|
6
|
+
end
|
7
|
+
begin
|
8
|
+
require 'rdoc/task'
|
9
|
+
rescue LoadError
|
10
|
+
require 'rdoc/rdoc'
|
11
|
+
require 'rake/rdoctask'
|
12
|
+
RDoc::Task = Rake::RDocTask
|
13
|
+
end
|
14
|
+
|
15
|
+
RDoc::Task.new(:rdoc) do |rdoc|
|
16
|
+
rdoc.rdoc_dir = 'rdoc'
|
17
|
+
rdoc.title = 'ActsAsCitable'
|
18
|
+
rdoc.options << '--line-numbers'
|
19
|
+
rdoc.rdoc_files.include('README.rdoc')
|
20
|
+
rdoc.rdoc_files.include('lib/**/*.rb')
|
21
|
+
end
|
22
|
+
|
23
|
+
|
24
|
+
|
25
|
+
|
26
|
+
Bundler::GemHelper.install_tasks
|
27
|
+
|
28
|
+
require 'rake/testtask'
|
29
|
+
|
30
|
+
Rake::TestTask.new(:test) do |t|
|
31
|
+
t.libs << 'lib'
|
32
|
+
t.libs << 'test'
|
33
|
+
t.pattern = 'test/**/*_test.rb'
|
34
|
+
t.verbose = false
|
35
|
+
end
|
36
|
+
|
37
|
+
|
38
|
+
task :default => :test
|
@@ -0,0 +1,87 @@
|
|
1
|
+
require 'acts_as_citable/mime_types'
|
2
|
+
require 'acts_as_citable/renderers'
|
3
|
+
require 'citero-jruby'
|
4
|
+
module ActsAsCitable
|
5
|
+
attr_accessor :format_field, :data_field
|
6
|
+
# Set attribute accessors
|
7
|
+
|
8
|
+
# Hooks into an object to define its 'format' and 'data' fields. These are used to
|
9
|
+
# translate into other forms of metadata.
|
10
|
+
def acts_as_citable &block
|
11
|
+
# Allow for configurations
|
12
|
+
self.format_field = 'format'
|
13
|
+
self.data_field = 'data'
|
14
|
+
if block
|
15
|
+
yield self
|
16
|
+
end
|
17
|
+
|
18
|
+
# Use procs to define methods that give the data_field and format_field for inherited models.
|
19
|
+
format_string = "#{self.format_field}"
|
20
|
+
data_string = "#{self.data_field}"
|
21
|
+
|
22
|
+
define_method(:format_field, Proc.new {format_string} )
|
23
|
+
define_method(:data_field, Proc.new {data_string} )
|
24
|
+
# Include the instance methods found below
|
25
|
+
include InstanceMethods
|
26
|
+
end
|
27
|
+
|
28
|
+
module InstanceMethods
|
29
|
+
# The method_missing override checks to see if the called method
|
30
|
+
# can be evaluated to a method name and parameter, then stores it
|
31
|
+
# and calls it if it can.
|
32
|
+
# For example, to_csf or from_pnx. pnx_to will not work.
|
33
|
+
def method_missing(meth, *args, &block)
|
34
|
+
# Check to see if it can be evaluated
|
35
|
+
if(matches? meth)
|
36
|
+
#Defines the method and caches it to the class
|
37
|
+
self.class.send(:define_method, meth) do
|
38
|
+
# Uses data_field and format_field to translate the metadata.
|
39
|
+
# debugger
|
40
|
+
Citero.map(_data).send("from_#{_format}").send(meth)
|
41
|
+
end
|
42
|
+
# calls the method
|
43
|
+
send meth, *args, &block
|
44
|
+
else
|
45
|
+
super
|
46
|
+
end
|
47
|
+
end
|
48
|
+
|
49
|
+
# Returns true if the method can be evaluated to a method name
|
50
|
+
# and parameter.
|
51
|
+
def respond_to? meth, include_private=false
|
52
|
+
if(matches? meth)
|
53
|
+
return true
|
54
|
+
else
|
55
|
+
super
|
56
|
+
end
|
57
|
+
end
|
58
|
+
|
59
|
+
# Private method. Checks to see if the method name is in the list of methods
|
60
|
+
# that can accept the formats, and checks to see if the formats are in a list
|
61
|
+
# of formats as defined by the Java enum Format.
|
62
|
+
def matches? meth
|
63
|
+
Citero.map("").respond_to?(meth) && ( directionize(meth).eql?("to") || directionize(meth).eql?(meth.to_s) )
|
64
|
+
end
|
65
|
+
private :matches?
|
66
|
+
|
67
|
+
# Splits the method to get its direction, or method ie to and from.
|
68
|
+
def directionize meth, delimiter="_"
|
69
|
+
meth.to_s.split(delimiter, 2).first
|
70
|
+
end
|
71
|
+
private :directionize
|
72
|
+
|
73
|
+
def _data
|
74
|
+
self.send(data_field.to_sym)
|
75
|
+
end
|
76
|
+
private :_data
|
77
|
+
|
78
|
+
def _format
|
79
|
+
self.send(format_field.to_sym)
|
80
|
+
end
|
81
|
+
private :_format
|
82
|
+
|
83
|
+
end
|
84
|
+
|
85
|
+
end
|
86
|
+
|
87
|
+
ActiveRecord::Base.extend ActsAsCitable
|
@@ -0,0 +1,32 @@
|
|
1
|
+
class Array
|
2
|
+
# Allow array of objects to be translated to ris
|
3
|
+
def to_ris
|
4
|
+
self.collect { |r| r.to_ris if r.respond_to? :to_ris}.join("\n\n")
|
5
|
+
end
|
6
|
+
|
7
|
+
# Allow array of objects to be translated to ris
|
8
|
+
def to_bibtex
|
9
|
+
self.collect { |r| r.to_bibtex if r.respond_to? :to_bibtex }.join("\n\n")
|
10
|
+
end
|
11
|
+
end
|
12
|
+
|
13
|
+
# Adds a renderer for RIS.
|
14
|
+
ActionController::Renderers.add :ris do |ris, options|
|
15
|
+
ris = ris.first if ris.is_a? Array and ris.count == 1
|
16
|
+
filename = (ris.respond_to?(:to_param) and ris.class.respond_to?(:acts_as_citable)) ? ris.to_param : "export"
|
17
|
+
ris = ris.respond_to?(:to_ris) ? ris.to_ris() : ris
|
18
|
+
ris = "#{options[:callback]}(#{ris})" unless options[:callback].blank?
|
19
|
+
self.content_type ||= Mime::RIS
|
20
|
+
self.send_data ris, filename: "#{filename}.ris"
|
21
|
+
end
|
22
|
+
|
23
|
+
# Adds a renderer for BibTeX.
|
24
|
+
ActionController::Renderers.add :bibtex do |bibtex, options|
|
25
|
+
bibtex = bibtex.first if bibtex.is_a? Array and bibtex.count == 1
|
26
|
+
filename = (bibtex.respond_to?(:to_param) and bibtex.class.respond_to?(:acts_as_citable)) ? bibtex.to_param : "export"
|
27
|
+
bibtex = bibtex.respond_to?(:to_bibtex) ? bibtex.to_bibtex() : bibtex
|
28
|
+
bibtex = "#{options[:callback]}(#{bibtex})" unless options[:callback].blank?
|
29
|
+
self.content_type ||= Mime::Bibtex
|
30
|
+
self.send_data bibtex, filename: "#{filename}.bib"
|
31
|
+
end
|
32
|
+
|
@@ -0,0 +1 @@
|
|
1
|
+
require 'acts_as_citable/base'
|
@@ -0,0 +1,81 @@
|
|
1
|
+
require 'test_helper'
|
2
|
+
require 'ruby-debug'
|
3
|
+
|
4
|
+
class ActsAsCitableTest < ActiveSupport::TestCase
|
5
|
+
test "truth" do
|
6
|
+
assert_kind_of Module, ActsAsCitable
|
7
|
+
end
|
8
|
+
end
|
9
|
+
|
10
|
+
class RecordTest < ActiveSupport::TestCase
|
11
|
+
test "should check if i can use the record" do
|
12
|
+
assert rec = Record.new( :data => "data", :format => "from_format")
|
13
|
+
assert rec.destroy
|
14
|
+
end
|
15
|
+
|
16
|
+
test "should check to see if format fields are set" do
|
17
|
+
assert 'format', Record.format_field
|
18
|
+
assert 'from_format', RecordChangedField.format_field
|
19
|
+
end
|
20
|
+
|
21
|
+
test "should check to see if records can be converted" do
|
22
|
+
rec = Record.new(:data => "itemType: book", :format => "csf")
|
23
|
+
assert rec.respond_to?(:to_ris)
|
24
|
+
assert rec.respond_to?(:to_bibtex)
|
25
|
+
assert rec.respond_to?(:to_openurl)
|
26
|
+
assert rec.respond_to?(:to_csf)
|
27
|
+
assert rec.respond_to?(:to_easybib)
|
28
|
+
assert rec.respond_to?(:csf)
|
29
|
+
assert rec.destroy
|
30
|
+
end
|
31
|
+
|
32
|
+
test "should work with models inherited acts_as_citable models" do
|
33
|
+
rec = InheritedRecord.new(:data => "itemType: book", :format => "csf")
|
34
|
+
assert rec.to_ris.eql? "TY - BOOK\nER -\n\n"
|
35
|
+
assert rec.to_bibtex.eql? "@book{????\n}"
|
36
|
+
assert rec.to_openurl.eql? "rft.ulr_ver=Z39.88-2004&rft.ctx_ver=Z39.88-2004&rft.rfr_id=info:sid/libraries.nyu.edu:citero&rft_val_fmlt=info:ofi/fmt:kev:mtx:book&rft.genre=book"
|
37
|
+
assert rec.to_easybib.eql? "{\"source\":\"book\",\"book\":{\"title\":null},\"pubtype\":{\"main\":\"pubnonperiodical\"},\"pubnonperiodical\":{},\"contributors\":[{}]}"
|
38
|
+
assert rec.destroy
|
39
|
+
end
|
40
|
+
|
41
|
+
test "should check to see if you cannot convert from" do
|
42
|
+
rec = Record.new(:data => "itemType: book", :format => "csf")
|
43
|
+
assert !rec.respond_to?(:from_ris)
|
44
|
+
assert !rec.respond_to?(:from_bibtex)
|
45
|
+
assert !rec.respond_to?(:from_openurl)
|
46
|
+
assert !rec.respond_to?(:from_csf)
|
47
|
+
assert !rec.respond_to?(:from_pnx)
|
48
|
+
end
|
49
|
+
|
50
|
+
test "should raise no method error" do
|
51
|
+
rec = Record.new(:data => "itemType: book", :format => "csf")
|
52
|
+
assert_raise NoMethodError do
|
53
|
+
rec.from_ris
|
54
|
+
end
|
55
|
+
assert rec.destroy
|
56
|
+
end
|
57
|
+
|
58
|
+
test "should be available to convert to" do
|
59
|
+
rec = Record.new(:data => "itemType: book", :format => "csf")
|
60
|
+
assert rec.to_ris.eql? "TY - BOOK\nER -\n\n"
|
61
|
+
assert rec.to_bibtex.eql? "@book{????\n}"
|
62
|
+
assert rec.to_openurl.eql? "rft.ulr_ver=Z39.88-2004&rft.ctx_ver=Z39.88-2004&rft.rfr_id=info:sid/libraries.nyu.edu:citero&rft_val_fmlt=info:ofi/fmt:kev:mtx:book&rft.genre=book"
|
63
|
+
assert rec.to_easybib.eql? "{\"source\":\"book\",\"book\":{\"title\":null},\"pubtype\":{\"main\":\"pubnonperiodical\"},\"pubnonperiodical\":{},\"contributors\":[{}]}"
|
64
|
+
assert rec.destroy
|
65
|
+
end
|
66
|
+
|
67
|
+
test "new nokogiri xml document" do
|
68
|
+
assert_nothing_raised("New Nokogiri::XML::Document raises an error.") {
|
69
|
+
Nokogiri::XML::Document.new
|
70
|
+
}
|
71
|
+
end
|
72
|
+
|
73
|
+
test "arrays should be able to convert to ris and bibtex" do
|
74
|
+
arr = Array.new
|
75
|
+
arr << Record.new(:data => "itemType: book", :format => "csf") << Record.create(:data => "itemType: book", :format => "csf")
|
76
|
+
assert arr.to_bibtex
|
77
|
+
assert arr.to_ris
|
78
|
+
arr.each {|rec| assert rec.destroy}
|
79
|
+
end
|
80
|
+
|
81
|
+
end
|
@@ -0,0 +1,261 @@
|
|
1
|
+
== Welcome to Rails
|
2
|
+
|
3
|
+
Rails is a web-application framework that includes everything needed to create
|
4
|
+
database-backed web applications according to the Model-View-Control pattern.
|
5
|
+
|
6
|
+
This pattern splits the view (also called the presentation) into "dumb"
|
7
|
+
templates that are primarily responsible for inserting pre-built data in between
|
8
|
+
HTML tags. The model contains the "smart" domain objects (such as Account,
|
9
|
+
Product, Person, Post) that holds all the business logic and knows how to
|
10
|
+
persist themselves to a database. The controller handles the incoming requests
|
11
|
+
(such as Save New Account, Update Product, Show Post) by manipulating the model
|
12
|
+
and directing data to the view.
|
13
|
+
|
14
|
+
In Rails, the model is handled by what's called an object-relational mapping
|
15
|
+
layer entitled Active Record. This layer allows you to present the data from
|
16
|
+
database rows as objects and embellish these data objects with business logic
|
17
|
+
methods. You can read more about Active Record in
|
18
|
+
link:files/vendor/rails/activerecord/README.html.
|
19
|
+
|
20
|
+
The controller and view are handled by the Action Pack, which handles both
|
21
|
+
layers by its two parts: Action View and Action Controller. These two layers
|
22
|
+
are bundled in a single package due to their heavy interdependence. This is
|
23
|
+
unlike the relationship between the Active Record and Action Pack that is much
|
24
|
+
more separate. Each of these packages can be used independently outside of
|
25
|
+
Rails. You can read more about Action Pack in
|
26
|
+
link:files/vendor/rails/actionpack/README.html.
|
27
|
+
|
28
|
+
|
29
|
+
== Getting Started
|
30
|
+
|
31
|
+
1. At the command prompt, create a new Rails application:
|
32
|
+
<tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
|
33
|
+
|
34
|
+
2. Change directory to <tt>myapp</tt> and start the web server:
|
35
|
+
<tt>cd myapp; rails server</tt> (run with --help for options)
|
36
|
+
|
37
|
+
3. Go to http://localhost:3000/ and you'll see:
|
38
|
+
"Welcome aboard: You're riding Ruby on Rails!"
|
39
|
+
|
40
|
+
4. Follow the guidelines to start developing your application. You can find
|
41
|
+
the following resources handy:
|
42
|
+
|
43
|
+
* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
|
44
|
+
* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
|
45
|
+
|
46
|
+
|
47
|
+
== Debugging Rails
|
48
|
+
|
49
|
+
Sometimes your application goes wrong. Fortunately there are a lot of tools that
|
50
|
+
will help you debug it and get it back on the rails.
|
51
|
+
|
52
|
+
First area to check is the application log files. Have "tail -f" commands
|
53
|
+
running on the server.log and development.log. Rails will automatically display
|
54
|
+
debugging and runtime information to these files. Debugging info will also be
|
55
|
+
shown in the browser on requests from 127.0.0.1.
|
56
|
+
|
57
|
+
You can also log your own messages directly into the log file from your code
|
58
|
+
using the Ruby logger class from inside your controllers. Example:
|
59
|
+
|
60
|
+
class WeblogController < ActionController::Base
|
61
|
+
def destroy
|
62
|
+
@weblog = Weblog.find(params[:id])
|
63
|
+
@weblog.destroy
|
64
|
+
logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
|
65
|
+
end
|
66
|
+
end
|
67
|
+
|
68
|
+
The result will be a message in your log file along the lines of:
|
69
|
+
|
70
|
+
Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
|
71
|
+
|
72
|
+
More information on how to use the logger is at http://www.ruby-doc.org/core/
|
73
|
+
|
74
|
+
Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
|
75
|
+
several books available online as well:
|
76
|
+
|
77
|
+
* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
|
78
|
+
* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
|
79
|
+
|
80
|
+
These two books will bring you up to speed on the Ruby language and also on
|
81
|
+
programming in general.
|
82
|
+
|
83
|
+
|
84
|
+
== Debugger
|
85
|
+
|
86
|
+
Debugger support is available through the debugger command when you start your
|
87
|
+
Mongrel or WEBrick server with --debugger. This means that you can break out of
|
88
|
+
execution at any point in the code, investigate and change the model, and then,
|
89
|
+
resume execution! You need to install ruby-debug to run the server in debugging
|
90
|
+
mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
|
91
|
+
|
92
|
+
class WeblogController < ActionController::Base
|
93
|
+
def index
|
94
|
+
@posts = Post.all
|
95
|
+
debugger
|
96
|
+
end
|
97
|
+
end
|
98
|
+
|
99
|
+
So the controller will accept the action, run the first line, then present you
|
100
|
+
with a IRB prompt in the server window. Here you can do things like:
|
101
|
+
|
102
|
+
>> @posts.inspect
|
103
|
+
=> "[#<Post:0x14a6be8
|
104
|
+
@attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
|
105
|
+
#<Post:0x14a6620
|
106
|
+
@attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
|
107
|
+
>> @posts.first.title = "hello from a debugger"
|
108
|
+
=> "hello from a debugger"
|
109
|
+
|
110
|
+
...and even better, you can examine how your runtime objects actually work:
|
111
|
+
|
112
|
+
>> f = @posts.first
|
113
|
+
=> #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
|
114
|
+
>> f.
|
115
|
+
Display all 152 possibilities? (y or n)
|
116
|
+
|
117
|
+
Finally, when you're ready to resume execution, you can enter "cont".
|
118
|
+
|
119
|
+
|
120
|
+
== Console
|
121
|
+
|
122
|
+
The console is a Ruby shell, which allows you to interact with your
|
123
|
+
application's domain model. Here you'll have all parts of the application
|
124
|
+
configured, just like it is when the application is running. You can inspect
|
125
|
+
domain models, change values, and save to the database. Starting the script
|
126
|
+
without arguments will launch it in the development environment.
|
127
|
+
|
128
|
+
To start the console, run <tt>rails console</tt> from the application
|
129
|
+
directory.
|
130
|
+
|
131
|
+
Options:
|
132
|
+
|
133
|
+
* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
|
134
|
+
made to the database.
|
135
|
+
* Passing an environment name as an argument will load the corresponding
|
136
|
+
environment. Example: <tt>rails console production</tt>.
|
137
|
+
|
138
|
+
To reload your controllers and models after launching the console run
|
139
|
+
<tt>reload!</tt>
|
140
|
+
|
141
|
+
More information about irb can be found at:
|
142
|
+
link:http://www.rubycentral.org/pickaxe/irb.html
|
143
|
+
|
144
|
+
|
145
|
+
== dbconsole
|
146
|
+
|
147
|
+
You can go to the command line of your database directly through <tt>rails
|
148
|
+
dbconsole</tt>. You would be connected to the database with the credentials
|
149
|
+
defined in database.yml. Starting the script without arguments will connect you
|
150
|
+
to the development database. Passing an argument will connect you to a different
|
151
|
+
database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
|
152
|
+
PostgreSQL and SQLite 3.
|
153
|
+
|
154
|
+
== Description of Contents
|
155
|
+
|
156
|
+
The default directory structure of a generated Ruby on Rails application:
|
157
|
+
|
158
|
+
|-- app
|
159
|
+
| |-- assets
|
160
|
+
| |-- images
|
161
|
+
| |-- javascripts
|
162
|
+
| `-- stylesheets
|
163
|
+
| |-- controllers
|
164
|
+
| |-- helpers
|
165
|
+
| |-- mailers
|
166
|
+
| |-- models
|
167
|
+
| `-- views
|
168
|
+
| `-- layouts
|
169
|
+
|-- config
|
170
|
+
| |-- environments
|
171
|
+
| |-- initializers
|
172
|
+
| `-- locales
|
173
|
+
|-- db
|
174
|
+
|-- doc
|
175
|
+
|-- lib
|
176
|
+
| `-- tasks
|
177
|
+
|-- log
|
178
|
+
|-- public
|
179
|
+
|-- script
|
180
|
+
|-- test
|
181
|
+
| |-- fixtures
|
182
|
+
| |-- functional
|
183
|
+
| |-- integration
|
184
|
+
| |-- performance
|
185
|
+
| `-- unit
|
186
|
+
|-- tmp
|
187
|
+
| |-- cache
|
188
|
+
| |-- pids
|
189
|
+
| |-- sessions
|
190
|
+
| `-- sockets
|
191
|
+
`-- vendor
|
192
|
+
|-- assets
|
193
|
+
`-- stylesheets
|
194
|
+
`-- plugins
|
195
|
+
|
196
|
+
app
|
197
|
+
Holds all the code that's specific to this particular application.
|
198
|
+
|
199
|
+
app/assets
|
200
|
+
Contains subdirectories for images, stylesheets, and JavaScript files.
|
201
|
+
|
202
|
+
app/controllers
|
203
|
+
Holds controllers that should be named like weblogs_controller.rb for
|
204
|
+
automated URL mapping. All controllers should descend from
|
205
|
+
ApplicationController which itself descends from ActionController::Base.
|
206
|
+
|
207
|
+
app/models
|
208
|
+
Holds models that should be named like post.rb. Models descend from
|
209
|
+
ActiveRecord::Base by default.
|
210
|
+
|
211
|
+
app/views
|
212
|
+
Holds the template files for the view that should be named like
|
213
|
+
weblogs/index.html.erb for the WeblogsController#index action. All views use
|
214
|
+
eRuby syntax by default.
|
215
|
+
|
216
|
+
app/views/layouts
|
217
|
+
Holds the template files for layouts to be used with views. This models the
|
218
|
+
common header/footer method of wrapping views. In your views, define a layout
|
219
|
+
using the <tt>layout :default</tt> and create a file named default.html.erb.
|
220
|
+
Inside default.html.erb, call <% yield %> to render the view using this
|
221
|
+
layout.
|
222
|
+
|
223
|
+
app/helpers
|
224
|
+
Holds view helpers that should be named like weblogs_helper.rb. These are
|
225
|
+
generated for you automatically when using generators for controllers.
|
226
|
+
Helpers can be used to wrap functionality for your views into methods.
|
227
|
+
|
228
|
+
config
|
229
|
+
Configuration files for the Rails environment, the routing map, the database,
|
230
|
+
and other dependencies.
|
231
|
+
|
232
|
+
db
|
233
|
+
Contains the database schema in schema.rb. db/migrate contains all the
|
234
|
+
sequence of Migrations for your schema.
|
235
|
+
|
236
|
+
doc
|
237
|
+
This directory is where your application documentation will be stored when
|
238
|
+
generated using <tt>rake doc:app</tt>
|
239
|
+
|
240
|
+
lib
|
241
|
+
Application specific libraries. Basically, any kind of custom code that
|
242
|
+
doesn't belong under controllers, models, or helpers. This directory is in
|
243
|
+
the load path.
|
244
|
+
|
245
|
+
public
|
246
|
+
The directory available for the web server. Also contains the dispatchers and the
|
247
|
+
default HTML files. This should be set as the DOCUMENT_ROOT of your web
|
248
|
+
server.
|
249
|
+
|
250
|
+
script
|
251
|
+
Helper scripts for automation and generation.
|
252
|
+
|
253
|
+
test
|
254
|
+
Unit and functional tests along with fixtures. When using the rails generate
|
255
|
+
command, template test files will be generated for you and placed in this
|
256
|
+
directory.
|
257
|
+
|
258
|
+
vendor
|
259
|
+
External libraries that the application depends on. Also includes the plugins
|
260
|
+
subdirectory. If the app has frozen rails, those gems also go here, under
|
261
|
+
vendor/rails/. This directory is in the load path.
|
data/test/dummy/Rakefile
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
#!/usr/bin/env rake
|
2
|
+
# Add your own tasks in files placed in lib/tasks ending in .rake,
|
3
|
+
# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
|
4
|
+
|
5
|
+
require File.expand_path('../config/application', __FILE__)
|
6
|
+
|
7
|
+
Dummy::Application.load_tasks
|
@@ -0,0 +1,15 @@
|
|
1
|
+
// This is a manifest file that'll be compiled into application.js, which will include all the files
|
2
|
+
// listed below.
|
3
|
+
//
|
4
|
+
// Any JavaScript/Coffee file within this directory, lib/assets/javascripts, vendor/assets/javascripts,
|
5
|
+
// or vendor/assets/javascripts of plugins, if any, can be referenced here using a relative path.
|
6
|
+
//
|
7
|
+
// It's not advisable to add code directly here, but if you do, it'll appear at the bottom of the
|
8
|
+
// the compiled file.
|
9
|
+
//
|
10
|
+
// WARNING: THE FIRST BLANK LINE MARKS THE END OF WHAT'S TO BE PROCESSED, ANY BLANK LINE SHOULD
|
11
|
+
// GO AFTER THE REQUIRES BELOW.
|
12
|
+
//
|
13
|
+
//= require jquery
|
14
|
+
//= require jquery_ujs
|
15
|
+
//= require_tree .
|
@@ -0,0 +1,13 @@
|
|
1
|
+
/*
|
2
|
+
* This is a manifest file that'll be compiled into application.css, which will include all the files
|
3
|
+
* listed below.
|
4
|
+
*
|
5
|
+
* Any CSS and SCSS file within this directory, lib/assets/stylesheets, vendor/assets/stylesheets,
|
6
|
+
* or vendor/assets/stylesheets of plugins, if any, can be referenced here using a relative path.
|
7
|
+
*
|
8
|
+
* You're free to add application-wide styles to this file and they'll appear at the top of the
|
9
|
+
* compiled file, but it's generally better to create a new file per style scope.
|
10
|
+
*
|
11
|
+
*= require_self
|
12
|
+
*= require_tree .
|
13
|
+
*/
|