ahmed-bhs

<?php

namespace Portal\Common\Infrastructure\Symfony\DependencyInjection;

use Symfony\Component\DependencyInjection\ContainerBuilder;
use Symfony\Component\DependencyInjection\Extension\Extension;

class AppContextExtension extends Extension
{
    public function load(array $configs, ContainerBuilder $container)

ahmed-bhs

<?php

Portal\Common\Infrastructure\Symfony\PortalBundle::class => ['all' => true],

ahmed-bhs

"autoload": {
    "psr-4": {
        "App\\": "src/",
        "Portal\\Common\\Infrastructure\\Symfony\\": "portal/src/Symfony/"
    }
},

ahmed-bhs

OFF DOC: https://github.com/Exercise/FOQElasticaBundle

Exemples utiles: https://hotexamples.com/examples/-/Elastica%255CQuery%255CMatch/setFieldFuzziness/php-elastica%255cquery%255cmatch-setfieldfuzziness-method-examples.html

    $finder = $this->container->get('fos_elastica.finder.app.job');
    // filter only activated and not expired
    $filter = new \Elastica\Query\BoolQuery();
    $filter->addMust(new \Elastica\Query\Term(array('isActivated' => true)));
    $rangeQuery = new \Elastica\Query\Range();

ahmed-bhs

Using fos_elastica.finder.post_index.post service to get list of sugesstion available from my mapping:

fos_elastica:
    clients:
        default: { host: elasticsearch, port: 9200 }
    indexes:
        post_index:
            client: default

ahmed-bhs

I dont know why this json query does not return the hole aggregations:

```

{
  "query": {
    "match": {
      "title": {
        "query": "test11",
        "fuzziness": 0

ahmed-bhs

http://blog.servergrove.com/2015/04/13/symfony2-components-overview-optionsresolver/

ahmed-bhs

https://symfony.com/doc/current/event_dispatcher.html?fbclid=IwAR24BDj4UJ9MuOI6klzeR33MOuAfajQKBCrEenuEpYooik3b_tvdClKWkVE

ahmed-bhs

# Project language
language: php

# Allows use container-based infrastructure
sudo: false

# Start mysql service
services:
  - mysql

ahmed-bhs

Auto-Deploying via Travis CI

Because Travis CI can automatically execute scripts after successfully (or unsuccessfully!) executing tests, it is an obvious choice for a deployment tool. In order to deploy to a Git repository on a remote server, the process generally is as follows:

• Set up SSH keys
• Add the server's copy of the repository as a Git remote
• Push to the remote
• SSH into the server and execute any installation/compilation/miscellaneous commands

Before even touching .travis.yml...

Users