Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Kevin2523/nextAuditAi/llms.txt

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

NextAudit AI ships three Docker Compose files, each tuned to a different stage of the software lifecycle. All three start the same set of services—Ollama, PostgreSQL, Flowise, n8n, MySQL, Redis, and Fleet—but they differ in how images are sourced and how strictly they mirror a production-grade configuration.

​
Environments at a glance

Compose fileImage sourceIntended use
docker-compose.dev.ymlLocal build: context for Ollama and PostgreSQLActive development and local iteration
docker-compose.test.ymlVersioned images from jjsotom2k4/ registryIntegration testing against a fixed image set
docker-compose.prod.ymlVersioned images from jjsotom2k4/ registryProduction deployments

​
Development vs. test and production

The key architectural difference between environments is how the Ollama and PostgreSQL containers are created. Development (docker-compose.dev.yml) uses build: directives that compile images from the local source tree: 
ollama:
  build:
    context: ./ollama

postgres:
  build: ./postgres
This lets you iterate on the AI model configuration and database schema without publishing new images. Test and production (docker-compose.test.yml, docker-compose.prod.yml) pull versioned images from the jjsotom2k4/ registry. Both files are structurally identical—the distinction is operational (test environments are ephemeral; production environments are persistent). 
ollama:
  image: jjsotom2k4/ollama-ai:${VERSION}

postgres:
  image: jjsotom2k4/postgres-ai:${VERSION}
The VERSION environment variable pins every deployment to a specific, reproducible release.

​
Prerequisites

Before starting any environment you need:
  • Docker 24.0 or later
  • Docker Compose v2 (the docker compose plugin, not the legacy docker-compose binary)

​
Branch structure

The repository uses three long-lived branches that map to the environments above:
  • main — stable baseline: README, .gitignore, and the core Compose files.
  • develop — active development branch where new features land first.
  • docs — technical documentation, manuals, and operational guides.

​
Where to go next

Development environment

Run the full stack locally with hot-buildable images.

Production deployment

Deploy with versioned images and production-hardened settings.

Build docs developers (and LLMs) love

Get started for freeTalk to us