Tools
Optional operator tooling for inspecting and managing a MatrixEasyMode deployment.
MatrixEasyMode does not require pgAdmin or Portainer to run.
They are optional operator conveniences for people who want a UI for database inspection or container management. The core MatrixEasyMode runtime remains:
- PostgreSQL
- Nginx Proxy Manager
- MatrixEasyMode API
- MatrixEasyMode web frontend
This section covers optional operator tooling that can be run alongside MatrixEasyMode.
These tools are not part of the core MatrixEasyMode application runtime. They exist to help serious operators inspect, diagnose, and manage parts of the environment more comfortably when needed.
For the main deployment path, start with:
What this section is for
Use the Tools section when you want optional UI-based support for operational tasks such as:
- inspecting PostgreSQL data and schema
- checking container state through a web interface
- doing light environment inspection during troubleshooting
- supplementing the normal shell-first operator workflow
These tools are helpful, but they are not required.
What this section is not for
This section is not the main MatrixEasyMode operating model.
The expected operator posture is still:
- use the helper scripts
- understand the staged startup model
- read logs directly
- review
.envdeliberately - treat ingress and certificates as real infrastructure concerns
In other words, pgAdmin and Portainer are conveniences, not substitutes for understanding the deployment.
Available tools
Optional pgAdmin
Use this when you want a browser-based interface for PostgreSQL.
Typical reasons include:
- checking database connectivity
- inspecting tables during troubleshooting
- verifying stored state more comfortably than through raw SQL shell access
Optional Portainer
Use this when you want a browser-based interface for Docker container and stack inspection.
Typical reasons include:
- checking container state visually
- reviewing logs in a UI
- inspecting volumes, networks, and containers during troubleshooting
Recommended posture
For most operators, the right order is:
- learn the standard install and ops workflow first
- use logs and helper scripts as the primary path
- add optional tools only if they genuinely help your workflow
That keeps the mental model clear.
Tooling philosophy
MatrixEasyMode is currently documented for operators who are comfortable with explicit infrastructure.
That means the project should still be understandable and operable without relying on heavy dashboards. Optional tools are there to help, not to hide the runtime model.