plano/config
Adil Hafeez 9cd764fc3e separate config generation from process startup in supervisord
Extract config generation (planoai.config_generator + envsubst) into its own
supervisord program that runs first. Brightstaff and envoy wait for a sentinel
file before starting. If any critical process exits, supervisord is terminated
so the container restarts cleanly.

Made-with: Cursor
2026-03-19 22:18:10 -07:00
..
docker-compose.dev.yaml Overhaul demos directory: cleanup, restructure, and standardize configs (#760) 2026-02-17 03:09:28 -08:00
env.list restructure cli (#656) 2025-12-25 14:55:29 -08:00
envoy.template.yaml Unified overrides for custom router and orchestrator models (#820) 2026-03-15 09:36:11 -07:00
plano_config_schema.yaml add output filter chain (#822) 2026-03-18 17:58:20 -07:00
README.md Adding support for wildcard models in the model_providers config (#696) 2026-01-28 17:47:33 -08:00
requirements.txt restructure cli (#656) 2025-12-25 14:55:29 -08:00
supervisord.conf separate config generation from process startup in supervisord 2026-03-19 22:18:10 -07:00
test_passthrough.yaml Run plano natively by default (#744) 2026-03-05 07:35:25 -08:00
validate_plano_config.sh Run plano natively by default (#744) 2026-03-05 07:35:25 -08:00

Envoy filter code for gateway

Add toolchain

$ rustup target add wasm32-wasip1

Building

$ cargo build --target wasm32-wasip1 --release

Testing

$ cargo test

Local development

  • Build docker image for Plano. Note this needs to be built once.

    $ sh build_filter_image.sh
    
  • Build filter binary,

    $ cargo build --target wasm32-wasip1 --release
    
  • Start envoy with config.yaml and test,

    $ docker compose -f docker-compose.dev.yaml up plano
    
  • dev version of docker-compose file uses following files that are mounted inside the container. That means no docker rebuild is needed if any of these files change. Just restart the container and chagne will be picked up,

    • envoy.template.yaml
    • intelligent_prompt_gateway.wasm