| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
| | | |
| | | |
| | | | |
ENGINE_PATH is available
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Some of the engines needs database. As engine needs to be run inside
Rails application, migrations and other database operations are run
from dummy application. To make that process simple I changed db
tasks to look for migrations in both engine's and application's
db/migrate directory. You can run all of the database tasks from
test/dummy or directly from engine with prefix app, like:
rake app:db:migrate
rake app:db:migrate:redo
|
| |/ /
| | |
| | |
| | | |
record is skipeed
|
|/ / |
|
|\ \ |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
and after
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
documentation
|
| |
| |
| |
| | |
config guide
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
create is for creating
|
| |
| |
| |
| | |
associations of the belongs_to and has_one type
|
| |
| |
| |
| | |
documentation in configuring guide
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
the generators guide
|
| |\ |
|
| | | |
|
| |\ \
| | | |
| | | |
| | | | |
gjastrab-master
|
| | |/ |
|
| | | |
|
| | |
| | |
| | |
| | | |
config guide
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
users should *never* do that.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|