Consolidate tools #12
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… and projects Co-authored-by: HenkDz <[email protected]>
- Split dokploy_database into dokploy_postgres and dokploy_mysql - Merge all domain tools into dokploy_application - Final tool count: 4 consolidated tools (dokploy_application, dokploy_postgres, dokploy_mysql, dokploy_project) - All 67 original API calls remain accessible through consolidated tools Co-authored-by: HenkDz <[email protected]>
- Document all 4 consolidated tools with action parameters - Add comprehensive examples for each tool - Include migration guide from individual tools - Add security considerations and usage notes Co-authored-by: HenkDz <[email protected]>
Co-authored-by: HenkDz <[email protected]>
…itions Refactor existing tool definitions for consolidated architecture
Author
|
Consoidation is needed because AI assistants get confused when given large number of tools to work with ( 67 in this case) I turned them into 4. Moreover, I added project lock and tools whitelist features as well: 
The goal behind project locking is to focus on the project we are working on and for tools whitelist is to focus on the stack the current project uses, like there's no point of having MySQL tools when I only use Postgres and need its realted tools. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a major refactor to the Dokploy tool system by consolidating multiple resource-specific tools (for applications, domains, MySQL, PostgreSQL, and projects) into unified, action-driven tools. Instead of exposing each resource operation as a separate tool, the new approach provides a single tool per resource type that accepts an action parameter to determine the operation. This simplifies the tool interface and makes it easier to manage and extend.
The most important changes are:
Consolidation of Tools:
dokployApplication), MySQL (dokployMysql), PostgreSQL (dokployPostgres), and projects (dokployProject). Each tool now handles multiple actions through anactionparameter, routing to the appropriate handler internally. [1] [2] [3] [4]Exports and Tool Registry Update:
consolidated/index.tsfile to export the new consolidated tools.tools/index.tsto import only the consolidated tools and expose them as the complete set of available tools, removing the previous resource-specific tool imports.These changes greatly simplify the codebase and the interface for managing Dokploy resources, making it easier for both developers and users to interact with the system.