I'm looking to integrate the FOSElasticaBundle into my symfony 3 project. Currently this bundle doesn't support symfony 3. I was ondering what I could do to still implement it?
Seems is not yet tagged a valid release for using it via packagist. See this issue on github.
The release dev-master / 3.2.x-dev seems already compliant with symfony3.
I successfully installed this bundle on a symfony3 installation with the command :
composer require friendsofsymfony/elastica-bundle dev-master
Hope this help
Related
At https://symfony.com/doc/current/setup.html you are instructed to run:
composer create-project symfony/website-skeleton my-project
whereas at http://symfony.com/doc/current/quick_tour/the_big_picture.html you are instructed to run:
composer create-project symfony/skeleton quick_tour
I have just done both. Using symfony/website-skeleton I got an error message in the browser: No route found for "GET /"
With symfony/skeleton I did get a Welcome to Symfony 4.0.4 page.
What are the differences between the two and why would you use one rather than the other?
The new symfony edition (Symfony 4) is "bundle less".
Symfony core team decided to not provide the Symfony Standard Edition for Symfony 4.0 that means when you run composer create-project symfony/skeleton you download the minimum package to start an application and you have to download the over packages needed and you need to explicitly add all the dependencies you want to depend on (twig, routing...) look here for other package .
But it could be difficult for new comers and the Symfony core team dediced to provide an edition with the minimum common Symfony features.
You get it with composer create-project symfony/website-skeleton.
You have more explanation here
Came here as a result of a similar search, but was more interested in what's under the hood.
Not to take away from the accepted answer, but for those who, like me, were after something more detailed, you can look at the package details in packagist and reviewing the dependencies noted in the requires and requires dev sub-sections:
https://packagist.org/packages/symfony/website-skeleton
Includes: framework, framework extra, console, asset, security, validator twig, doctrine, http client, serialiser, yaml, dotenv, flex, form and validator packages among others.
https://packagist.org/packages/symfony/skeleton
Includes: console, dotenv, flex, platform and yaml only.
Seems like a no brainer, but if you came here looking for it, it's there.
php artisan workbench vendor/package --resources
command is not available in laravel 5, but how now create package in laravel 5 ?
Shameless self-promotion, but I've written a post about this called "Creating Laravel 5 packages for dummies" that explains how to create the package, how to put it on GitHub & Packagist and how to push changes/new versions afterwards.
If you're already familiar with creating packages in Laravel 4, the fastest solution I've found was to use this CLI tool.
The laravel workbench has been renamed in laravel 5 to "Package Development" in the documentation
http://laravel.com/docs/master/packages
Notice that there is no longer a workbench command and you need to create your own package structure, as the Laravel creator want to limit the dependency between created packages and the Laravel framework (#ref)
UPDATE: Laravel 5 is now stable and the illuminate/workbench package can be used in a laravel 5 application as I suggested in this post
In Laravel, these are some handy tricks I follow each time I need to create a Laravel package
Solution 1: Get a boilerplate template from https://github.com/cviebrock/laravel5-package-template, and put it under packages/ (follow the instruction in the repo)
Solution 2: Use a packager (with Laravel >= 5.5)
Install packager it as dev dependency > composer require jeroen-g/laravel-packager --dev (check instruction in the repo here)
create the package > composer require jeroen-g/laravel-packager --dev etc, see full tuto
then, we have a choice to keep the package in our project, or just remove it by rollingback composer.json
Hope this is a good update for Laravel lovers ;)
php artisan workbench vendor/package --resources
command is not available in laravel 5, but how now create package in laravel 5 ?
Shameless self-promotion, but I've written a post about this called "Creating Laravel 5 packages for dummies" that explains how to create the package, how to put it on GitHub & Packagist and how to push changes/new versions afterwards.
If you're already familiar with creating packages in Laravel 4, the fastest solution I've found was to use this CLI tool.
The laravel workbench has been renamed in laravel 5 to "Package Development" in the documentation
http://laravel.com/docs/master/packages
Notice that there is no longer a workbench command and you need to create your own package structure, as the Laravel creator want to limit the dependency between created packages and the Laravel framework (#ref)
UPDATE: Laravel 5 is now stable and the illuminate/workbench package can be used in a laravel 5 application as I suggested in this post
In Laravel, these are some handy tricks I follow each time I need to create a Laravel package
Solution 1: Get a boilerplate template from https://github.com/cviebrock/laravel5-package-template, and put it under packages/ (follow the instruction in the repo)
Solution 2: Use a packager (with Laravel >= 5.5)
Install packager it as dev dependency > composer require jeroen-g/laravel-packager --dev (check instruction in the repo here)
create the package > composer require jeroen-g/laravel-packager --dev etc, see full tuto
then, we have a choice to keep the package in our project, or just remove it by rollingback composer.json
Hope this is a good update for Laravel lovers ;)
I am installing Symfony 2.3.x and sonata admin bundle, but when it is installed, the admin panel is shown in a wrong way (see the screen capture).
This problem has appeared when I run composer update command. Before that, my sonata admin panel looks nice.
Any idea? Could be a problem with any template of sonata? (Icons from sonata not appear).
Thank you!
It appears that there is a dependency between the dev-master versions of SonataCoreBundle and SonataAdminBundle that breaks if any older version is used between either. Here is a GitHub issue regarding the problem
The solution is to use the ~2.3 Composer version tag of SonataAdminBundle instead of dev-master, or run composer require sonata-project/core-bundle dev-master so that it exceeds the minimum requirement of ~2.2 for SonataCoreBundle in the composer.json file of SonataAdminBundle. Then run composer update to fix all of the dependencies.
I want to start a new project on symfony 2.4.3 and I need the functionality of the fosuserbundle. My Problem: On their github (https://github.com/FriendsOfSymfony/FOSUserBundle) in the documentation they recommand 2.1.x.
Here , a user says you should install fosuserbundle manually but this question is for symfony 2.3.
Can I use the bundle on my version of symfony? If yes, can I install it with composer? If no, are there any similar bundles that I can use instead?
Thanks in advance
This version of the bundle requires Symfony 2.1+. If you are using Symfony 2.0.x, please use the 1.2.x releases of the bundle.
From their docs. 2.1+ means, 2.1, 2.2, 2.3, 2.4, ... 2.n So 2.3 is perfectly valid.
Moreover, Composer handles the dependencies for you, so just require it and run composer update, if the Symfony version is not supported the command fails and you know it doesn't support your current version, if it succeeds everything is working perfectly.