docs/install/options/docker-compose.mdx
To get up and running quickly with Activepieces, we will use the Activepieces Docker image. Follow these steps:
You need to have Git and Docker installed on your machine in order to set up Activepieces via Docker Compose.
1. Clone Activepieces repository.
Use the command line to clone Activepieces repository:
git clone https://github.com/activepieces/activepieces.git
2. Go to the repository folder.
cd activepieces
3.Generate Environment variable
Run the following command from the command prompt / terminal
sh tools/deploy.sh
4. Run Activepieces.
<Warning> Please note that "docker-compose" (with a dash) is an outdated version of Docker Compose and it will not work properly. We strongly recommend downloading and installing version 2 from the [here](https://docs.docker.com/compose/install/) to use Docker Compose. </Warning>docker compose -p activepieces up
Note: By default, Activepieces will try to use your public IP for webhooks. If you are self-hosting on a personal machine, you must configure the frontend URL so that the webhook is accessible from the internet.
Optional: The easiest way to expose your webhook URL on localhost is by using a service like ngrok. However, it is not suitable for production use.
ngrok http 8080
AP_FRONTEND_URL environment variable in .env with the ngrok url.Review the configurations guide to make any necessary adjustments. </Warning>
To upgrade to new versions, which are installed using docker compose, perform the following steps. First, open a terminal in the activepieces repository directory and run the following commands.
1. Run the update script
sh tools/update.sh
1. Pull the new docker compose file
git pull
2. Pull the new images
docker compose pull
3. Review changelog for breaking changes
<Warning> Please review breaking changes in the [changelog](../configuration/breaking-changes). </Warning>4. Run the updated docker images
docker compose up -d --remove-orphans
Congratulations! You have now successfully updated the version.
The following command is capable of deleting all Docker containers and associated data, and therefore should be used with caution:
sh tools/reset.sh