Ah, yes. I did that too... so:
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
On Sat, 2007-11-17 at 22:21 +0100, Reinier Balt wrote:
> Hi Tim,
>
> I was wondering, didn't you need to change the salt in environment.rb
> to the same value you used for 1.043?
>
> Reinier
>
>
> On Nov 17, 2007 9:14 PM, Tim Madden <[EMAIL PROTECTED]> wrote:
>
> Here is the process that I followed to convert my 1.043
> database to the 1.5 database. I am assuming that the user has
> already installed the new tracks on the system. (although
> maybe this should be included as well)
>
> Process to convert existing Tracks 1.043 database to Tracks
> 1.5 on Ubuntu using mysql.
>
> 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. 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;
>
> 4. Copy data from the 1.043 database to the 1.5 database
>
> Code:
> mysqldump -uroot -pYourPasswordHere tracks1043 | mysql -uroot
> -pYourPasswordHere tracks15
>
> 5. Move to the tracks
>
> code:
> cd /var/www/tracks15
>
> 6. Convert the data structure in the track15 database the
> structure needed for version 1.5
>
> rake db:migrate RAILS_ENV=production
>
>
>
>
> _______________________________________________
> Tracks-discuss mailing list
> [email protected]
> http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
>
>
>
_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
