Download the PHP package nawasara/registry without Composer
On this page you can find all versions of the php package nawasara/registry. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.
Example:
Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.
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.
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 PHP packages are not free to download and because of that hosted in private repositories.
In this case some credentials are needed to access such packages.
Please use the auth.json textarea to insert credentials, if a package is coming from a private repository.
You can look here for more information.
- 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.
Please rate this library. Is it a good library?
Informations about the package registry
Nawasara Registry
Master data for the Nawasara superapp framework: organizational units (OPD), persons in charge (PIC), and a generic asset ownership index that other packages link into.
Features
- OPD — code, name, address, phone, email, and a list of related PIC contacts
- PIC (Person-in-Charge) — name, position, contact details, scoped to one OPD
- Asset — generic ownership record keyed by
(package_ref, external_id). Other packages (Cloudflare DNS, WHM Account, Email account) write here with their canonical IDs so the dashboard can render an "OPD / PIC" column on every resource list and a single OPD detail page can show every asset they own - Activity log — every write is captured via
spatie/laravel-activitylog - Admin pages — Livewire CRUD for OPD, PIC, and Asset with search, filter, and detail modals
Installation
Auto-discovered.
Asset linking pattern
Other packages create an asset row whenever they create a managed resource:
Resource list pages then look up the asset map in one query:
Pages
| Route | Permission |
|---|---|
/admin/registry/opd |
registry.opd.view |
/admin/registry/pic |
registry.pic.view |
/admin/registry/asset |
registry.asset.view |
Author
Pringgo J. Saputro <[email protected]>
License
MIT
All versions of registry with dependencies
PHP Build Version
Package Version
Requires
php Version
^8.1
illuminate/support Version ^10.0|^12.0
spatie/laravel-permission Version ^6.0
spatie/laravel-activitylog Version ^4.9
nawasara/ui Version *
livewire/livewire Version ^3.0
illuminate/support Version ^10.0|^12.0
spatie/laravel-permission Version ^6.0
spatie/laravel-activitylog Version ^4.9
nawasara/ui Version *
livewire/livewire Version ^3.0
The package nawasara/registry contains the following files
Loading the files please wait ...