just finished porting to 2.3.4. thanks for all your efforts - I stolen a
lot from your previous results ;-)
to test do:
rails test
cd test
script/plugin install git://github.com/yura/railfrog.git
script/plugin install git://github.com/collectiveidea/awesome_nested_set.git
rake db:migrate
rake railfrog:site:load SITE=db/sites/railfrog/
rm public/index.html
script/server
--
Best regards,
Yury Kotlyarov
<;-) BrainHouse
web: http://www.brainhouse.ru
email: yu...@brainhouse.ru
skype: yura__115
phone: +7 905 758 1491
jabber: yury.ko...@jabber.ru
Works sweetly for me :-)
I'll have a think about how to avoid the duplication of railfrog/db/*
and railfrogcms/db/* -- and similarly for .../public. In other words,
the code in install.rb that copies migrations and assets, that would get
triggered if you did script/plugin install, needs to be invoked (rake
task in railfrogcms?) to keep things DRY. Then this looks as though
yura/railfrog and yura/railfrogcms should get merged into railfrog/* ASAP.
The migration numbering has changed, so we'll need a smooth migration
path -- either empty 1..6-*.rb migrations, or a rake task to patch the
schema_migrations table.
And then, unless anyone screams *very* loudly, this will become Railfrog
0.6.
This seems to work now, if anyone wants to play. If you want to upgrade
an existing installation you might be better to wait until the migration
path is smoother.
Major kudos to Yura for getting this out :-D
-- Thomas
I am out of the office and will be back on Monday 14/09.
Urgent messages can be sent to info.b...@transeurope.com.
Kind regards,
Linda Christiaen
Contracts Director
Transeurope
Sint-Jakobsstraat 52
8000 Brugge
Tel: +32 50 34 65 65
Fax: +32 50 34 64 73
www.transeurope.com