# PR Description ## Split toolkits This PR splits the `Microsoft`, `Google`, and `Search` toolkits into multiple toolkits each. * `Microsoft` --> `OutlookCalendar`, `OutlookMail`. * `Google` -----> `GoogleCalendar`, `GoogleContacts`, `GoogleDocs`, `GoogleDrive`, `Gmail`, `GoogleSheets` * `Search` -----> `GoogleFinance`, `GoogleFlights`, `GoogleHotels`, `GoogleJobs`, `GoogleMaps`, `GoogleNews`, `GoogleSearch`, `GoogleShopping`, `Walmart`, `Youtube` > The original monolithic toolkits (`Microsoft`, `Google`, `Search`) are not removed in this PR. The plan is to keep those toolkits around while we > 1. Stop documenting the toolkits, > 2. Stop displaying the toolkits in the dashboard, and > 3. Help customers migrate over to the new split toolkits. ## Rename toolkits This PR renames the following toolkits * `Web` ------------> `Firecrawl` * `CodeSandbox` ---> `E2B` > The `Web` and `CodeSandbox` toolkits are not removed in this PR. The plan is to keep them around while we > 1. Stop documenting the toolkits, > 2. Stop displaying the toolkits in the dashboard, and > 3. Help customers migrate over to the new renamed toolkits. ## Rename tools Since toolkit names were changed, this called for some tools to be renamed as well. * `GoogleSearch.SearchGoogle` ----------------> `GoogleSearch.Search` * `GoogleShopping.SearchShoppingProducts` ---> `GoogleShopping.SearchProducts` * `Walmart.SearchWalmartProducts` ------------> `Walmart.SearchProducts` * `Walmart.GetWalmartProductDetails` ---------> `Walmart.GetProductDetails` * `Youtube.SearchYoutubeVideos` --------------> `Youtube.SearchForVideos` ## Google File Picker Improvements to the Google File Picker experience were also added in this PR. The following tools will ALWAYS provide llm_instructions in their response to "let the end-user know that they have the option to select more files via the file picker url if they want to": * `GoogleDocs.SearchDocuments` * `GoogleDocs.SearchAndRetrieveDocuments` * `GoogleDrive.GetFileTreeStructure` The following tools will only provide the file picker URL if a 404 or 403 from the Google API: * `GoogleDocs.InsertTextAtEndOfDocument` * `GoogleDocs.GetDocumentById` * `GoogleSheets.GetSpreadsheet` * `GoogleSheets.WriteToCell` Also, a standalone `GoogleDrive.GenerateGoogleFilePickerUrl` tool exists. ## Other * The `SearchDocuments` and `SearchAndRetrieveDocuments` tools used to be organized within the Drive portion of the Google toolkit, but I moved these into the new GoogleDocs toolkit because they are specific to Docs. # Progress - [x] `OutlookCalendar` - [x] `OutlookMail` - [x] `GoogleFinance` - [x] `GoogleFlights` - [x] `GoogleHotels` - [x] `GoogleJobs` - [x] `GoogleMaps` - [x] `GoogleNews` - [x] `GoogleSearch` - [x] `GoogleShopping` - [x] `Walmart` - [x] `Youtube` - [x] `GoogleCalendar` - [x] `GoogleContacts` - [x] `GoogleDocs` - [x] `GoogleDrive` - [x] `Gmail` - [x] `GoogleSheets` - [x] `Firecrawl` - [x] `E2B` - [x] File picker # Discussion * Repeated code is a consequence of splitting toolkits that use the same provider. I am open to any ideas that would allow multiple toolkits to reference common code. Comment your ideas in this PR. |
||
|---|---|---|
| .. | ||
| docker-compose.yml | ||
| docker.engine.yaml | ||
| Dockerfile | ||
| env.example | ||
| Makefile | ||
| nginx.conf | ||
| README.md | ||
| start.sh | ||
| toolkits.txt | ||
Arcade Docker Compose Guide
This guide provides detailed instructions on how to set up and run Arcade using Docker Compose.
Prerequisites
- Docker installed on your system. Install Docker
- Docker Compose installed. It comes bundled with Docker Desktop on Windows and macOS. For Linux, follow the Docker Compose installation guide.
Getting Started
1. Clone the Repository
Begin by cloning the Arcade repository:
git clone https://github.com/ArcadeAI/arcade-ai.git
2. Build package wheels
From the root of the arcade-ai repository:
make full-dist
3. Copy and Configure Environment Variables
Change to the docker directory:
cd arcade-ai/docker
Copy the example environment file to .env:
cp env.example .env
Open the .env file in your preferred text editor and fill in the required values. At a minimum, you must provide the OPENAI_API_KEY:
### LLM ###
OPENAI_API_KEY=your_openai_api_key_here
If you plan to use other Large Language Model (LLM) providers, add their API keys as well:
ANTHROPIC_API_KEY=your_anthropic_api_key_here
4. Run Docker Compose
Start the Arcade services using Docker Compose:
docker compose up
This command will build and start all the services defined in the docker-compose.yml file and make their ports available to your host machine.
5. Verify the Engine is Running
In a separate terminal window, check if the engine is running:
curl http://localhost:9099/v1/health
You should receive a response indicating that the engine is healthy:
{ "healthy": "true" }
Open a browser and navigate to http://localhost:9099/dashboard to view the Arcade dashboard.
Adding Authentication Providers
Arcade supports various authentication providers. To add an auth provider, follow these steps:
1. Enable the Auth Provider in the Configuration
Edit the docker.engine.yaml file to enable the desired auth provider. For example, to enable Google authentication, modify the file as follows:
auth:
providers:
- id: google
enabled: true # Change from false to true
2. Add Client ID and Secret to the .env File
Obtain the client ID and client secret from your auth provider and add them to the .env file:
GOOGLE_CLIENT_ID="your_google_client_id"
GOOGLE_CLIENT_SECRET="your_google_client_secret"
Repeat this step for any other auth providers you wish to enable.
3. Restart the Docker Compose Services
After making changes to the configuration, restart the services:
docker compose down
docker compose up
Troubleshooting
- Engine Health Check Fails: Ensure that all environment variables are correctly set in the
.envfile and that the services have started without errors. - Port Conflicts: If the default ports are already in use, modify the ports in the
docker-compose.ymlfile. - Authentication Errors: Double-check the client IDs and secrets provided for auth providers.
NOTE: arcade login will not work within a docker container, you must copy your credentials into the container if you would like to use it.