Sean Cribbs
seancribbs.com
On 9/22/06, Steven Noels <[EMAIL PROTECTED]> wrote:
On 22 Sep 2006, at 15:20, Jon Baer wrote:
> This is feasible as the schema setup in rails is db-agnostic.
>
> Edit database.yml w/ sqlite driver
> Generate your tables in sqlite
> rake db:schema:dump
> (this gives you schema.rb, move to production w/ database.yml w/
> mysql driver)
> rake db:schema:load
OK - so now I have recreate tables on the production-side.
Now, since the templates are stored in the (development) DB, I assume
I will still have to recreate them on the production-side? And that
should still be done manually, no? What if I want to do this on a
regular basis: move setup/config, templates _and_ content from
development -> production (and even vice-versa, to test things out).
How would I need to work then?
(sorry for the dumb questions)
Also, I assume the difference between the instance and the
application mode is that the Rails rake stuff gets copied in or not.
So if I want to work with rake, I need to setup up a radiant instance
using the --unpack command.
Thanks for your help!
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought Open Source Java & XML
stevenn at outerthought.org stevenn at apache.org
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
