New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rake redmine:backlogs:install failing #387
Comments
That table belongs to redmine itself. Looks like your database got |
Ok, that helps. I went poking and found my railsapp_development database is completely empty but railsapp_production has all the tables. I have seen mention of rails or redmine having a dev vs prod mode....is this related and how can I switch it so the rake command works on prod? |
Yes, it's related. If you have an existing production environment you do not want to go screwing about. But the easiest way (that I've used for my dev, not production environment) is to simply set the entries for development and production in config/database.yml in your redmine directory to be the same. Generally, you need to have redmine up and running before you can install backlogs. |
Ok, thanks so much. |
Did some more digging....this isn't related to line 9-ish in redmine_backlogs/lib/tasks/install.rake is it? |
Final update and I'm closing as this is not a bug per-se: |
I've added it to the installer instead. |
Hi,
Trying to upgrade from v0.6.5 to v0.7.1 or to master per the instructions on http://www.redminebacklogs.net/en/installation.html under "Optional: Getting the latest code" and when I run rake redmine:backlogs:install I get a few deprecated messages but then ultimately:
rake aborted!
Mysql::Error: Table 'railsapp_development.enumerations' doesn't exist: SHOW FIELDS FROM 'enumerations'
I'm new to rails, trying to learn the ropes here so if there is more info I can provide let me know what and how to find it.
I'm wondering if this is related to the version of Redmine I'm running (1.2.1 stable)...or perhaps to the way I updated either it, rails packages and dependencies, or installed other plugins etc in the past.
The text was updated successfully, but these errors were encountered: