ffmike-suprails 0.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
data/.suprails.example ADDED
@@ -0,0 +1,115 @@
1
+ #
2
+ # This is the example configuration file for Suprails
3
+ #
4
+
5
+ # It is important to realize that this file is essentially a ruby source file.
6
+ # Every statement that is not commented out with a '#' character, will be
7
+ # executed as a ruby expression. The most important aspect of this is that all
8
+ # string-based arguments must either be a symbol (where syntax allows) or
9
+ # enclosed in quotes. Additionally, arguments must be separated by a comma,
10
+ # just like a ruby method call.
11
+ #
12
+ # Example (will NOT work):
13
+ # gems.update rspec rspec-rails haml
14
+ # Example (will work):
15
+ # gems.update :rspec, "rspec-rails", :haml
16
+ #
17
+ # Also, the commands in this file are run in order. In other words, this file
18
+ # is functional, rather than declarative. If you try to update the rails gem
19
+ # after running the rails command, the update to rails will NOT take effect.
20
+
21
+ # Declare the location for your files to copy from. Let's say you have a
22
+ # helper file you always have, and you'd like it to be installed into the
23
+ # lib/ folder. This command defines the location of your master helper file
24
+ # (or any other similar files). Ideally, this should be one of your first
25
+ # commands
26
+ # Example (also the default):
27
+ # sources "~/.suprails/sources"
28
+
29
+ # Declare the gems you'd like to update. Keep in mind that this will likely
30
+ # require you to enter your root password, as sudo will probably be called
31
+ # You should probably do this before issuing the rails command
32
+ # Example:
33
+ # gems.update :rspec, "rspec-rails", :haml, :capistrano
34
+ #
35
+ # You could instead update all gems
36
+ # Example:
37
+ # gems.update
38
+
39
+ # There are two ways to run the rails generator: rails and frozen_rails.
40
+ # Only one should be called, so if you want frozen rails, comment out the
41
+ # rails command
42
+ #
43
+ # frozen_rails
44
+ rails
45
+
46
+ # Now, define the gems you wish to mention in the config/environment.rb file
47
+ # Example:
48
+ # gems.config :haml
49
+
50
+ # You can unpack the gems that you defined with gems.config by calling
51
+ # gems.unpack
52
+ # Example:
53
+ # gems.unpack
54
+
55
+ # Plugins are also available for installation.
56
+ plugin "git://github.com/rails/exception_notification"
57
+
58
+ # And you can generate stuff, too
59
+ # Example:
60
+ # generate :rspec
61
+ # generate "model", "Model", "name:string"
62
+
63
+ # Creating new folders is easy. Here's one for Haml
64
+ # Example:
65
+ # folder "public/stylesheets/sass"
66
+
67
+ # You can also create new files with pre-existing content. Suprails looks for
68
+ # the existing file in the folder specified above in sources
69
+ # Example:
70
+ # file "site.sass", "public/stylesheets/sass/"
71
+
72
+ # You can delete files too
73
+ # Example:
74
+ # delete "public/index.html"
75
+ delete "public/index.html"
76
+
77
+ # There's a convenience method for the GPL. Because... you know... the GPL
78
+ # is good. and stuff. Note: this method accesses the GPL from the net.
79
+ # Example:
80
+ # gpl
81
+
82
+ # You can setup your database, too. Unfortunately, this is not yet implemented.
83
+ # Use 'file' to copy your database.yml file instead.
84
+ # Examples:
85
+ # db.development.adapter :sqlite3
86
+ # db.development.db "db/development.sqlite3"
87
+ # db.development.timeout 5000
88
+ # db.create
89
+ # db.migrate
90
+
91
+ # Rake works too
92
+ # Example:
93
+ # rake
94
+
95
+ # Like Git? Set it up!
96
+ # Example:
97
+ # git
98
+ git
99
+
100
+ # Perhaps you like subversion? Use that instead!
101
+ # Example:
102
+ # svn
103
+
104
+ # Need a command not supplied (yet!) by suprails?
105
+ # You can extend it by using runcommand
106
+ # Example:
107
+ # runcommand capify
108
+
109
+ # Oh yeah, you can use plugins, too. Except, to prevent confusion with real
110
+ # rails plugins, we call them facets for suprails. They should be installed at:
111
+ # ~/.suprails/facets
112
+ # Haml is one such facet. It requires special attention because installing it
113
+ # as a plugin does not complete its installation into the rails app
114
+ # Example:
115
+ # haml