12 tools for the new Confluence toolkit. | Name | Description | |----------------------------------|------------------------------------------------------------------------------------| | Confluence.CreatePage | Create a new page at the root of the given space. | | Confluence.UpdatePageContent | Update a page's content. | | Confluence.RenamePage | Rename a page by changing its title. | | Confluence.GetPage | Retrieve a SINGLE page's content by its ID or title. | | Confluence.GetPagesById | Get the content of MULTIPLE pages by their ID in a single efficient request. | | Confluence.ListPages | Get the content of multiple pages by their ID. | | Confluence.ListAttachments | List attachments in a workspace. | | Confluence.GetAttachmentsForPage | Get attachments for a page by its ID or title. | | Confluence.SearchContent | Search for content in Confluence. | | Confluence.GetSpace | Get the details of a space by its ID or key. | | Confluence.ListSpaces | List all spaces sorted by name in ascending order. | | Confluence.GetSpaceHierarchy | Retrieve the full hierarchical structure of a Confluence space as a tree structure.| ### Confluence Clients Confluence has deprecated most of their V1 endpoints, so most of the tools use V2. However, we still need a V1 client to support search. The V1 search API has not been deprecated yet, because there is no V2 equivalent. But we need to be aware in the future for when this deprecation happens. ### Future work * Content of pages are returned in the Confluence `storage` format. This is the format that Confluence uses to store pages internally. We should understand the storage format more deeply, and write utility function to transform this format into plain text. * Better protections against extremely large pages. I've tested up to 6,000 word pages. * Tools for blog posts * Tool for getting the children of a page. (`get_space_hierarchy` will suffice for now) * Allow for numerical titles |
||
|---|---|---|
| .. | ||
| 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
Change to the docker directory:
cd arcade-ai/docker
2. Copy and Configure Environment Variables
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
3. 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.
4. 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:
{ "status": "healthy" }
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.