Download the PHP package swalker2/cpanel without Composer
On this page you can find all versions of the php package swalker2/cpanel. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 cpanel
swalker2 - Cpanel
The simplest PHP implementation of the cpanel version 2 api for Laravel
At the moment suporting only the Zone Edit and Email modules
You can write your own modules if you dig into the Guide to cPanel API 2
Install
Require this package with composer using the following command:
After updating composer, add the service provider to the providers array in config/app.php
Also, publish the configuration file using the following command:
Finally, add the .env variables:
But how do I use it?
After completing the instalation steps, you simply make a cpanel instance, like so:
And then you can call the module implementations
Note that the Modules that you create can be instantiated individually:
Writing a module
To write a module you need to extend the class Swalker2\CpanelFunction
like so:
Contributing
Feel free to send pull requests, not just bug reports.
"Bug reports" may also be sent in the form of a pull request containing a failing test.
However, if you file a bug report, your issue should contain a title and a clear description of the issue. You should also include as much relevant information as possible and a code sample that demonstrates the issue. The goal of a bug report is to make it easy for yourself - and others - to replicate the bug and develop a fix.
