gradio-tools VS aws-organization-for-devs

We leverage Transformers Agent to generate an image to accompany a talk. This was a bit tricky to get going because the example I was working from uses gradio_tools which seems like a great library for LLM agents using Python, however it requires Python 3.8 or greater and the Docker image we were using was last built a year ago on Ubuntu 18 which uses Python 3.6. This is a very frustrating class of problem to have and I spent about a day trying to find a substitute image to work with or (ugh) upgrade Python in our base image. Ultimately I rebuilt the same image using Ubuntu 22 and Python 3.9 and that worked out for us, but it was a bit of a journey to get there.

Gradio tools is an open source library that lets you combine an LLM agent with any gradio app, and it integrates with Langchain. Honestly I can see so many use cases with something like this, just not enough time to build 😢 [Link]

Huge shoutout to AWS Community Builder Matt Morgan who has created an awesome AWS Organizations for devs GitHub repository where you can learn about deploying full AWS Organizations!

I had set up a Community Builders AWS Organization recently using superwerker. My intent is for this organization to show the best practices for setting up a multi-account organization with Organizational Units representing sandbox, test and production environments, scoped developer roles and limited production access. I think the developer roles need a little work, but the group was able to be productive in this environment, so that's a win.