auto-install plugin deps

[deadanon]

CREDIT

I give all credit for the idea to k-boikov from https://github.com/Significant-Gravitas/Auto-GPT/pull/4151

Background

Plugin dependencies are not installed automatically without using the --install-plugin-deps flag; however, this isn't very user-friendly from the docker side of things.

Changes

Overwriting the entrypoint via docker-compose to auto-install plugin dependencies if needed

Documentation

--install-plugin-deps is already documented; this is just a uuser-friendlyaddition of that flag to the docker-compose file

Test Plan

docker-compose run auto-gpt

PR Quality Checklist

• [x] My pull request is atomic and focuses on a single change.
• [x] I have thoroughly tested my changes with multiple different prompts.
• [x] I have considered potential risks and mitigations for my changes.
• [x] I have documented my changes clearly and comprehensively.
• [x] I have not snuck in any "extra" small tweaks changes

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
docs	⬜️ Ignored (Inspect)			May 13, 2023 6:36am

[ppetermann]

this will cause it to run the install in the container every time you start it up, and it won't run it for people who don't use docker-compose.

it works, but generally, when building a docker setup you usually want all installation done in the Dockerfile, not through commands injected into the container.

If you don't want to rebuild your auto-gpt image all the time, you can make a dockerfile that extends the original image, and have that rebuild if you change the requirements - if you don't mind rebuilding the auto-gpt image, then you can do just that, both better than installing all requirements every time you start the container.

(That is once #4151 is merged, until then the easiest way is to extend image and have your own image run the same line from that commit)

Edit: sorry this was confusing, rephrased