Download the PHP package anekdotes/manager without Composer
On this page you can find all versions of the php package anekdotes/manager. 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 manager
Anekdotes Manager
A library that provides an easy way to upload files to the server simply by using configurations.
Installation
Install via composer into your project:
Usage
Use the class where ever you need it:
See configuration section below for more information
With Laravel:
Without Laravel:
Catch errors/exceptions:
Configurations
Instantiation
You can pass a config array to the Manager's constructor.
Available properties:
prefix : type string. Path's prefix to upload file (default: /public)
path : type string. Path to upload file (default: /uploads)
exts : type array. Array of all supported file extensions (default: jpg, jpeg, png)
weight : type integer. Maximum file size in bytes (default: 3 mbs)
size : type array. Array containing as many sizes as needed (default: null)
Put together:
Manage method's callback
You may pass a closure to the manage method to execute special code before uploading file such as creating an entry in the database or simply changing name.
With the above example and default configurations, the new file will be located at /public/uploads as potato.jpg.
