Friendly Tip #1: If you want to experiment, you can fork or clone the public repository.
For private piece installation, you will need the paid edition. However, you can still develop pieces, contribute them back, OR publish them to the public npm registry and use them in your own instance or project.
By following these steps, you can create a private fork on GitHub, GitLab or another platform and configure the “activepieces” repository as the upstream source, allowing you to incorporate changes from the “activepieces” repository.
Clone the Repository:
Begin by creating a bare clone of the repository. Remember that this is a temporary step and will be deleted later.
Generate a new private repository on GitHub or your chosen platform. When initializing the new repository, do not include a README, license, or gitignore files. This precaution is essential to avoid merge conflicts when synchronizing your fork with the original repository.
Mirror-Push to the Private Repository:
Mirror-push the bare clone you created earlier to your newly created “activepieces” repository. Make sure to replace <your_username> in the URL below with your actual GitHub username.
Copy
Ask AI
cd activepieces.gitgit push --mirror git@github.com:<your_username>/activepieces.git
Remove the Temporary Local Repository:
Copy
Ask AI
cd ..rm -rf activepieces.git
Clone Your Private Repository:
Now, you can clone your “activepieces” repository onto your local machine into your desired directory.
Copy
Ask AI
cd ~/path/to/directorygit clone git@github.com:<your_username>/activepieces.git
Add the Original Repository as a Remote:
If desired, you can add the original repository as a remote to fetch potential future changes. However, remember to disable push operations for this remote, as you are not permitted to push changes to it.