Use-case guide Windows

Inspect, diagnose, export, and restore project databases

Inspect application schemas, find a bounded set of records, review migration state, and create or restore native database backups from the project workspace.

The job to be done

How does DevDock help with local database operations?

Inspect application schemas, find a bounded set of records, review migration state, and create or restore native database backups from the project workspace.

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.

DevDock command workspace showing a detected development command and its output area
Commands stay attached to the project, working directory, and execution target they belong to.

Recommended path

Review the workspace

See its folders, health, saved commands, and recent activity from one overview.

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

Database tools, schema inspection, and backups

Use DevDock with SQLite, MySQL/MariaDB, PostgreSQL, and detected Laravel databases for safe lookups, schema review, diagnostics, exports, and confirmed restores.

Its sections cover choose the project or direct connection, understand the supported database engines, inspect schema before querying, find records with a constrained lookup, export and restore native backups, use laravel diagnostics and maintenance, troubleshoot without weakening safety. Use it when you are ready to reproduce this workflow with your own project data.

Read the guide

Direct answers

Questions about this use case.

How does DevDock help with local database operations?

Inspect application schemas, find a bounded set of records, review migration state, and create or restore native database backups from the project workspace. The recommended path starts with review the workspace and uses database tools, project workspace, command history.

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.

Next

Explore more DevDock workflows.

Back to use cases