Download the PHP package compwright/codeigniter-installers without Composer
On this page you can find all versions of the php package compwright/codeigniter-installers. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download compwright/codeigniter-installers
More information about compwright/codeigniter-installers
Files in compwright/codeigniter-installers
Package codeigniter-installers
Short Description Composer installers for CodeIgniter
License MIT
Homepage https://github.com/compwright/codeigniter-installers
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 codeigniter-installers
CodeIgniter Installers for Composer
Composer installers for CodeIgniter components, Sparks, and modules
Usage
To use, simply specify the desired type from the list below and require the
compwright/codeigniter-installers package in your composer.json file, like so:
By default this installer expects your project's composer.json file to be at the same level as your
application directory and sparks directory. If you are using a different directory structure for
your project, you will need to configure the paths accordingly in your project composer.json file:
Supported Package Types
| Package Type | Installs To |
|---|---|
codeigniter-library |
application/libraries/{package}/ |
codeigniter-core |
application/core/ |
codeigniter-third-party |
application/third_party/{package}/ |
codeigniter-module |
application/modules/{package}/ |
codeigniter-spark |
sparks/{package}/ |
Notes
-
codeigniter-librarypackages should follow CodeIgniter library naming conventions, and the library PHP file should match the package name or you will need to set up a custom loader or manuallyincludethe file.If one or more PHP files have the
MY_subclass prefix, they will be moved up one level into theapplication/libraries/directory. If all of the PHP files have theMY_prefix, then theapplication/libraries/{package}directory will be deleted after the PHP files are moved. Uninstallation of these files must be performed manually. -
codeigniter-corepackages are specifically for packages that override a core CodeIgniter file in theapplication/core/directory. All PHP files will installed into that directory. Any non-PHP files included in the package will not be installed.Uninstallation of
codeigniter-corepackages must be performed manually. -
codeigniter-modulepackages are designed for the Modular Extensions add-on for CodeIgniter, but in theory it could work with any type of module provided that the installation directory is the same. -
codeigniter-sparkpackages should be built according to the instructions on getsparks.org. - Individual support for CodeIgniter controllers, config files, language files, models, or helpers is not supported. Those components should be encapsulated in a module or spark.
