Optional pgAdmin
Optional pgAdmin usage for operators who want a graphical database admin tool alongside MatrixEasyMode.
pgAdmin is an optional operator convenience. It is not required to install, run, or upgrade MatrixEasyMode.
Use it when you specifically want a graphical PostgreSQL administration tool. If you do not need that, skip it.
MatrixEasyMode can be operated entirely from the normal helper scripts, logs, and command line workflow.
pgAdmin exists as an optional operator tool for people who want a graphical view into PostgreSQL for investigation, inspection, or careful admin work.
It should be treated as an extra tool, not part of the core runtime.
When to use pgAdmin
Use pgAdmin when you want to:
- inspect PostgreSQL objects visually
- review tables or data during troubleshooting
- confirm database connectivity from an operator perspective
- perform careful database inspection in a more visual workflow
Do not treat pgAdmin as required for normal MatrixEasyMode operation.
For most operators, the primary workflow should still be:
- install MatrixEasyMode
- keep the core stack healthy
- inspect logs and status first
- use optional tools only when they are actually helpful
Why this sits under Tools
pgAdmin belongs under Tools because it is:
- optional
- operator-facing
- outside the core application runtime
- useful for some workflows, but not part of the main install path
That keeps the main docs hierarchy clean.
The core path remains:
- Get Started
- Installation
- Operations
- Troubleshooting
- Upgrading
- Architecture / Network Behavior
And Tools becomes the place for optional operator conveniences.
What MatrixEasyMode already provides
The deployment pack already includes support for optional pgAdmin usage.
That shows up in the repository in two places:
docker-compose.pgadmin.ymltools.sh
The normal installation docs already frame pgAdmin as optional operator tooling rather than part of the required runtime.
Start pgAdmin
Use the helper script:
./tools.sh pgadmin startCheck pgAdmin status
./tools.sh pgadmin statusView pgAdmin logs
./tools.sh pgadmin logsStop pgAdmin
./tools.sh pgadmin stopOperator guidance
A good posture is:
- bring up and verify the core MatrixEasyMode stack first
- confirm PostgreSQL and the application layer are healthy
- only then start pgAdmin if you actually need it
This matters because pgAdmin is a support tool, not a prerequisite.
When pgAdmin is actually helpful
pgAdmin is most useful when:
- you are diagnosing database-related issues
- you want a visual admin interface for PostgreSQL
- you are doing careful operator validation during testing or evaluation
It is less useful when the real problem is elsewhere, such as:
- Nginx Proxy Manager state
- certificates
- public URLs
- DNS
- app-layer configuration
In those cases, start with the normal MatrixEasyMode troubleshooting flow first.
Safety posture
Use pgAdmin deliberately.
A database admin UI is powerful, which means it is easy to confuse investigation with accidental change. In most cases, your first steps should still be:
./stack.sh status
./stack.sh logs infra
./stack.sh logs appUse pgAdmin when you have a clear reason to inspect PostgreSQL more directly.
Keep the core/runtime boundary clear
pgAdmin is not part of the core MatrixEasyMode runtime.
The core runtime remains:
postgresnpmapiweb
pgAdmin is an optional side tool for operators.
That distinction is worth keeping clear in the docs so new operators do not mistake it for a deployment requirement.