Skip to content

[DOCS]:Align LawGPT setup instructions with current Docker deployment topology #1348

@cosmoqain459

Description

@cosmoqain459

Description

Problem

The repository documentation and deployment configuration appear to describe different service topologies for the AI components.

Documentation

Several setup and testing guides describe LawGPT as a standalone service running on port 8000 and include instructions for starting and interacting with that service.

Deployment Configuration

The current docker-compose.yml defines:

  • PostgreSQL database
  • Spring Boot backend
  • NLP Orchestrator (backend-python) on port 8001
  • React frontend

However, no LawGPT service is defined in the Docker deployment configuration.

Impact

This can create confusion for new contributors because:

  • Setup guides reference a service that is not started through Docker Compose.
  • Contributors may attempt to run additional services that are not part of the documented deployment workflow.
  • The documented architecture may not accurately reflect the currently supported deployment topology.

Suggested Investigation

Review whether:

  • LawGPT is still intended to run as a standalone service.
  • LawGPT functionality has been consolidated into the NLP Orchestrator.
  • Documentation should be updated to reflect the current architecture.
  • Docker Compose should include the LawGPT service if it is still required.

Expected Outcome

Documentation and deployment configuration should describe the same architecture so contributors can follow setup instructions without ambiguity.

URL

No response

Proposed Changes

Proposed Changes

  • Review current AI service architecture.
  • Verify whether lawgpt-service is still required for local development.
  • Update CONTRIBUTING.md setup instructions if the service is no longer part of the recommended workflow.
  • Update architecture diagrams and service topology descriptions.
  • Update API testing documentation to reflect the current deployment model.
  • Remove references to obsolete ports or startup steps if they are no longer required.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions