Download the PHP package vortexphp/vortex without Composer
On this page you can find all versions of the php package vortexphp/vortex. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download vortexphp/vortex
More information about vortexphp/vortex
Files in vortexphp/vortex
Package vortex
Short Description Lightweight PHP application stack (app/, config/, resources/views, routes/, lang/)
License MIT
FAQ
Example:
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 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.
Informations about the package vortex
Vortex Startup App
Minimal startup-ready PHP app on vortexphp/framework.
The vortex file in the project root is the CLI entry point (also registered in Composer bin). Run it with php vortex <command> (for example php vortex serve).
Requirements
- PHP
8.2+ - Composer
- Node.js + npm (for Tailwind CSS build)
- GNU Make (optional; use the
composer run …equivalents below if you prefer) - Docker (optional; see Docker)
Monorepo development
composer.json includes path repositories so a full Vortex checkout can symlink vendor/vortexphp/framework and vendor/vortexphp/live to sibling packages while you work on the framework. That is optional: vendor/ is gitignored, and installs from Packagist use normal package copies when those path entries are absent or unused. If you see symlinks under vendor/vortexphp/, you are using the local path repositories.
Quick start (clone)
Same without Make:
Create Project
Install (existing clone)
Generate APP_KEY and put it in .env:
Set at least:
APP_KEYAPP_URL(for local:http://localhost:8000)
Run Locally
Build front-end assets (Tailwind → public/css/app.css, then copy Live → public/js/live.js):
npm run build only compiles CSS; composer run build / make build also runs php vortex publish:assets, which copies package assets (for example vortexphp/live → public/js/live.js).
Watch CSS during development:
Run the app:
Open:
http://localhost:8000/http://localhost:8000/health
Useful Commands
Assets
| Output | Source | How it is produced |
|---|---|---|
public/css/app.css |
ui/css/app.css |
Tailwind: npm run build / npm run dev |
public/js/live.js |
vendor/vortexphp/live/resources/live.js |
php vortex publish:assets (from LivePackage::publicAssets()); part of composer run build; also Composer post-install / post-update |
Templates reference /css/app.css and /js/live.js only. There is no separate public/dist/ pipeline in this app; that path is gitignored to avoid duplicate stale files.
Database seeders
database/seeders/DatabaseSeeder.php (Database\Seeders\DatabaseSeeder) is the entry point for seed data. Wire it into your own commands or tooling as the project grows.
Exceptions
App\Exceptions\AppException— base class for domain-level errors.App\Exceptions\Handler— implementhandle()to return a customResponsefor specific throwables; returnnullto use the frameworkErrorRenderer(wired frompublic/index.php).
Docker
Requires vendor/ (run composer install on the host first). Then:
Serves on http://127.0.0.1:8080/ (PHP built-in server, 0.0.0.0:8080 inside the container).
Production Install
(composer run build runs npm run build and then syncs Live assets; Node is required for the Tailwind step.)
