Debugging Mathesar¶
Not for production
Debug mode should not be enabled in production environments, where it can cause performance issues and potentially expose sensitive information.
If your Mathesar installation isn’t working as expected, you can prefix the docker command with DEBUG=true to add additional debugging output to the console and more verbose errors in the browser when something goes wrong. The additional information logged should help you or the Mathesar team diagnose any installation issues.
With Docker Compose¶
When debugging Mathesar’s recommended docker compose installation method, add DEBUG=true to the beginning of the docker compose command:
With the basic Mathesar docker image¶
If you are just trying the Mathesar Docker image directly as instructed in the introduction, you will follow the same approach of setting DEBUG=true:
- docker run -it --name mathesar -p 8000:8000 mathesar/mathesar:latest
+ DEBUG=true docker run -it --name mathesar -p 8000:8000 mathesar/mathesar:latest
Before version 0.2.1¶
Previous versions of Mathesar used a dedicated debugging image called mathesar/mathesar-debug. These images will not be supported or created for Mathesar versions 0.2.1 or higher.