Skip to content

feat: env-configurable plugin loading and home-manager plugin settings#623

Open
connor-grady wants to merge 3 commits into
rynfar:mainfrom
connor-grady:feat/plugin-env-config
Open

feat: env-configurable plugin loading and home-manager plugin settings#623
connor-grady wants to merge 3 commits into
rynfar:mainfrom
connor-grady:feat/plugin-env-config

Conversation

@connor-grady

Copy link
Copy Markdown
Contributor

ProxyConfig.pluginDir and pluginConfigPath were only settable through the embedded createProxyServer API — the CLI never read them, so a standalone meridian process always used the fixed ~/.config/meridian/plugins/ and ~/.config/meridian/plugins.json. bin/cli.ts now reads MERIDIAN_PLUGIN_DIR and MERIDIAN_PLUGIN_CONFIG and forwards them into startProxyServer (documented in --help), so both paths are configurable for the standalone proxy.

The home-manager module gains two settings. services.meridian.settings.pluginConfig takes a list of { path, enabled } submodules and renders them, in order, to a plugins.json manifest in the Nix store (via pkgs.formats.json), passed as MERIDIAN_PLUGIN_CONFIG. services.meridian.settings.pluginDir maps to MERIDIAN_PLUGIN_DIR. The service Environment now derives each MERIDIAN_* variable name automatically from its settings attribute path, so new settings are exported without a hand-maintained key mapping.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant