Python-Service | A Python Service using pywin32 and pyinstaller

As Alex said, specifying port in the URL makes it work. For some reason I though the connection had to be done over container external ports which makes no sense and is obviously wrong. David is also right when he says networks are not necessary. I deleted network declarations from compose file and it also works.

Before making your call do a File.list to see which files the service account has access to. Doing a file.get on a file that the service account doesn't have access to will result in a file not found error. Remember that the service account is not you, it has its own google drive account. Any files you want to access need to be uploaded to its account or shared with the service account.

If the file.list fails then it would suggest to me that there is something wrong with the authorization and you should ensure that the service account has access to client file maybe its that file it cant find.

Create a directory on your personal google drive account. Take the service account email address, it can be found in the key file you downloaded it has a @ in it. Then share that directory on your drive account with the service account like you would share with any other user.

• Adding files to that directory may or may not give the service account access to them automatically permissions is a pain you may need to also share the file with the service account.
• Remember to have the service account grant your personal account permissions to the file when it uploads it its going to be the owner.

An Ingress binds a Service like hello-python-service above to an ALB through the nginx ingress controller.

It does so by mapping a virtual host to your service so that nginx knows how to route requests.

example:

The following in Myservice

Since you haven't provided any error messages, the initial look at Autoscaling template shows several issues.

The AWS::ECS::Service LoadBalancer is an object. There were also other issues:

• Missing DependsOn
• Missing port on container

I used the template in us-east-1 using default VPC. The template will still not work as there are no container instances. But at least your original issue should be addressed.

I made robot-jumpstarter, and yes, it has a fair amount of boilerplate code to make debugging more easy etc.

If you want a bare-bones service, How to write a qimessaging service in the documentation covers that; there's also the tutorial you already found that covers that and in addition also how to use qipkg, which is indeed the standard command-line way of packaging a service. The examples given in those two docs are indeed pretty much as simple as can get.

The minimum structure should be a manifest.xml, a .pml file, and your python script (and maybe an icon for the package; heavily recommended at least, apps without icons are ugly).

You should also be aware that:

• the word "service" can refer either to a NAOqi service (that registers, that you can call with qicli etc. and that is managed by the ServiceDirectory service), or to a systemd service, which is basically a standalone process (that may or may not contain a NAOqi service), that is managed by ALServiceManager
• often when one makes a NAOqi application in Python, the core code of the application is in one or several NAOqi services contained in the application's package ("application" and "service" are not mutually exclusive categories)