On Nov 18, 2007 10:27 AM, Tim Madden <[EMAIL PROTECTED]> wrote:
>
>  1. Back up existing tracks database with tool of your preference to ensure
> safety of your data (not real experienced here, so I don't have method to
> recommend)
>
>  2. In the tracks 1.5 installation, edit the database.yml file in
> /var/www/tracks15/config/ to point to the new database:
>
>  development:
>    adapter: mysql
>    database: tracks15
>    host: localhost
>    username: tracks
>    password: YourPasswordHere
>    socket: /var/run/mysqld/mysqld.sock
>
>  test:
>    adapter: mysql
>    database: tracks_test
>    host: localhost
>    username: root
>    password: newPassword
>
>  production:
>    adapter: mysql
>    database: tracks15
>    host: localhost
>    username: tracks
>    password: YourPasswordHere
>    socket: /var/run/mysqld/mysqld.sock
>
>
>  3. Edit environment.rb to include the same value in the "salt" field as
> used in the 1.043 installation.  (can they just copy the old environment.rb?
> or has it changed in ways that make it incompatible with 1.5?
>
>
>  4. Create new tracks 1.5 database
>
>  Code:
>  mysql -uroot -p
>  mysql> CREATE DATABASE tracks15;
>  mysql> GRANT ALL PRIVILEGES ON tracks15.* TO [EMAIL PROTECTED] \
>       IDENTIFIED BY 'password-goes-here' WITH GRANT OPTION;
>
>  5. Copy data from the 1.043 database to the 1.5 database
>
>  Code:
>  mysqldump -uroot -pYourPasswordHere tracks1043 | mysql -uroot
> -pYourPasswordHere tracks15
>
>  6. Move to the tracks
>
>  code:
>  cd /var/www/tracks15
>
>  7. Convert the data structure in the track15 database the structure needed
> for version 1.5
>
>  rake db:migrate  RAILS_ENV=production

Hey, all-

Is this still the canonical method for a 1.04*->trunk upgrade? I tried
looking at the svn docs suggested elsewhere in this thread, but they
seem to have disappeared.

Relatedly, is trunk in relatively good shape right now? Or should I
hold off on an upgrade? I'm willing to tolerate some flakiness (and
more than happy to file bugs from the perspective of a skilled but not
expert user) but ideally I'd like at least a little reassurance that
it mostly works, has a reasonably low chance of eating my data, etc.,
etc.

Thanks-
Luis
_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss

Reply via email to