Download the PHP package ixaya/manager without Composer

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

Manager — by Ixaya

HMVC CodeIgniter 3 based Framework for creating backends

About this package

Ixaya Manager extends CodeIgniter 3 with HMVC module loading, a typed base model, a REST framework with API-key auth, and a cross-engine migration builder.

The framework is always consumed as a Composer dependency: your project bootstraps once from the included scaffold, and from then on the framework lives in vendor/ixaya/manager and upgrades with composer update. Framework code is never copied into or edited inside a project — see docs/development/upgrading.md in your project to learn how to update your project's files after an upgrade.

Features


How to Install

This is the quick version. If you want a more in depth guide follow system/docs/setup.md instead, which covers this setup in full.

Requirements

1. Install via Composer

2. Scaffold your project (one time)

Copy the sample application structure from the package into your project root. This is a one-time bootstrap — it copies your application's starting structure (controllers, models, views, config, and entry points), not the framework itself:

This gives you a complete working structure — controllers, models, views, config, and entry points — ready to customize. The sample ships composer.json.sample, a template, so this never overwrites your own composer.json; integrate its require-dev block into yours, then run composer update (not install).

3. Configure environment

Open both files and fill in the required fields:

Suggested packages

Depending on the features you need, install one or more of the following:

Optional — core extensions:

Optional — WebSocket server:


Agent skills

The package ships its coding conventions as agent skills (open SKILL.md format, usable by any coding agent) in system/skills/. They cover the whole development surface — code style, database models, REST endpoints and auth, web controllers and theming, migrations, CLI and background jobs, helpers and libraries, caching and WebSockets, and live runtime testing — and each skill describes when to use it. The scaffold's AGENTS.md carries the per-skill routing table for agents working in your project.

Link them into your project (run from the project root; re-run after major framework updates):

Project-wide agent instructions belong in your project's AGENTS.md (the cross-tool standard); tools that read CLAUDE.md can use a one-line @AGENTS.md import.


PHP Validations

PHP Static Code Analysis

Run using PHPStan:

First time, install PHPStan:

Standard analysis:

With increased memory limit:

Tip: Use the memory limit option if you encounter out-of-memory errors during analysis.

PHP Unit Testing

Run using PHPUnit. For DB-backed suites, copy .env.sample.testing.priv to .env.testing.priv and fill in a DB profile first — review your project's documentation for the full setup.

First time, install PHPUnit:

Run all tests:

Run one testsuite (as named in phpunit.xml):

Run a specific test file (absolute path — the framework's CLI boot changes the working directory, so relative file arguments don't resolve):

Run tests matching a class or method name:

Tip: Use --testdox flag for readable test output, or --stop-on-failure to halt execution on the first failed test. Note: Run it through the docker tools service — see docs/development/docker.md. This is the supported path regardless of what's installed on the host.

PHP Code Formatting

Fix using PHP CS Fixer

First time, install PHP CS Fixer:

Fix code formatting:

Dry run (preview changes without applying):

Dry run with diff (preview exact changes):


Docker Setup

The scaffold ships a complete Docker stack under docker/: PHP-FPM + Nginx for the website, plus Valkey (cache/sessions), and optional WebSocket, cron, and database (MySQL/MariaDB/PostgreSQL) containers behind profiles.

All operations go through the wrapper script — never docker compose directly, since it wires the per-instance env files and secrets the compose file needs:

<instance> selects the env files, secrets, and published ports, so multiple instances can run side by side. First-time setup (creating your instance's env files, secrets, and picking a database engine) is documented in the scaffold's docs/development/docker.md.


MsgPack Support

This package can use MsgPack for faster cache and payload serialization. While the native PHP MsgPack extension (installed via pecl or system packages) offers the best performance, not all servers have it available.

Install the PHP MsgPack Fallback Library

Add the pure PHP implementation to your project, along the composer patcher:

Apply the PHP 8.1+ Compatibility Patch

Add the following configuration to your root composer.json:

Apply the Changes

Run the following command to install dependencies and apply patches:


Application Structure

Project Setup

Create a root folder named app and upload the project inside it — on a server that is where the project lives, in place of public_html or similar. The framework follows an HMVC (Hierarchical Model-View-Controller) architecture based on CodeIgniter.

Root Directory

Public Directory

The public/ folder contains all publicly accessible files served by the web server.

Application Directory

The application/ folder contains the core application code and global resources.

Modules (HMVC Structure)

The framework uses HMVC architecture, allowing you to organize code into self-contained modules. Each module can have its own MVC structure and resources.

Benefits of HMVC:

Example Module Structure:

Additional Directories


All versions of manager with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
nielbuys/framework Version ^3.1
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 ixaya/manager contains the following files

Loading the files please wait ...