
Security News
Node.js Drops Bug Bounty Rewards After Funding Dries Up
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.
directus-sync
Advanced tools
This is a CLI tool to sync schema and configuration from one Directus instance to another.
[!IMPORTANT] Documentation: Check the documentation for detailed information. You need to install the required Directus extension
directus-extension-syncon your Directus instance to use Directus-Sync. Follow the installation instructions in the directus-extension-sync documentation.
[!NOTE] Donate: If Directus Sync is enhancing your team's productivity in a commercial setting, please consider supporting our project financially. More information in the Donate section.
Directus Sync is a powerful CLI tool that enables seamless synchronization and versioning of configurations across multiple Directus instances. It addresses the critical need for maintaining consistent setups across development, staging, production, and any number of additional environments.
By facilitating easy configuration transfers between instances and providing version control, Directus Sync streamlines workflows and enhances collaboration for teams managing Directus deployments.
To use Directus Sync, you need to install the required Directus extension directus-extension-sync on your Directus
instance.
Follow the installation instructions in the directus-extension-sync documentation.
npx directus-sync pull: Retrieve configurations from a Directus instancenpx directus-sync diff: Compare local configurations with a Directus instancenpx directus-sync push: Apply local configurations to a Directus instanceCreate a directus-sync.config.js file in your project root to configure Directus Sync. Example:
module.exports = {
directusUrl: 'https://your-directus-instance.com',
directusToken: 'your-access-token',
dumpPath: './directus-config',
// Additional options...
};
For detailed configuration options, refer to the full documentation.
We're constantly working to improve Directus Sync. Some features we're considering for future releases:
We value your input! Help shape the future of Directus Sync by sharing your experience and suggestions. Please take a moment to complete our feedback form. Your insights are crucial in guiding our development priorities and ensuring Directus Sync continues to meet your needs.
We welcome contributions to Directus Sync! Please check our contribution guidelines for more information on how to get involved.
If you're a solo developer or using Directus Sync for personal projects, please enjoy the tool without any consideration to donate. There are other ways you can support like starring our repository, share your experience with Directus Sync in your network or provide feedback thanks to our feedback form.
If Directus Sync is enhancing your team's productivity in a commercial setting, please consider supporting our project financially. Your contributions enable us to dedicate more time to feature development, ensure long-term maintenance, and potentially provide priority support. Even small donations can significantly impact our ability to improve and expand the tool. By supporting Directus Sync, you're investing in your team's efficiency and the project's future.
If you encounter any issues or have questions, please:
FAQs
This is a CLI tool to sync schema and configuration from one Directus instance to another.
We found that directus-sync demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.

Security News
The Axios compromise shows how time-dependent dependency resolution makes exposure harder to detect and contain.

Research
A supply chain attack on Axios introduced a malicious dependency, plain-crypto-js@4.2.1, published minutes earlier and absent from the project’s GitHub releases.