tack2us

No description

Find a file

Andrew Tomaka ae9aecc2ab Deal with turbolinks $document().ready is only called when the DOM completes loading. Since turbolinks loads new data into the DOM without completely reloading, the ready event is never fired. We can account for this by using the page:load event.		2014-03-09 06:36:23 -04:00
app	Deal with turbolinks	2014-03-09 06:36:23 -04:00
bin	Gemfile updates and gem setup	2014-02-14 15:54:53 -05:00
config	Fix deprecation warning	2014-02-14 15:54:54 -05:00
db	Add inital base paste functionality	2014-02-14 15:54:54 -05:00
lib	rails new tack2us	2014-02-14 15:54:53 -05:00
log	rails new tack2us	2014-02-14 15:54:53 -05:00
public	rails new tack2us	2014-02-14 15:54:53 -05:00
spec	Improve layout flow / tests	2014-02-27 19:52:48 -05:00
test	rails new tack2us	2014-02-14 15:54:53 -05:00
vendor/assets	Setup highlight.js	2014-03-09 06:35:37 -04:00
.gitignore	rails new tack2us	2014-02-14 15:54:53 -05:00
.rspec	Use spork instead of spring	2014-02-14 15:54:53 -05:00
config.ru	rails new tack2us	2014-02-14 15:54:53 -05:00
Gemfile	Use thin instead of webrick	2014-02-14 15:54:53 -05:00
Gemfile.lock	Use thin instead of webrick	2014-02-14 15:54:53 -05:00
Guardfile	Use spork instead of spring	2014-02-14 15:54:53 -05:00
Rakefile	rails new tack2us	2014-02-14 15:54:53 -05:00
README.rdoc	rails new tack2us	2014-02-14 15:54:53 -05:00

README.rdoc

== README

This README would normally document whatever steps are necessary to get the
application up and running.

Things you may want to cover:

* Ruby version

* System dependencies

* Configuration

* Database creation

* Database initialization

* How to run the test suite

* Services (job queues, cache servers, search engines, etc.)

* Deployment instructions

* ...


Please feel free to use a different markup language if you do not plan to run
<tt>rake doc:app</tt>.