Skip to content
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

There is still a problem with the credentials. There is a known problem with the assistant and speech-to-text creds role. There is a workaround. #64

Open
markstur opened this issue Sep 25, 2020 · 2 comments

Comments

@markstur
Copy link
Contributor

markstur commented Sep 25, 2020

There is still a problem with the credentials. There is a known problem with the assistant and speech-to-text creds roles. There is a workaround that works for both.

Go to the Cloud Foundry App -> Runtime -> Environment Variables and add the Assistant and STT creds (APIKey and URL) using the same key/values described for use in the local runtime .env. We'll need to document this if we don't come up with an alternative.

Adding a screenshot here for now:

runtime_env

Originally posted by @markstur in #55 (comment)

@markstur markstur changed the title There is still a problem with the credentials. There is a known problem with the assistant creds role, but I'm not sure why there is a problem with STT/TTS. There is a workaround that works for both. There is still a problem with the credentials. There is a known problem with the assistant creds role. There is a workaround. Sep 25, 2020
@markstur markstur changed the title There is still a problem with the credentials. There is a known problem with the assistant creds role. There is a workaround. There is still a problem with the credentials. There is a known problem with the assistant and speech-to-text creds role. There is a workaround. Sep 25, 2020
@markstur
Copy link
Contributor Author

Note: For assistant make sure you are using the APIKEY from the "Service" and not the "Cloud Foundry Service".

Same for STT.

TTS seems to be working fine from the CF provided VCAP_SERVICES runtime variable. You should not need to add these as shown in the image. Just ASSISTANT_APIKEY and URL and SPEECH_TO_TEXT_APIKEY and URL

@markstur
Copy link
Contributor Author

Update: Seems to work better if you also specify runtime env for TEXT_TO_SPEECH_APIKEY and TEXT_TO_SPEECH_URL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant