ChiliProject is not maintained anymore.
Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and
we urge all existing users to migrate their data to a maintained
system, e.g. Redmine. We will
provide a migration script later. In the meantime, you can use the
instructions by
Christian Daehn.
Forums » Develop »
Getting rid of test_postgres, test_mysql, test_sqlite
Added by Gregor Schmidt at 2011-03-21 09:30 am
I would like to know, if anybody is actually using these environment. If not, I would like to get rid of them. I think, they don't buy us anything.
On the other hand, the constantly annoy me, when I run rake db:drop:all
or rake db:create:all
. If they are just there as a helper, on how to define connections for each supported database, they should simply become comments.
What do you think?
Gregor Schmidt wrote:
they should simply become comments.
Commenting those envs is the first thing I do when editing the config, so yay for commenting them from me.
I don't. I just use some YAML tricks and variables to switch environments and databases. I forgot all about those other ones completely.
Eric Davis
### Adapters
mysql: &mysql
adapter: mysql2
host: localhost
username: root
password: password
postgresql: &postgresql
adapter: postgresql
host: localhost
username: edavis
password: password
sqlite3: &sqlite3
adapter: sqlite3
database: db/development.sqlite3
### Main databases
cp: &cp
<<: *postgresql
database: chiliproject
cp_master: &cp_master
<<: *postgresql
database: chiliproject_master
cp_mysql: &cp_mysql
<<: *mysql
database: chiliproject
cp_test: &cp_test
<<: *postgresql
database: chiliproject_test
cp_mysql_test: &cp_mysql_test
<<: *mysql
database: chiliproject_test
chili: &chili
<<: *mysql
database: chili
### Rails definations
main: &main
<<: *cp
# <<: *chili
# <<: *mysql
# database: redmine_11
test:
<<: *cp_test
database: chiliproject_test<%= ENV['TEST_ENV_NUMBER'] %>
production:
<<: *main
development:
<<: *main
staging:
<<: *main
(My Redmine version is way more complex. 153 lines at the moment...)
So I guess, I could open a ticket and pull request to remove them? Any votes against?