Adam
> ...the super_export (which is the only one of the two that will work for
> this) will put its files there too.
The import_export extension can provide a custom path to a yaml file, so
could also be used for this.
e.g.:
rake db:export TEMPLATE="db/path/to/export.yml"
rake db:imp
Anton Aylward wrote:
Hi Anton,
Mohit Sindhwani said the following on 11/13/2008 02:01 PM:
So far, I'm using SQLite, so I just
move the database between my PC and the demo site.
How lucky you are! I tried that, moving from my laptop to my ISP and it
didn't work.
Probably because
On 13-Nov-08, at 2:00 PM, Chris Parrish wrote:
* It's simple (read: non-technical users love it)
* It's db-independent so if my local development environment is
Sqlite3 but my server is MySQL or PostgreSQL (or I want to change
databases/servers some day) it's no sweat to move conten
On 2008/11/13, at 15:00, Chris Parrish wrote:
* Bonus points for managing asset files such as images images
(though I'm not holding my breath here).
I've found page attachments using Amazon S3 as the storage backend
alleviates all of the issues I had surrounding tracking static assets.
Chris,
The import_export extension[1] captures every model in the database
within one big yaml file. By default this is saved as db/export.yml.
Pros:
* very portable
Cons:
* if you want to edit the records captured in the yaml, they can be
quite difficult to find
The super_export extens
One of the problems with Radiant being so extensible is that it attracts
a lot of software geek-types. ;-) It's no issue for me to do a db
dump/restore but I couldn't give that job to my assistant.
Plus I'm not sure that that's a friendly format for, say, version
controlling a site's content
Mohit Sindhwani said the following on 11/13/2008 02:01 PM:
> So far, I'm using SQLite, so I just
> move the database between my PC and the demo site.
How lucky you are! I tried that, moving from my laptop to my ISP and it
didn't work.
Probably because my laptop runs a 32-bit processor and m
Chris Parrish wrote:
I'm looking for a good way to backup/restore all of my content for a
Radiant App. I'm want something that collects all the data (including
extension models).
I'm aware of Import-Export and Super Import-Export but I can't seem to
find anything that clearly spells out the
