Weave Code
Framework Laravel Package
hubleto/framework
Hubleto Framework is a PHP framework for building business and enterprise applications, with an extensible module system, CRM/ERP-ready components, and a pragmatic foundation for rapid development of data-driven apps.
MVC-based framework for the Hubleto ERP | 🌟 Star if you like it!
Frequently asked questions about Framework
- What is hubleto/framework and is it a Laravel package?
- Hubleto Framework is a lightweight, open-source PHP framework for building data-driven business applications such as CRM and ERP systems. It provides a modular foundation for models, views, controllers, and reusable app components, along with rapid CRUD scaffolding and role-based access control. It is installable via Composer and can be used inside a Laravel application, but it is not a narrowly scoped Laravel utility. Its documentation and behaviour are defined by the upstream hubleto/erp repository, so treat it as an ERP-adjacent module set rather than a generic package.
- How do I install hubleto/framework with Composer?
- Install it with composer require hubleto/framework, pinning an exact version rather than a floating constraint so builds stay reproducible. Because the release notes defer to hubleto/erp, plan to run php artisan vendor:publish and php artisan migrate in a disposable environment to see what config, routes, and tables actually arrive. Commit the composer.lock and record the published assets, since these are not documented in the package itself.
- Which Laravel and PHP versions does hubleto/framework support?
- The package does not publish its own compatibility matrix; version floors are inherited from the upstream hubleto/erp 2.x dependency tree. You must inspect the upstream composer.json and run composer why and composer outdated against your pinned Laravel and PHP versions before assuming support. Watch for constraints expressed as dev-master or wildcard asterisks in the upstream package, which are a red flag for reproducibility.
- Is hubleto/framework 2.0.0-alpha3 production ready?
- No. It is a pre-release alpha with no stability guarantee, and its release note is a single line pointing to the hubleto/erp repository with no changelog, migration notes, or diff summary. Do not integrate it directly into a production Laravel application. The reliable approach is to stand up a sandbox environment, install the alpha, and produce your own changelog from what you observe.
- What changed between hubleto/framework 1.x and 2.0.0?
- That cannot be determined from the package artifact alone, because the only release note for 2.0.0-alpha3 refers you to hubleto/erp. A major version bump must be treated as breaking until proven otherwise, covering namespaces, service provider bindings, config keys, and database schema. If you are already on 1.x, plan the move as a re-integration project: branch, migrate a copy of the database, and diff behaviour before any cutover.
- Does Hubleto Framework include CRUD scaffolding and access control?
- Yes. The framework advertises rapid CRUD scaffolding for forms, grids, and records, an MVC structure that separates logic from presentation, and built-in user-role and access control support for business data. It also provides a modular architecture so features can be packaged as reusable apps, plus an extensible base for custom workflows and integrations. These are the core reasons teams building CRM or ERP style tools consider it.
- Does hubleto/framework ship database migrations, and how do I roll back?
- An ERP-shaped framework of this kind normally publishes migrations and expects to own database tables, so assume migrations are part of the install until you verify otherwise. Inspect the vendor:publish output in a sandbox and inventory every table, config key, route, and event it registers. Because rollback paths are not documented here, rely on database backups and a staged environment rather than assuming a clean artisan migrate:rollback will restore your schema.
- How does hubleto/framework relate to hubleto/erp?
- The framework is effectively a satellite release of hubleto/erp: its documentation, dependency constraints, and domain model all live upstream. Adopting it means adopting a slice of the Hubleto ERP domain model, including entities, ACL, UI widgets, and the module registry. That is a reasonable fit for teams already running Laravel who want ERP-adjacent building blocks, but a poor fit if you need an independently versioned, tightly scoped package.
- Is hubleto/framework an alternative to Laravel Nova or Filament?
- Not directly. Nova and Filament are admin panel and CRUD UI toolkits you layer onto an existing Laravel app, while Hubleto Framework is a broader business application framework with its own module registry, ACL, and ERP-style domain model. It brings more built-in structure for CRM and ERP workflows but also more coupling and a heavier dependency tree. Evaluate it against your architecture rather than treating it as a drop-in admin panel replacement.
- Who maintains hubleto/framework and how should I evaluate releases?
- Maintenance, release cadence, and security disclosure channels are not documented in the package and must be confirmed by reviewing the upstream hubleto/erp repository. Before committing, run a spike in a throwaway Laravel environment: install the alpha, publish assets, migrate, and inventory schema, config, routes, and events. Then write an internal upgrade note to replace the empty release note, pin an exact version, and keep the ERP integration behind a dedicated module boundary rather than spreading calls through existing domain code.
Weaver
How can I help you explore Laravel packages today?