93ddd41621
* feat: add reverse proxy support * improve * improve * improve * improve * improve * fix: update integration test to use modern 'docker compose' command - Replace 'docker-compose' with 'docker compose' (Docker Compose v2+) - Add fallback to legacy docker-compose command for compatibility - Fixes test failures on systems using Docker Compose plugin * ci: trigger test rerun * fix: make docker-compose detection more robust for CI - Add get_docker_compose_command() to detect available command - Use shutil.which() to check command availability - Dynamically use correct command (docker compose vs docker-compose) - Should work in both modern and legacy Docker environments * fix: docker-compose networking in base path integration test Fix connection refused error in test_reverse_proxy_simple_config by handling host vs bridge networking modes correctly: - Linux (host mode): nginx listens on 18080 directly, no port mapping - Mac/Windows (bridge mode): nginx listens on 80, mapped to 18080 With host networking, port mappings in docker-compose don't work since the container binds directly to the host's network namespace.
18 lines
477 B
TypeScript
18 lines
477 B
TypeScript
import type { NextConfig } from "next";
|
|
import path from "path";
|
|
|
|
const basePath = process.env.NEXT_PUBLIC_BASE_PATH || '';
|
|
|
|
const nextConfig: NextConfig = {
|
|
output: 'standalone',
|
|
basePath: basePath,
|
|
assetPrefix: basePath,
|
|
// Disable request logging in production
|
|
logging: false,
|
|
// Set the monorepo root explicitly to avoid detecting wrong lockfiles in parent directories
|
|
turbopack: {
|
|
root: path.resolve(__dirname, '..'),
|
|
},
|
|
};
|
|
|
|
export default nextConfig;
|