PHPackages hexis-hr/deployer-fanfare - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [DevOps & Deployment](/categories/devops) 4. / 5. hexis-hr/deployer-fanfare ActiveLibrary[DevOps & Deployment](/categories/devops) hexis-hr/deployer-fanfare ========================= Rich Block Kit Slack deploy notifications for Deployer — environment, commit list, and ticket summary linked to your issue tracker. v0.1.1(1mo ago)0150↑33.3%Apache-2.0PHPPHP >=8.1 Since Apr 28Pushed 1mo agoCompare [ Source](https://github.com/hexis-hr/deployer-fanfare)[ Packagist](https://packagist.org/packages/hexis-hr/deployer-fanfare)[ RSS](/packages/hexis-hr-deployer-fanfare/feed)WikiDiscussions master Synced 1w ago READMEChangelogDependencies (1)Versions (3)Used By (0) deployer-fanfare ================ [](#deployer-fanfare) Rich [Block Kit](https://api.slack.com/block-kit) Slack notifications for [Deployer](https://deployer.org/) — environment, commit list, and ticket summary linked to your issue tracker. ``` ✅ Deploy successful Application: widget Environment: web-prod-1 Branch: main ← linked to GitHub Deployer: Ada Lovelace (ada@acme.io) Old commit: a1b2c3d4 ← linked Deployed commit: e5f6a7b8 ← linked ──────────────────────────────────────── TICKET SUMMARY • ROS-9 feat(security): 30-day sessions for users… ← linked to YouTrack/Jira/… • ROS-2 fix(users): prevent duplicate employee creation… ──────────────────────────────────────── COMMITS (5) • e5f6a7b8 fix(users): prevent duplicate employee creation… • 70b695f7 feat(security): 30-day sessions for users… • … ``` Failure variant gets a red `:x:` header; redeploys with no new commits get a `:neutral_face: Nothing new deployed` empty state instead of a confusing green "successful". Install ------- [](#install) ``` composer require --dev hexis-hr/deployer-fanfare ``` Wire it up ---------- [](#wire-it-up) In your `deploy.php`: ``` require 'recipe/symfony.php'; require __DIR__ . '/vendor/hexis-hr/deployer-fanfare/recipe.php'; set('repository', 'git@github.com:acme/widget.git'); set('fanfare_webhook', 'https://hooks.slack.com/services/…'); set('fanfare_issue_url_template', 'https://acme.atlassian.net/browse/{key}'); before('deploy:update_code', 'fanfare:revision'); after('deploy:success', 'fanfare:notify'); after('deploy:failed', 'fanfare:notify:failure'); ``` `fanfare_webhook` falls back to `slack_webhook` if you already have it set, so dropping the recipe into a project that uses the Deployer `contrib/slack.php` recipe works without renaming. Settings -------- [](#settings) SettingDefaultPurpose`fanfare_webhook`falls back to `slack_webhook`Slack incoming webhook URL. Required.`fanfare_channel``false` (use webhook default)Override channel; e.g. `'#deploys'`.`fanfare_issue_url_template``''` (no linking)Issue URL with `{key}` placeholder. See [examples](#issue-url-template-examples).`fanfare_ticket_pattern``/\b([A-Z][A-Z0-9]{1,9}-\d+)\b/`Regex extracting ticket keys from commit subjects. Capture group 1 is the key.`fanfare_commit_cap``30`Commits beyond this collapse to `… and N more`.`fanfare_emoji_success``:white_check_mark:`Header emoji on success.`fanfare_emoji_failure``:x:`Header emoji on failure.`fanfare_emoji_empty``:neutral_face:`Header emoji when redeploy has no new commits.`fanfare_header_success``Deploy successful`Header text on success.`fanfare_header_failure``Deploy FAILED`Header text on failure.`fanfare_header_empty``Nothing new deployed`Header text on no-op redeploy.`fanfare_github_repo_url`derived from `repository`Auto-detected GitHub web URL; commit/branch links are skipped if `repository` is not a GitHub remote.### Issue-URL template examples [](#issue-url-template-examples) ``` // YouTrack set('fanfare_issue_url_template', 'https://youtrack.example.com/issue/{key}'); // Jira Cloud set('fanfare_issue_url_template', 'https://acme.atlassian.net/browse/{key}'); // Linear set('fanfare_issue_url_template', 'https://linear.app/acme/issue/{key}'); // GitHub Issues — adjust the regex to match #123 instead of ROS-9 set('fanfare_issue_url_template', 'https://github.com/acme/widget/issues/{key}'); set('fanfare_ticket_pattern', '/#(\d+)/'); ``` Tasks ----- [](#tasks) TaskHook it viaVisibility`fanfare:revision``before('deploy:update_code', 'fanfare:revision')`hidden`fanfare:notify``after('deploy:success', 'fanfare:notify')`listed`fanfare:notify:failure``after('deploy:failed', 'fanfare:notify:failure')`listed`fanfare:revision` reads the previous deploy's `REVISION` file under `current/` so the recipe can compute the commit diff after a successful release. State is keyed by host alias, so concurrent multi-host deploys do not stomp on each other. How the diff works ------------------ [](#how-the-diff-works) 1. `fanfare:revision` (before `deploy:update_code`) reads `{{deploy_path}}/current/REVISION` — that's the previous deploy's HEAD. Empty on first deploy. 2. `fanfare:notify` (after `deploy:success`) reads the new `{{current_path}}/REVISION`, then runs `git log ..` against the cached deploy repo at `{{deploy_path}}/.dep/repo`. The result is parsed line-by-line using `\x1f` (ASCII unit-separator) as the field delimiter so commit subjects containing `|` aren't truncated. If `previous` is empty (first deploy) or equals `new` (no-op redeploy), the empty-state header is shown instead. Robustness ---------- [](#robustness) - Local `git config user.name` / `user.email` failures fall back to `unknown` — won't crash the deploy. - The Slack POST is wrapped in `try/catch`; webhook failures emit a Deployer warning but the deploy continues. - A plain-text `text` fallback ships alongside every `blocks` payload (Slack a11y requirement). - `fanfare:notify` and `fanfare:notify:failure` are marked `->once()` so multi-host deploys send a single roll-up message rather than one per host. License ------- [](#license) Apache-2.0. See [LICENSE](LICENSE). ### Health Score 38 — LowBetter than 83% of packages Maintenance91 Actively maintained with recent releases Popularity15 Limited adoption so far Community6 Small or concentrated contributor base Maturity33 Early-stage or recently created project Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~0 days Total 2 Last Release 42d ago ### Community Maintainers ![](https://avatars.githubusercontent.com/u/1439958?v=4)[Sinisa Valentic](/maintainers/tic984)[@tic984](https://github.com/tic984) --- Top Contributors [![tic984](https://avatars.githubusercontent.com/u/1439958?v=4)](https://github.com/tic984 "tic984 (3 commits)") --- Tags notificationsslackdeploydeployerblock-kit ### Embed Badge ![Health badge](/badges/hexis-hr-deployer-fanfare/health.svg) ``` [![Health](https://phpackages.com/badges/hexis-hr-deployer-fanfare/health.svg)](https://phpackages.com/packages/hexis-hr-deployer-fanfare) ``` ### Alternatives [easycorp/easy-deploy-bundle The easiest way to deploy Symfony applications 469312.2k](/packages/easycorp-easy-deploy-bundle)[jalogut/magento2-deployer-plus Magento 2 deployment tool based on deployer.org 201439.0k](/packages/jalogut-magento2-deployer-plus)[ngmy/webloyer Webloyer is a Web UI for managing Deployer deployments 2191.1k](/packages/ngmy-webloyer)[rafaelstz/deployer-magento2 Magento 2 deployment tool based on deployer.org 5223.8k](/packages/rafaelstz-deployer-magento2) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)