ToolJet GitSync Community Call February 2024: Key Insights and Highlights

We extend our gratitude to all participants who joined our Community Call on February 29, 2024. The session proved to be an enriching experience, covering various aspects of the GitSync feature in ToolJet. Below, you’ll find the video capturing the highlights and detailed discussions from the call.

Let’s go through a quick summary of the key topics that we covered.

We initiated the session by exploring the configuration process of GitSync within the ToolJet workspace settings by going ahead to Workspace settings and configuring different keys along with a newly created GitHub repository. Here’s a detailed breakdown of the steps:

• Workspace Setting: To configure GitSync, navigate to the workspace settings.
• Permission Level: Ensure administrative or owner-level permissions for configuring GitSync.
• Provider Support: Select your Git provider from the supported list, including GitHub, GitLab, and Bitbucket.
• Key Support: Generate authentication keys (e.g., SSH keys) for secure connection between ToolJet and your Git repository.
• Auto Commit: Enable auto-commit for seamless synchronization of changes made in ToolJet with your Git repository.

We then moved on to the importance of syncing application resources with our Git repository, where we added a new button to our App-Builder and committed it. Here are the steps:

• Sync Application Resources: Ensure that your application resources, including configurations, code files, and assets, are properly synchronized with your Git repository. Monitor the sync status to confirm that all changes are accurately reflected in your repository.
• Auto-Push Feature: Activate the auto-push feature for basic operations to automate the synchronization process. With auto-push enabled, ToolJet will automatically push changes to your Git repository, reducing manual intervention and ensuring that your repository remains up-to-date.
• Check Your Last Commit: Review your last commit to verify the changes made and ensure that they align with your project’s objectives.

For migrations and importing existing apps, we discussed how we can import the application and start using it in our application along with the steps involved:

• Import Existing App: Utilize the “Import from git repository” option within the ToolJet dashboard to seamlessly import apps from any repository.
• Pull Latest Updated Version: Keep your app up-to-date by checking for updates in the Git repository via the GitSync feature.

We explored various use case scenarios, including:

• Application Data Backup: Utilize GitSync for secure data backup and version control.
• Migration Between Instances: Effortlessly migrate apps between instances while preserving configurations.
• Editor Operations Tracking: Track changes made by users within the application’s editor environment.
• Better Project Development Management: Implement version control and collaboration features for enhanced project management.

Looking ahead, we discussed potential improvements to GitSync along with feedbacks taken from community and customers, such as:

• Improving Task Tracking: Integrating task management features within GitSync.
• Adding More Git Operations: Incorporating advanced Git operations for enhanced version control.
• Adding More Data Points: Extending synchronization to include additional data points.
• Improving Syncing ToolJet DB Schema: Enhancing synchronization of ToolJet database schema changes.

We hope you found this community call informative and helpful. Since this call happens every month, we’re open to topics for future sessions. Your feedback matters — let us know how we can make them even better. You can connect with us through our social media links provided below. We truly value your insights.

• ToolJet Documentation:  Docs – ToolJet
• GitSync Documentation: Docs – Gitsync

• Slack:  ToolJet – Slack
• Twitter:  ToolJet – Twitter
• Blog:  ToolJet Blog