The job to be done
How does DevDock help with multi-stack products?
Treat a Laravel API, React frontend, and mobile client as one project without forcing them into one repository.
The Today view surfaces recent projects and saved daily workflows. Inside a project, DevDock connects registered folders, detected technologies, Docker and Git state, database operations, local security findings, and the actions you use to get back to work.
Recommended path
Add a project
Register a local project folder and give it a clear place in the sidebar.
DevDock keeps the project, registered folder, working directory, execution target, and retained output connected so the same task remains understandable later.
Capabilities involved
The parts of DevDock used here.
Related manual
Organize multi-folder and multi-repository projects
Represent a complete product without forcing its API, web client, mobile app, and infrastructure into one repository.
Its sections cover choose the workspace boundary, add and label folders, keep detection scoped, name commands for the whole product, use project shortcuts, restructure without losing clarity. Use it when you are ready to reproduce this workflow with your own project data.
Read the guideDirect answers
Questions about this use case.
How does DevDock help with multi-stack products?
Treat a Laravel API, React frontend, and mobile client as one project without forcing them into one repository. The recommended path starts with add a project and uses registered folders, project workspace, project shortcuts.
Does DevDock replace the terminal?
No. It provides a repeatable control surface for common project workflows and can still open a registered folder in a terminal, Visual Studio Code, or File Explorer.
Does project detection run repository code?
No. Detection reads a bounded set of manifests and marker files. It does not execute package managers, build tools, project scripts, or network requests.