Weave Code
Activity Stream Bundle Laravel Package
sipsynergy/activity-stream-bundle
A Symfony bundle for creating and managing activity streams, with support for feed entries, actors, objects, and verbs. Integrates Activity Streams concepts into your app for social or event-driven feeds.
At a glance
Frequently asked questions about Activity Stream Bundle
- What is sipsynergy/activity-stream-bundle used for?
- sipsynergy/activity-stream-bundle is a Symfony bundle for creating and managing activity streams, modelling feed entries along with actors, objects, and verbs. It brings Activity Streams vocabulary into your application so you can build social feeds or event-driven timelines without inventing your own data structures. Check the repository README for the exact service names, classes, and configuration keys it exposes.
- Is sipsynergy/activity-stream-bundle compatible with Laravel?
- No, it is published as a Symfony bundle, so it registers through Symfony's bundle and dependency injection system rather than a Laravel service provider. Using it in Laravel would require a custom bridge or manual wiring of its classes, which is usually more effort than it is worth. Laravel projects are generally better served by a Laravel-native activity stream or audit log package.
- How do I install sipsynergy/activity-stream-bundle with Composer?
- Install it with composer require sipsynergy/activity-stream-bundle from your project root. After installation, enable the bundle in your Symfony application's bundle configuration. Before running the command, confirm the PHP and Symfony version constraints in the package's composer.json so Composer does not resolve an incompatible release.
- How do I register and configure the bundle in a Symfony application?
- On Symfony Flex applications, add the bundle class to config/bundles.php; on older versions, register it inside AppKernel::registerBundles(). Once registered, its services should be available for autowiring or for retrieval from the container. Review the README for any required configuration files, parameters, or environment variables before writing feature code.
- What are actors, objects, and verbs in an activity stream?
- In Activity Streams, the actor is the entity performing an action, the verb describes what happened such as post, follow, or like, and the object is the thing the action targets. The bundle treats these as first-class concepts so every entry has a consistent, serializable shape. That consistency is what lets you render many different feed item types through a single template or API response.
- How do I create a feed entry with this bundle?
- You typically build an entry by combining an actor, a verb, and an object, then passing it to the bundle's feed or entry service for storage or rendering. The precise class names and method signatures are documented in the repository README rather than in the package blurb. A good first step is creating one hard-coded entry in a controller to confirm the wiring before adding persistence.
- Can I use it to build a social feed or notification timeline?
- Yes, social feeds, activity timelines, and event-driven streams are the intended use cases, since different item types share the actor-verb-object structure. Because entries are uniform, you can persist events and replay them into a chronological feed. For notification delivery such as email or push, you will still need your own transport layer on top of the stream.
- Which Symfony and PHP versions does the bundle support?
- The provided package context does not list supported Symfony or PHP versions, so treat composer.json in the repository as the authoritative source. Bundle registration and directory conventions differ across Symfony major versions, so verify compatibility against the version you actually run. If your project is on a recent Symfony release, confirm there is a tagged bundle release that matches it.
- How should I test activity stream functionality in my application?
- Start with unit tests that build entries and assert the expected actor, verb, and object values, since the bundle is largely about structured data. Then use Symfony's test container to fetch the bundle services and confirm they are wired correctly. A small functional test that renders a feed will catch configuration and templating regressions early.
- Is the bundle actively maintained, and what should I check before using it in production?
- The supplied context includes no release history, so review the repository's commit activity, open issues, and latest tagged release before depending on it. Because it is a smaller vendor bundle, pin an explicit version in composer.json and confirm its Symfony constraints track the framework version you deploy. Also plan how feed entries will be persisted, indexed, and pruned, since stream tables grow quickly in production.
Weaver
How can I help you explore Laravel packages today?