dmarts

This post was a long, long time ago... but I managed to get this working and I can try and answer some questions if anyone wants. Can't tell you best practice or anything like that. I've got the geemusic docker running, and the API it exposes (local only) is exposed to the internet by nginx as https://mydomainname.com/alexa - this then goes in the Alexa Dev Console with the certificate option as "My development endpoint is a sub-domain of a domain that has a wildcard certificate from a certificate authority". The SSL / certificates part was all managed by the letsencrypt docker, which is pretty well documented online... it requests the certificate itself and applies it so geemusic doesn't need to know about SSL, it just exposes the API locally and nginx (in the letsencrypt docker) handles the encryption. The letsencrypt docker is awesome and I would recommend it - it 8/10 easy to get everything working but 25/10 for the security I needed. So the overall process for a request on my setup is: Alexa device sends request to Alexa servers (and a whole bunch of other stuff) Alexa things happen using the custom skill that I copy/pasted in there according to the instructions, then it calls the endpoint https://mydomainname.com/alexa nginx is exposing that endpoint to the internet (in my case nginx is in the letsencrypt docker) nginx passes that request to an endpoint on the geemusic docker, i.e. 'for the /alexa path on https://mydomainname.com, send the requests on to localhost:5000', which happens to be where the geemusic docker is exposing an endpoint geemusic docker gets the request and does geemusic stuff and returns a response back to Alexa (a URL for the track / whatever) Sweet sweet music