Closed ccatlett1984 closed 10 years ago
I'd be totally OK with populating the DB directly through a sql script, although a csv import would be preferred from a usability standpoint.
Would this actually still be a requirement now that users can register and add their own API keys? You can check the key status though the member tracking of the corporation?
Make it easy for admins to switch from ECM to SEAT. Since ECM is now a dead project. On Jun 23, 2014 11:35 AM, "eve-seat" notifications@github.com wrote:
Would this actually still be a requirement now that users can register and add their own API keys? You can check the key status though the member tracking of the corporation?
— Reply to this email directly or view it on GitHub https://github.com/eve-seat/seat/issues/134#issuecomment-46861341.
@ccatlett1984 I am not familiar with the internals of that tool, however, you could prepare SQL statements like the following to bulk add users (sample keyID: 123456; sample vCode:qwertyuiop):
INSERT INTO `seat_keys` (`user_id`, `keyID`, `vCode`, `isOk`, `lastError`, `created_at`, `updated_at`) VALUES (1, 123456, 'qwertyuiop', '1', NULL, NOW(), NOW());
So just extract the keyID's & vCodes, sed/grep/awk them into the above query and run them all. Is this an acceptable solution. I am not sure if we going to look at adding a bulk add atm.
that should work, just didn't know where I needed to add data ;)
One additional thing.
I'd like to auto create the "users" as I already have the username & email.
Then tie the characters to the respective user.
Moving 220+ characters over will save me lots of bitching.
@ccatlett1984 happy if we close this now?
I know I'm not the only one that has a well established corp website with loads of users / keys. Just looking for a non-invasive method to pre-populate my corp-mates data. As it will be pulling teeth to get them to register on another site. I'm getting close to cutting over to SEAT for all of our corps needs, and am starting to look at options to move the users over.