Use latest available packagist
sadortun opened this issue · comments
Hi,
composer/packagist@2d90743 is over a year old,
Would it be possible to have a release pointing to the latest packagist ?
Thanks,
Samuel
Hi Samuel.
There's a switch from Solr to Algolia. I was thinking about second docker image, because you have to provide Algolia's credentials.
What do you think?
ping @sadortun
@f3l1x would it be possible to have one image with various config options. I think it would be more simple to maintain.
Well, I don't know how to achieve that. This package is based on composer/packagist repo. It's hardcoded to old revision with Solr support. The latest version of the packagist is based on Algolia. I don't know how to combine these two options together.
Do you know?
@f3l1x Ahhh, i see ! Sorry about that !
In that case, you should probably have two branches, (1.x, 2.x) where 1.x is the following patch versions of the current master branch, and where 2.x use the newest packagist releases.
At some point in the future, master should jump to 2.x when you find fit to stop supporting the old packagist version.
implemented support for 2 search engines ( Solr for self - hosted ) See PR #15