Weave Code
Communication Laravel Package
noerd/communication
noerd/communication is a Laravel package that adds a structured communication layer to your PHP applications, helping you organize messaging, notifications, and user-to-user interactions with clean, framework-friendly code.
At a glance
Frequently asked questions about Communication
- What is noerd/communication used for in a Laravel application?
- It is a Laravel package that adds a structured communication layer for organizing messaging, notifications, and user-to-user interactions with framework-friendly code. The package follows standard Laravel conventions: a registered service provider, artisan migrations, and database-backed configuration for marketing and communication settings plus mail senders. It fits most naturally into apps that already run php artisan migrate in their deployment pipeline.
- How do I install noerd/communication in a Laravel app?
- Install the package with Composer and let Laravel package discovery register its service provider, then run php artisan migrate. On a fresh application, v0.5.0 ships three consolidated final-schema migrations, so the full schema is created in a single pass. No separate configuration publishing step is described in the release notes, and settings are stored in the database rather than in config files.
- Which Laravel and PHP versions does noerd/communication support?
- The v0.5.0 release note does not state explicit Laravel or PHP version constraints. Before scheduling an upgrade, check the package's composer.json requirements against your application's framework and PHP versions. This is one of the open questions flagged in the technical assessment, so treat version support as unconfirmed until you verify it directly.
- How do I upgrade an existing Laravel app to noerd/communication v0.5.0?
- Treat the upgrade as a two-phase deployment rather than a single version bump. Pin your application to v0.4.12, back up the database, record the current migration state, deploy, and run php artisan migrate. Verify the upgrade-only migrations completed and data looks correct, then raise the dependency constraint to v0.5.0, deploy, and migrate again; the create migrations are skipped because their filenames are preserved.
- What breaking changes are in noerd/communication v0.5.0?
- v0.5.0 consolidates the schema into three final-schema migrations and removes the legacy redirect routes /sent-mails, /sent-mail/{id}, /marketing-settings, and /communication-settings. The schema change itself is not destructive, because existing create migration filenames are preserved and will not re-run after the v0.4.12 step. The package therefore owns fewer compatibility shims and expects your application to handle anything that depended on those routes.
- Why do /sent-mails and /marketing-settings return 404 after upgrading to v0.5.0?
- Those legacy redirect routes were removed in v0.5.0, so links or bookmarks pointing at them will no longer resolve. Audit your front-end links, email templates, tests, and any external integrations that reference them before deploying. If those URLs are exposed to users or third parties, add replacement routes or redirects at the application layer.
- Can I skip v0.4.12 and install noerd/communication v0.5.0 directly?
- You can, but the documented upgrade path requires installing v0.4.12 and running migrations first, so skipping it risks data loss. The upgrade-only migrations removed in v0.5.0 include the marketing rename, the SMTP move to mail senders, and column drops, which are exactly the transformations you would miss. This risk is low for greenfield installs and medium-to-high for existing installations on an older or unknown version.
- How are marketing settings and mail senders configured in noerd/communication?
- Marketing and communication settings and mail senders are stored in the database rather than in static config files. That means you configure them through the package's data layer after migrations have run, and the values travel with your database across deployments. Plan database seeding or a post-deploy configuration step if you need consistent sender settings across environments.
- Is there a rollback path if the noerd/communication upgrade fails?
- The v0.5.0 release note does not mention rollback support or data backfill verification. Because the consolidated migrations run in a single deployment, back up the database and record the migration state before you start so you can restore manually if something fails mid-deploy. Test the full two-phase upgrade against a staging copy of production data before touching a live environment.
- How do I verify the intermediate v0.4.12 migrations ran before upgrading to v0.5.0?
- The package does not document a migration-status or schema-verification command of its own, so rely on php artisan migrate:status and direct inspection of the tables. Confirm the marketing rename, the mail sender migration, and the column drops all completed and that the data looks correct. Recording that state before bumping the constraint to v0.5.0 gives you a clear baseline for troubleshooting.
Weaver
How can I help you explore Laravel packages today?