Sign in with the default development account:
rm -rf node_modules cache dev
To complete your setup, see my guide on connecting Drupal with Activepieces.
npm start
cd activepieces
npm install
This account is preconfigured so you can start building and testing custom Pieces right away.
Start by deleting all caches:
If you want to contribute to the Drupal Piece integration or create a new Piece, the Docker setup won’t work. To develop or modify Pieces, you’ll need to set up a full Activepieces development environment, which this note explains.
- Email:
dev@ap.com - Password:
12345678
I’ve run into a few issues while working with the Activepieces development environment. Here is what usually fixes them.
git clone https://github.com/YOUR-USERNAME/activepieces.git
First, fork the Activepieces repository on GitHub using the UI. Then clone your fork locally:
When you make changes to the code, they’re automatically compiled and hot-reloaded, so you can see your changes immediately without restarting the development server.
Troubleshooting common issues
Activepieces uses Nx, an open source build system for monorepos. If Nx’s cache is out of sync, reset it to start with a clean slate for builds and tests:
Next, start your local development instance:
If you just want to use Activepieces with Drupal on your local development machine, the easiest option is to follow my guide on running Activepieces locally with Docker. That approach allows you to use Activepieces, but you can’t make code changes to it.
The Drupal Piece code lives in ./packages/pieces/community/drupal.
npx nx reset
