Upgrading & Migration
Short guide to upgrading Faramesh and migrating between configurations.
Moving from YAML policies to database policies
If you previously used file-based YAML policies (e.g. engine_v2.yaml or policy packs):
Export or copy your existing YAML rules.
In the Policies page in the dashboard, open the policy editor and paste or import the YAML (if your deployment supports import). Alternatively, re-create the rules in the editor.
Validate with
faramesh policy validate(against the API) or the in-dashboard validator.Remove or disable file-based policy loading in your server config so the engine uses the database as the source of truth.
See Database-Backed Policies for editor usage and Policy Reference for rule syntax.
Version upgrades (self-hosted)
Back up your database and any mounted policy/config files before upgrading.
Check release notes for breaking changes, new env vars, and schema migrations.
Run migrations if the release includes DB changes (e.g. Alembic or project-specific migration commands).
Restart services after upgrading binaries and config.
Horizon (managed)
Horizon is updated by the Faramesh team. API and behavior changes are documented in release notes and in this docs site. If you rely on a specific API shape or feature, check the changelog before upgrading your client or SDK.