Download the PHP package cs/symfony-vagrant-kernel without Composer

On this page you can find all versions of the php package cs/symfony-vagrant-kernel. 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:
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.
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 symfony-vagrant-kernel

Symfony Vagrant Kernel

This package can speed up your Symfony dev installation when you're using Vagrant.

If your application is residing on your host os' drive and it's shared with Vagrant box over network then symfony cache and logs IO will kill your performance. This kernel extension configures your application to store cache and logs in /dev/shm.

The only drawback I can think of is that the whole cache (possible including sessions) will be lost once you power down the Vagrant box. Oh, and /dev/shm was probably designed for sharing...

WARNING! This is not for production. Use at your own risk! WARNING! The logs will be in /dev/shm/(symfony2|projectname)/logs.

Installation

Add "cs/symfony-vagrant-kernel": "1.0", to your composer.json.

Change the line use Symfony\Component\HttpKernel\Kernel; to use CS\Vagrant\Kernel; in your app/AppKernel.php.

Multiple projects on the same Vagrant box

If you have multiple projects running on the same vagrant box then you should define your "project name" which is basically the name of /dev/shm subdirectory which will be used to store your cache. If you don't do this then prepare for chaos to ensue.

Override the method getProjectName, so it looks sth like this:

Configure when to attempt to use the memory cache.

By default the kernel will enable /dev/shm caching when following conditions are met:

You can change the last condition by overriding the method useMemoryCaching in your kernel. For example if you want this feature to be used always in your dev environment do sth like this:

Other considerations

I suppose you could use /tmp but doesn't memory cache sound better?

Acknowledgment

This code is based on the idea presented by Benjamin Eberlei and later expanded by Jakub Kanclerz.


All versions of symfony-vagrant-kernel with dependencies

PHP Build Version
Package Version
Requires php Version >=5.4
symfony/http-kernel Version >=2.3.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package cs/symfony-vagrant-kernel contains the following files

Loading the files please wait ...