Download the PHP package buzztech/boi-backend without Composer
On this page you can find all versions of the php package buzztech/boi-backend. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download buzztech/boi-backend
More information about buzztech/boi-backend
Files in buzztech/boi-backend
Package boi-backend
Short Description BOI Laravel backend package
License MIT
Homepage https://github.com/BuzzTechnics/boi-backend
Informations about the package boi-backend
boi-backend
Composer package shared by BOI Laravel apps (Glow, portals, …).
Full integration guide: see doc/README.md (package vs app, database connection, shared models, Nova & policies).
boi-api HTTP proxy (plug & play)
Forwards browser calls to your app’s /api/boi-api/{path} to BOI_API_URL with server-only BOI_API_KEY and headers X-Boi-User / X-Boi-App.
composer require buzztech/boi-backend(already auto-discoversBoiBackendServiceProvider).- Set
.env:BOI_API_URL,BOI_API_KEY,BOI_APP(slug, e.g.glow), optionalBOI_USER_HEADER/BOI_APP_HEADER. -
In
routes/web.php(inside yourauth+verifiedgroup): - Loan applications: for paths
api/loan-applications/{id}/…, the proxy checksApp\Models\Applicationexists anduser_idmatches the logged-in user (same convention for all BOI apps).
Publish full defaults: php artisan vendor:publish --tag=boi-backend-proxy
Other features
- Contracts:
StatementDataProviderInterface,StatementUpdaterInterface(implemented by the deployed boi-api service or tests). - PaystackBanks (
Boi\Backend\Support\PaystackBanks): sync bank list + short names into yourBankmodel (used by seeders). Boi\Backend\Models\Bank:bankson connectionboi_api(BOI_DB_*). boi-api can keepApp\Models\Bankviaconfig/banks.php.
EDOC / bank-statement API live in boi-api.
Installation
Optional publish tags: boi-backend-config (banks.php), boi-backend-boi-api (boi_api.php), boi-backend-proxy (boi_proxy.php).
Laravel Nova, factories, seeders
See doc/ — Nova resources and Gate::policy are per app; factories/seeders live in the package.
Development
Releasing (buzztech/boi-backend)
- Merge changes to
mainand ensurecomposer testpasses. -
Tag a semver release (Composer / Packagist use the tag, not a
versionfield incomposer.json): - Packagist (optional): submit
https://github.com/BuzzTechnics/boi-backendonce; future tags are picked up automatically. -
Consumers (e.g.
boi-api): require"buzztech/boi-backend": "^0.2@dev"whilemaintracks the next minor (@devallows the0.2.x-devalias; withprefer-stable, Composer prefers the latestv0.2.xtag). For stable-only installs after tags exist, use"^0.2". Add a VCS repository only if the package is not on Packagist:If
../boi-backendexists as a sibling checkout, a path repository (as inboi-api) keeps local development on a symlinked copy.
All versions of boi-backend with dependencies
brick/math Version ^0.12|^0.13|^0.14|^0.15|^0.16|^0.17
illuminate/console Version ^11.0|^12.0|^13.0
illuminate/database Version ^11.0|^12.0|^13.0
illuminate/filesystem Version ^11.0|^12.0|^13.0
illuminate/http Version ^11.0|^12.0|^13.0
illuminate/routing Version ^11.0|^12.0|^13.0
illuminate/support Version ^11.0|^12.0|^13.0