ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how Liquibase contexts let you tag changesets and run only those matching a supplied --contexts argument, with a concrete XML example, verification steps, and common pitfalls.
Learn how to design a secure, centralized secret strategy with CircleCI contexts—requirement-driven, operationally checked, and failure-mode aware. Use one context per trust domain, audit usage, and rotate secrets on schedule.
Configure MODX 3.x to run multiple independent websites from one installation using Contexts, with isolated resource trees, settings and ACLs per domain.
CircleCI Contexts let multiple repositories share a deploy credential without duplicating it in project settings. Use one context per trust tier, restrict project access, and verify fail-closed behavior.
MODX Revolution uses Contexts as its multi-tenancy primitive—one installation, multiple isolated sites. This architecture note covers the minimal viable design, trust boundaries, operational verification, failure modes, and the triggers that force a move to separate installations.
MODX contexts let one core serve multiple sites, but they share a database, manager, and codebase. This guide covers the minimal design, routing pitfalls, trust boundaries, ACL patterns, cache issues, and conditions that signal you need separate installations instead.
Learn how Liquibase contexts let you maintain a single changelog while applying environment‑specific changesets safely, with a concrete example, verification steps, and trade‑offs.
Deploy multiple sites on a single MODX install using Contexts. Learn the minimal design, trust boundaries, operational checks, failure modes, and when you need a separate instance.
Learn when to use Liquibase contexts or labels, see a side‑by‑side comparison, and follow a concrete example to validate your choice.
circleci
liquibase