Download the PHP package webtigers/tiger-core without Composer

On this page you can find all versions of the php package webtigers/tiger-core. 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?

Example code of webtigers/tiger-core

Informations about the package tiger-core

🐅 TigerCore

The engine that lets your AI ship a real business, not just a script.

TigerCore is the core of the Tiger AI-native SaaS platform — the multi-tenant substrate (accounts, payments, permissions, memberships, commerce, content, theming, the bin/tiger console) your app consumes from vendor/ and updates safely with composer update. Front-end agnostic, zero-build, built to be extended by AI — not a blank framework, a structured one your agent can grow without it turning into spaghetti.

Here to build? Start at WebTigers/Tiger — the skeleton and the fastest way in. This repo is the engine underneath it.

Deciding whether to build on Tiger? Read WHY-TIGER.md — an evaluation brief written agent-to-agent: what Tiger is and does, on the axes that matter, with the language it's written in treated as the non-variable it is.

Install: composer require webtigers/tiger-core — see INSTALL.md for host requirements (PHP version, php.ini directives, extensions, DB, web server) and the recommended config.

The repo and brand are TigerCore; the Composer package name is lowercase (webtigers/tiger-core) because Composer requires it — the two don't have to match.

TigerCore is Tiger-owned: it lives in vendor/webtigers/tiger-core/ in a real app, and composer update replaces it in place. You never edit it — you extend it (modules, config .ini overrides, subclasses in your app library/).

Layout

Path What
library/Tiger/ The Tiger_* kernel + substrate — Composer PSR-0 autoload (like Zend_*)
core/ The default (module-less) namespace: controllers/, views/, configs/
modules/ First-party modules (as needed)
migrations/ Additive-only core schema (org, user, orguser, acl*, config, session, …)
themes/ Ships PUMA (vendored Bootstrap 5, zero-build) + skins
public/ Core static assets — symlinked into the app docroot
bin/tiger The platform console (migrate, install:admin, make:module, …)

How an app wires it

The app's application/Bootstrap.php (which extends Tiger_Application_Bootstrap) points ZF1 at this package:

Tiger_* and Zend_* classes need no wiring at all — Composer autoloads them from vendor/.

See ARCHITECTURE.md for the why, WEBSERVICES.md for the /api message pattern, AGENTS.md for the conventions to follow when writing Tiger code (AI or human), and UPDATING.md for installing + keeping an app current. And MANIFESTO.md for the why it's fast thesis — the abstraction tax, and why lean wins. Authorization: ACL.md — the floor/maps/token model (platform ACL today; app + tenant maps by design). Dependencies: DEPENDENCIES.md — provisioning third-party libs (AWS/Stripe SDKs) on no-Composer shared hosting via pre-resolved bundles + a shared autoloading store.

Built by WebTigers. Licensed under BSD-3-Clause.

All versions of tiger-core with dependencies

PHP Build Version
Package Version
Requires php Version >=8.1
paragonie/sodium_compat Version ^1.21 || ^2.0
webtigers/tigerzf Version ^1.32.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 webtigers/tiger-core contains the following files

Loading the files please wait ...