Watson STT Patch

[seanmtracey]

Temporary fix to enable users of newer Watson STT credentials to continue using autoEdit until such a time that the copy / setup steps can be updated.

Suffice it to say:

Instead of using a username/password combination use:

apikey as the username <YOUR_API_KEY_FROM_YOUR_RECENT_STT_INSTACE> instead of password.

You will also need to include the url value from the credentials object (where you get your API key from) along with the above.

Addresses #49

[pietrop]

Thanks for this @seanmtracey !

I noticed you need some changes in file like

• docs/demo/app.js
• docs/demo/watson_keys.js
• project_page/demo/app.js

Unfortunately those are the pages for the online dummydemo the main app lives inside lib/app and electron where you got app.js is bundled and the main index.html for electron is as well.

And then npm run make_demo is used to create the folder from the client side part of the app (backbone). And npm run make_page is used to create the project for github pages, inside docs folder at root of repo.

Anyway going to try and see if I can port those changes inside the corresponding files in lib/app etc.. but I'll let you know if I get stuck.

[pietrop]

sorry, my bad, just realised that those files in docsand project_page might have been generated when you did npm start ...

Anyway I run it with the credentials and seemed to work, altho I didn't put apikey in username, just the regular username.

altho I had an issue, but I think it's unrelated, and think was happening before as well, so logged it here https://github.com/OpenNewsLabs/autoEdit_2/issues/51

@seanmtracey could you clarify what is the IBM change in credentials and location, how can one tell if they are supposed to put username + password credentials of instance + url based on region OR apikey + <YOUR_API_KEY_FROM_YOUR_RECENT_STT_INSTACE> instead of password + url ?

I am still unsure how that, and I'd like to update the user manual accordingly.

Thanks!