Download the PHP package baconfy/core without Composer
On this page you can find all versions of the php package baconfy/core. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package core
The module system at the heart of the Baconfy ecosystem. It lets Composer packages register themselves as application modules — with a name, label, icon, entry route, navigation tree and visibility rules — so the application shell can discover and render them with zero configuration.
This package is pure PHP and has no opinion about your frontend. It is consumed by baconfy/interface, which turns registered modules into a launcher and sidebar.
Requirements
- PHP 8.3+
- Laravel 11, 12 or 13
Installation
The service provider is auto-discovered. A ModuleRegistry singleton becomes available in the container.
Creating a module
A module is a regular Laravel package whose service provider extends ModuleProvider. Three methods are required:
That's it. The module is registered automatically when the provider boots.
Your boot() stays yours
ModuleProvider does not touch the boot() method — registration happens through a provider booting callback. Write your boot exactly the way you would in any Laravel package:
Conventions
The module name is the universal key. By convention it is also:
| Concern | Convention | Override |
|---|---|---|
| Entry route | {name}.index |
routeName(): ?string |
| Visibility gate | gate named {name}, if defined |
can(): ?string |
| Launcher position | order = 100 |
order(): int |
| JS page namespace | extra.baconfy.module in composer.json |
— (must match name()) |
Visibility
Three rules, checked in order:
- Explicit
can()— the module is visible only to users allowed by that gate. - Convention gate — if a gate named after the module exists (
Gate::define('notes', ...)), it decides. The application controls access without the module knowing. - Otherwise — the module is public, including for guests.
Manifest validation
If the package's composer.json declares a Baconfy manifest, the module key must match the provider's name():
A mismatch throws ManifestMismatchException at boot — configuration errors die early and loudly. The manifest is optional: headless modules (no frontend pages) don't need one.
Navigation
Modules may expose a navigation tree by overriding navigation():
- Trees nest to any depth through
children()(accepts arrays or Collections). - Items with
can()are pruned for users who fail the gate — and for guests. - Route-less items act as group headings; a group whose children were all pruned disappears with them.
- Returning
null(the default) means the module has no sidebar navigation at all.
Lazy by design
label() and navigation() are never called during boot. They are wrapped in closures and evaluated only at serialization time, per request. This means:
- labels translate to the locale of the current request, not the boot locale;
- navigation may safely query the database without taxing every request;
- long-running runtimes (Octane) never freeze stale values.
Consuming the registry
Sharing modules with an Inertia frontend is a one-liner:
Each module serializes to:
url is null when the entry route doesn't exist; navigation is null when the module defines none.
Testing
The suite runs against PHP 8.3/8.4/8.5 × Laravel 11/12/13 in CI.
License
MIT.
