We have implemented the Alexa skill with Node.js application. But the Node.js application domain is sub-domain like https://test.example.com/,
Does Alexa support sub-domains?
it shouldn't matter if you have a subdomain for your end point as long as it matches the requirements alexa specifies
for more information on that check the alexa documentation
Related
I am looking for a documentation or Github to build a HTML 5 (non gaming) skill in Alexa.
The Web API for Games is currently the only Alexa Skills Kit API that exposes HTML5 on compatible devices and the docs for that say specifically it's only approved for games.
https://developer.amazon.com/en-US/docs/alexa/web-api-for-games/understand-alexa-web-api-for-games.html#requirements-for-the-skill-and-web-app
I doesn't have much experience with Alexa Voice Service. But i hope someone can help me in this scenario.
I just used the Raspberry Example for Alexa Voice Service in the past.
But this example hat the Limitation that Amazon Music was not supported.
Also other 3rd Party Apps which use Amazon Voice Services (e.g. Reverb) are restricted and can't use Amazon Music.
As far as i know, this is a limitation because license issues.
I have now an Use Case to develop either an Desktop App or an Web-App which should interact with Alexa, but also be possible to play Amazon Music.
My Question: Has someone experience with Alexa Voice Service, to use it, AND have access to Amazon Music? (maybe there is a solution to pay something for licence etc.(
Or is Alexa Voice Service in general restricted with Amazon Music.
Kind Regards
Stefan
Alexa Voice Service can certainly be used with Amazon Music (and several other music providers). You need to get approval from Amazon for the music service you want to use. You can find more details by going to your AVS dashboard and looking in the entertainment tab on the product you want to enable music.
I am going to build an API for my mobile app using GAE. I am looking for a way to separate the whole application into separate services, trying out the microservice architecture.
The problem is there seems to be no information about any VPN or private network between GAE apps. Therefore, based on my understanding, when one of the GAE apps sends HTTP requests to other GAE apps in same account, its traffic will be treated as Internet traffic and therefore I will be charged for outbound bandwidth.
Am I correct?
Yes.
App Engine applications/Cloud Platform projects are isolated from each other by default, even if they were created using the same Google account.
Consider looking into Modules (link for Java) to implement individual services of your application.
Is there a way to set up an appengine web application to deploy on a website without making the user type in www.url.com?
I have it deployed to www.url.com but url.com does not work.
Is this possible with appengine?
AppEngine does not currently support naked domains.
The best that you can do right now is set up your naked domain name to automatically redirect to the www. version.
Useful Links:
Google Code Issue requesting support for Naked Domains
Nick Johnson's explanation for why the restriction exists
I'm trying to map my (naked) domain to an app.
I found this.
I'd like to map my app to http://myurl.com (also known as a naked
domain).
Due to recent changes, Google App Engine no longer supports mapping
your app to a naked domain. If your domain registrar supports URL
redirects, you can redirect from http://yourdomain.com to your app,
which can be served from domains like http://www.yourdomain.com or
http://appid.yourdomain.com.
For instructions on how to configure a redirect for your Google Apps
domain, please see the article on URL forwarding.
Now I'd like not to resort to redirection. I understand udacity.com is hosted on appengine and they seem to use a naked domain.
So, I;m hoping this is just typical bad documentation or not updated. Does anybody have any info on how Udacity solves this problem or how could I produce such a behaviour?
AFAIK AppEngine cannot be map to a naked domain, you can have a proxy mapped on your naked domain they will proxy into the application.
What most applications do is use forward from the naked domain to www where the application is mapped. GoDaddy supports that GoogleApps supports that and various other free and paid DNS services support that.