Download the PHP package omniphp/omniphp without Composer
On this page you can find all versions of the php package omniphp/omniphp. 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 omniphp
OmniPHP Skeleton
Ready-to-run project layout for the OmniPHP framework.
Layout
One process per concern: server.php serves HTTP, worker.php consumes queues. Both
require bootstrap.php first, so the same configuration and hooks apply everywhere.
Daily commands
| Change | Command |
|---|---|
| Handler / service code | php server.php reload |
routes.php, any app/*/routes.php |
php server.php restart -d (routes are registered in the master) |
Queue handler, config/queue.php |
php worker.php restart -d |
.env |
restart both — reload does not re-read the environment |
Adding things
- A new endpoint: a method on a class in
app/Api/Handlers/, one line inapp/Api/routes.php. - A queue job: implement
OmniPHP\Queue\HandlerInterface, register it underhandlersinconfig/queue.php, push with(new OmniPHP\Queue\Producer())->push('job_name', [...]). - A migration: drop a file in
database/migrations/returning aMigrationsubclass withup(). - Another project (say
Mobile): createapp/Mobile/{Handlers,routes.php}andrequireit fromroutes.php. Namespaces follow the folders (App\Mobile\Handlers\...) with no extra config.
License
MIT
All versions of omniphp with dependencies
PHP Build Version
Package Version
The package omniphp/omniphp contains the following files
Loading the files please wait ...