gsrohde
commented
10 years ago Right now, all of the deployments of BetyDB on pecandev except for the one at /beta share the same production database named ‘bety’. So you would think the same logins would work on all of them. But the site key that /jk and /dl are using is different from the one /ebi (= pecandev/bety), /beta, and /sr are using. This is the string in the file /config/initializers/site_keys.rb. Feel free to change the site key for /jk to ‘thisisnotasecret’. If you do this (and run “touch tmp/restart.txt” in the /usr/local/jk directory to restart the rails server), you should be able to log in using carya/illinois (and I think most the other users have password ‘illinois’ as well). But probably the login you were using (‘carlcrott’?) will no longer work after this.
If you want me to re-download a more up-to-date copy of the bety database, let me know. This may fix some of the problems with the autonumbering. (Which kind of record were you trying to add?)
Scott
On Jul 3, 2014, at 5:03 PM, phenolphtalein notifications@github.com<mailto:notifications@github.com> wrote:
I'm wondering if the schema/content database on the pecandev server is being changed frequently or something? Because when I tried to add a record to the database at http://pecandev.igb.illinois.edu/jk, I got this error in the log: "Duplicate entry '0' for key 1". This problem has never showed up before and I found it's somehow related to the auto increment counter inside the database which I don't think has anything to do with the code we wrote... And also, most of the logins on that site have become invalid for unknown reason.
— Reply to this email directly or view it on GitHubhttps://github.com/PecanProject/bety/issues/91.
I'm wondering if the schema/content database on the pecandev server is being changed frequently or something? Because when I tried to add a record to the database at http://pecandev.igb.illinois.edu/jk, I got this error in the log: "Duplicate entry '0' for key 1". This problem has never showed up before and I found it's somehow related to the auto increment counter inside the database which I don't think has anything to do with the code we wrote... And also, most of the logins on that site have become invalid for unknown reason.