Download the PHP package oops/morozko without Composer
On this page you can find all versions of the php package oops/morozko. 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 morozko
Oops/Morozko
:warning: THIS PACKAGE IS NO LONGER MAINTAINED. You can use the AdvancedCache module from contributte/console-extra instead.
Are you warm yet, my little application?
Morozko is a utility for cache warmup in a Nette Framework application.
Installation and requirements
Oops/Morozko requires PHP >= 7.1.
Oops/Morozko provides a Symfony/Console command, thus, you must also install and configure a Symfony/Console integration package such as Kdyby/Console or contributte/console.
Usage
Register the extension in your config file. Don't forget to register a Symfony/Console integration as well:
Then you can directly run the oops:morozko:warmup command, or add it to your deploy process.
Default cache warmers
By default, the oops:morozko:warmup command executes one default cache warmer: the NetteConfiguratorCacheWarmer, which compiles the DI container.
To be able to do so, it needs to know how your DI container is configured - you need to provide it with an implementation of ConfiguratorFactoryInterface whose create() method should return the same Configurator as in your application's bootstrap.php. Actually, it might be wise to use the implementation in bootstrap.php to prevent code duplication.
Be aware that in CLI the %wwwDir% and %appDir% parameters might not actually point to the document root. For example, if you run console commands via bin/console.php, it will likely point to the bin directory.
If that is your case, you need to set the parameters to the correct values in your configurator factory, otherwise the generated DI container won't match the one actually used in production:
Additional cache warmers
There are currently these official additions to the Morozko's DI container cache warmer:
oops/morozko-latte-bridgepre-compiles all Latte templates found within a configured directory.oops/morozko-doctrine-bridgewarms up Doctrine metadata cache and generates entity proxies.
Custom cache warmers
You can also create your own cache warmers. Simply create a class implementing the Oops\Morozko\CacheWarmer interface and register it as a service into the DI container.
Third-party cache warmers
If you have a cache warmer that you'd like to share with others, feel free to add it to this section via a pull request.
All versions of morozko with dependencies
nette/di Version ^2.4.10
nette/finder Version ^2.4
ocramius/package-versions Version ^1.1
psr/log Version ^1.0
symfony/console Version ^3.3||^4.0