It’s not obvious or documented how you use the asposewordscloud · PyPI library with the self-hosted docker container.
I’ve figured out how to override the base URL but the library tries to perform OAuth. It seems every SDK is built this way - how do you turn it off?
I’ve also had issues because the library only supports python 3.7. This python version went EOL 2 years ago - when are you going to update to something that is supported?
To use the Aspose.Words Cloud Python library with a self-hosted Docker container, you need to adjust the base URL to point to your Docker instance. You can do this by setting the host configuration in your code like this:
words_api.api_client.configuration.host = "http://localhost:8082"
For authentication, instead of using client_id and client_secret, you can set the User and Password environment variables when you run your Docker container. This can be done with the following command:
docker run -e "User=user_id" -e "Password=user_secret" your_docker_image
This way, you can bypass the OAuth mechanism that the SDK typically uses, allowing you to authenticate using the credentials you set in the Docker container.
Regarding your concern about the Python version, the current SDK version supports Python 3.7, which is indeed an older version. Unfortunately, there is no specific timeline available for when the SDK will be updated to support newer versions of Python. You may want to keep an eye on the official Aspose documentation or forums for any announcements regarding updates.
If you have further questions or need assistance with specific implementation details, feel free to ask!
Sources:
[1]: Docker self-hosted license issue
[2]: Aspose Documentation Available SDKs|Aspose Words Cloud Docs
Can I get the swagger spec then to regenerate a client? There is no way we can run python3.7 - that’s a huge security violation.
We will update the supported version in the upcoming release.