Function detect_from_config 

pub fn detect_from_config(project_root: &Path) -> Option<StackLabel>

Detect a stack label from configuration files in a project root.

The function scans only project_root and checks built-in rules in a fixed priority order. More specific frontend framework config files are evaluated before generic runtime markers such as Cargo.toml or go.mod. Python projects get a second pass that can identify Django, Flask, FastAPI, Starlette, and Litestar from entry files or dependency files. Ruby projects need Gemfile and config.ru (Ruby (Rack)), plus bin/rails for Rails. PHP projects with artisan next to composer.json are Laravel.

This function knows nothing about the process, so it uses the same rules StackDetector applies to an unknown process. Python entry files such as server.py alone do not make a Python project when package.json is present without a Python dependency file. The detector narrows the rules to the process’s ecosystem: a php process in a Laravel project with vite.config.js is Laravel, while a node process there is Vite.

Examples

use std::path::Path;
use what_stack::detect_from_config;

let label = detect_from_config(Path::new("/workspace/api"));
println!("{label:?}");

Performance

Directory entries are read once into a small in-memory set. Source and dependency files used for Python detection are capped to the first 64 KiB.