Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/whitiue/logiMathApp/llms.txt

Use this file to discover all available pages before exploring further.

Most issues with LogiMath’s local setup fall into a small number of categories: Docker not installed or misconfigured, volume synchronisation problems, port conflicts, database connectivity errors, or display environment issues with the Flet frontend. The solutions below address each case directly.
Error:
docker: command not found
Docker is not installed or not on your PATH.Solution: Download and install Docker Desktop for your operating system. After installation, restart your terminal and verify:
docker --version
docker-compose --version
Both commands should return a version string. On Windows, ensure Docker Desktop is running in the system tray before issuing any docker commands.
Symptom: You edit a file in src/BackEnd/ or src/FrontEnd/ but the running container does not reflect the change.Solution: Tear down the stack including its volumes and rebuild from scratch:
docker-compose down -v
docker-compose up --build
The -v flag removes named volumes so stale data cannot mask new code. If the issue persists, clear Docker’s build cache:
docker system prune -a
docker-compose up --build
docker system prune -a removes all unused images, containers, and build cache across every project on your machine, not just LogiMath. Only run it if a targeted rebuild does not resolve the problem.
Error:
Error starting userland proxy: listen tcp4 0.0.0.0:5432: bind: address already in use
Another PostgreSQL instance is already listening on port 5432 on the host.Solution: Change the host port in docker-compose.yml. Open the file and update the postgres service’s ports mapping:
services:
  postgres:
    ports:
      - "5433:5432"   # host:container — change host port only
The internal container port must stay 5432. The DATABASE_URL in your .env file does not need to change — it uses the Docker service name postgres and the internal port:
DATABASE_URL=postgresql://logmath_user:logmath_pass_change_me_in_production@postgres:5432/logmath_db
Restart the stack after saving the file:
docker-compose down
docker-compose up --build
Error:
psycopg2.OperationalError: could not translate host name "postgres" to address: Name or service not known
or
psycopg2.OperationalError: connection refused
The backend container cannot reach the database.Solution: Work through these checks in order:
  1. Confirm all containers are running: 
    docker-compose ps
    The postgres service must show healthy. If it shows starting, wait 10–15 seconds and check again.
  2. Inspect the database logs for startup errors: 
    docker-compose logs postgres
  3. Verify DATABASE_URL in your .env file uses postgres (the Docker service name) as the host, not localhost: 
    grep DATABASE_URL .env
    The value must match the format from .env.example: 
    DATABASE_URL=postgresql://logmath_user:logmath_pass_change_me_in_production@postgres:5432/logmath_db
  4. If you changed any credentials in .env, make sure POSTGRES_USER, POSTGRES_PASSWORD, and POSTGRES_DB match the username, password, and database name in DATABASE_URL.
Error:
_tkinter.TclError: no display name and no $DISPLAY environment variable
or a similar DISPLAY not set message from Flet.Cause: Docker containers run headless (no display server), but Flet requires a graphical display to render the application window.Solution: Run the frontend directly on your host machine, outside of Docker:
cd src/FrontEnd
python -m venv venv
source venv/bin/activate    # Windows: venv\Scripts\activate
pip install -r requirements.txt
python mainApp.py
Keep the backend and database running with Docker Compose in a separate terminal. The frontend will connect to the backend at http://localhost:8000 as long as the API_HOST and API_PORT environment variables are set correctly.
Error:
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.
Your local machine does not have a valid SSH key registered with GitHub.Solution:
  1. Test your current SSH access: 
    ssh -T git@github.com
    A successful connection returns: Hi <username>! You've successfully authenticated...
  2. If the test fails, generate a new SSH key and add it to your GitHub account: 
    ssh-keygen -t ed25519 -C "your_email@example.com"
    Then copy the public key (~/.ssh/id_ed25519.pub) and add it in GitHub → Settings → SSH and GPG keys → New SSH key.
  3. Full instructions are in the GitHub SSH documentation.

Build docs developers (and LLMs) love

Get started for freeTalk to us