Download the PHP package proklung/container-locator-bundle without Composer

On this page you can find all versions of the php package proklung/container-locator-bundle. 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?

Example code of proklung/container-locator-bundle

Informations about the package container-locator-bundle

Служебный бандл, позволяющий получить экземпляр контейнера за пределами Symfony в кастомных (Wordpress, Bitrix) вариантах использования

INTERNAL

Установка

composer.json:

Зачем?

Эксперимент. Сейчас хэлпер container в моих пакетах обращается к основному классу ServiceProvider, что нормально. Способ, реализуемый в этом бандле - альтернативный, представялется, что выглядит малость "чище".

Основан на знании, что в каждый инициированый бандл по методу boot загоняется экземпляр контейнера.

Все, что делается в этом бандле - декорируется метод setContainer бандла, сохраняя контейнер в статическое свойство. Плюс отвязывается от конкретной реализации контейнера.

Как достать контейнер

Класс ContainerLocator:

В результате хэлпер container может выглядеть как-то так:

Синтаксический сахарок

Для использования в неконтейнеродружелюбных местах (внутри компонентов Битрикс и т.п)

Класс ContainerHelper:

All versions of container-locator-bundle with dependencies

PHP Build Version
Package Version
Requires php Version >=7.3 || ^8.0
symfony/dependency-injection Version ^4.4 || ^5.0
symfony/http-kernel Version ^4.4 || ^5.0
symfony/config Version ^4.4 || ^5.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 proklung/container-locator-bundle contains the following files

Loading the files please wait ....