On 27 Nov 2006, at 1:43, Alan Macdougall wrote: > On 11/26/06, S K <[EMAIL PROTECTED]> wrote: >> One obvious solution I can think of is to install Tracks on a >> central machine as well as my laptop, mysqldump the database >> content and ship it between the two installs and sync it via a >> script. Any ideas/thoughts? > > There's an easier way, IMO. > > In the past (before I put it on a central server for other reasons) > I used to run Tracks against an SQLite database, with the whole > install living on a usb memory key. This way I could run it on any > machine independently of OS, so long as the machine you want to run > it on has Sqlite and Ruby (and a USB port).
Yes, that would be a good solution, although if you now have internet access from most machines you use, I'm not sure why you need to install it on your laptop as well as a central machine. Why not install it on an internet-accessible server, and then all you need is a computer with a browser and a connection to the internet. As a third possibility the next stable version (and the current development version in the trunk) has a special mobile view which works well on mobile phone browsers. So you could do most of the work from computers accessing a centrally installed version, and then use a mobile phone when you're out and about. > How you get the data out of MySQL and into SQlite may be a bit > tricky though - the data dumps are subtly different (I was changing > jobs at the time I swapped from SQlite locally to MySQL on the > server, so could vaporise most of the tasks and carry the rest over > manually). It's not impossible, and you would only have to do it once if you switched over to SQL. I'm hoping at some point to add export of data (in various formats) and import to get over this difficulty. Just FYI, if you're using the trunk version (and this will be in the next stable release too), you can use rake export_fixtures and rake load_exported_fixtures to dump the contents of your DB to YAML format, then reimport them. As it uses ActiveRecord and stores the data as YAML as an intermediary, it should be able to translate between database formats. cheers, bsag -- but she's a girl - the weblog of a female geek http://www.rousette.org.uk [EMAIL PROTECTED] _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
