Gitlab moved to mysql

Created by: dzaporozhets

1. bundle
2. sudo apt-get install mysql-server libmysql-ruby libmysqlclient-dev
3. bundle exec rake db:data:dump RAILS_ENV=production -> Dump contents of Rails database to db/data.yml
4. Edit database.yml
5. bundle exec rake db:setup
6. bundle exec rake db:data:load RAILS_ENV=production -> Load contents of db/data.yml into the database

Created by: tader

+1 ;)

By Administrator on 2012-03-07T09:46:25 (imported from GitLab project)

By Administrator on 2012-03-07T09:46:25 (imported from GitLab)

Created by: tarakanbg

Will you be adding some mysql specific SQL syntax or data types that will enforce the migration to mysql, or will this remain optional for users that don't care much about scalability and locking issues and will prefer to remain on sqlite and not to take the server performance tradeoff that mysql imposes?

By Administrator on 2012-03-07T13:39:45 (imported from GitLab project)

By Administrator on 2012-03-07T13:39:45 (imported from GitLab)

Created by: dzaporozhets

Cause app works for both db now I think we'll recommend mysql, but keep support of sqlite

By Administrator on 2012-03-07T13:41:02 (imported from GitLab project)

By Administrator on 2012-03-07T13:41:02 (imported from GitLab)

Created by: tarakanbg

Ok, thanks for the fast answer and that sounds perfectly reasonable solution. Choice is always good :)

By Administrator on 2012-03-07T13:43:24 (imported from GitLab project)

By Administrator on 2012-03-07T13:43:24 (imported from GitLab)