Download the PHP package wayaans/tyanc without Composer

On this page you can find all versions of the php package wayaans/tyanc. 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:
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.
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 tyanc

Tyanc

Tyanc is the admin foundation you install before the real apps arrive.

It gives you the platform pieces that serious products always end up needing anyway: authentication, users, roles, permissions, app access, page access, settings, approvals, notifications, files, and the shared admin shell.

tyanc is the control plane. cumpu is the approval workspace. Apps like ERP or Tasks plug in beside them under their own prefixes.

Why Tyanc exists

Tyanc is not a one-off dashboard for one product.

It is the shared platform layer for many apps. That means the cross-app rules stay in one place while each business app keeps its own routes, pages, actions, and UI.

In practice, Tyanc is where you keep things such as:

What lives where

Keep this mental model simple:

If a feature belongs to ERP, build it in ERP. If it governs ERP access, registration, or permissions, build it in Tyanc. If it is about reviewing or managing approvals, build it in Cumpu.

What you get out of the box

Tyanc is built around:

The one thing not to forget when adding a new app

Permissions are part of the app, not follow-up work.

When you add a real app such as erp or tasks, keep these in sync from the start:

  1. the app key
  2. the route prefix
  3. the permission namespace
  4. config/permission-sot.php
  5. config/sidebar-menu.php
  6. the app registry in apps and app_pages

A new app is not really done if routes exist but permissions do not. That mismatch breaks access control, app visibility, page visibility, and approval-rule options.

Practical checklist for a new app

If you introduce a new action verb like publish, cancel, or submit, add it to the top-level action map in config/permission-sot.php too.

How approvals work now

Tyanc uses a simpler approval model now.

Approval is a gate-and-grant flow:

The important part is this: approval attaches to the real action permission. If erp.orders.delete needs approval, the governed action is still erp.orders.delete. It is not a fake approval resource. Cumpu handles the review workflow, but the business app still owns the real mutation.

Install as a Laravel starter kit

After publishing wayaans/tyanc to Packagist, use the Laravel installer:

Or install it directly with Composer:

The starter kit install scripts copy .env, generate the app key, create the SQLite database, run migrations, and run php artisan tyanc:bootstrap-local --no-interaction.

Develop this repository directly

composer setup already runs the local Tyanc bootstrap, so you do not need a separate composer bootstrap:local step.

Production bootstrap

If you also need Reverb locally, run:

If a frontend change does not show up, make sure Vite is running or rebuild the frontend.

Read this next

If you are working with AI agents in this repo, start with TYANC-AI.md first.


All versions of tyanc with dependencies

PHP Build Version
Package Version
Requires php Version ^8.5.0
dompdf/dompdf Version ^3.1.5
inertiajs/inertia-laravel Version ^3.0.0-beta
laravel/fortify Version ^1.36.2
laravel/framework Version ^13.4.0
laravel/reverb Version ^1.10
laravel/wayfinder Version ^0.1.16
maatwebsite/excel Version ^3.1.68
nunomaduro/essentials Version ^1.2.0
spatie/laravel-activitylog Version ^5.0
spatie/laravel-data Version ^4.21
spatie/laravel-medialibrary Version ^11.21
spatie/laravel-pdf Version ^2.6
spatie/laravel-permission Version ^7.3
spatie/laravel-query-builder Version ^7.2
spatie/laravel-settings Version ^3.7.2
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package wayaans/tyanc contains the following files

Loading the files please wait ...