In the example below, "drupal_solr_conf" is in /var/www/sites/example.com 1sudo su solr 2cd /var/www/sites/example.com 3/opt/solr/bin/solr create_core -c upd_event -d drupal_solr_conf

1icasimpan@example.local:/opt/solr/bin$ sudo su solr -s /bin/bash 2solr@example.local:/opt/solr-6.6.2/bin$ /opt/solr/bin/solr create -c sample -p 8983 34Copying configuration to new core instance directory: 5/var/solr/data/sample 67Creating new core 'sample' using command: …

1$config['search_api.server.solr_events']['backend_config']['connector_config']['host'] = '68.193.132.102'; 2$config['search_api.server.solr_events']['backend_config']['connector_config']['port'] = '8983'; …

In Drupal Admin, do the following: Config > Search and Metadata > Search API Click on the index name (e.g. Events) Image not found a.warning-link { color: inherit !important; font-weight: inherit !important; text-decoration: underline !important; border-bottom: none !important; } Web path: …

1docker run -d --name testOnly -p 6379:6379 redis:latest NOTE: Always read the format of -p as host:container.

1docker ps -a

1docker logs <friendly-name|container-id> You can tail it much like tailing ordinary logs: 1docker logs -f --tail=5 <friendly-name|container-id> which means: "start tailing at current last 5 entries of the logs"

Example scenario: 1[root@selenium php-5.1.2]# docker build -t php5_1_2 . 2Sending build context to Docker daemon 8.071MB 3Step 1/9 : FROM nubs/arch-build 4---> a68cd3855bfe 5Step 2/9 : MAINTAINER Spencer Rinehart <anubis@overthemonkey.com> 6---> Using cache 7---> 0d099a2cd179 8Step 3/9 : COPY …

Location in 1/var/lib/docker

1[root@selenium02 ~]# docker rmi ad66a5961263 2Error response from daemon: conflict: unable to delete ad66a5961263 (must be forced) - image is being used by stopped container 088219585a61 3[root@selenium02 ~]# docker rmi -f ad66a5961263