uequations.com Technology Blog

A couple of ways to install Logstash is as a service on the cloud virtual machine, as well as deployed as a Docker container.  For our example, let's deploy Logstash as a Docker container. Assuming the Docker engine in installed, we can pull it from the docker.elastic.co repository: docker pull docker.elastic.co/logstash/logstash   You can execute the "docker image" command to verify the image was pulled.  Before we create a container from this image, we'll create a configuration file.   It is possible to have multiple inputs on a single Logstash configuration file, but let us, for this example, have one configuration file  per input. vim tcp-to-elasticsearch.conf input {   tcp { port => 8080   } } output {   elasticsearch { hosts => ["10.0.0.41:9200"]   }   stdout {

The Oracle NoSQL Database is a scalable, distributed low latency NoSQL database built on Oracle Berkeley DB Java Edition.  Its Docker image can be pulled and run with no changes needed to the Dockerfile. With that being said, we can have an Oracle NoSql Docker container up and running with the following command: docker run --restart=always -dit --name=nosqlce \ -p 5000-5020:5000-5020 oracle/nosql   To verify the container, you can use a 'docker logs' command.  if you're still not convinced, you can use a 'docker exec' command, utilizing kvstore.jar, similar to the following: docker exec -it nosqlce java -Xmx256m -Xmx256m \ -jar /kv-4.3.11/lib/kvstore.jar status -root /kvroot   Here, the root parameter is required.   Hopefully, this command returns a status of 'RUNNING.'  The reason for the '-Xmx256m -Xms256m' settings it's generally a best practice to keep heap usage low for administrative tasks.  if you get curious about the other utility comman…

Now, let's see if we can put together a docker command that will get our MySQL container up and running.  First, let's create a volume for our MySQL instance.

        docker volume create --name mysql_volume

    The following command, then, should create an instance of a MySQL container with a drupal database created on startup.

        docker run --restart=always -d -name mysql -p 3306:3306 \
        -e MYSQL_DATABASE=drupal \
        -e MYSQL_USER=drupal \
        -e MYSQL_PASSWORD=+3fRExawr7fu \
     -v mysql_volume:/var/lib/mysql \
     mysql/mysql-server

    After giving it a moment to get going, the 'docker ps' command should give us the status of our new container.

    We'll also want to execute a 'docker logs' command to get out temporary MySQL password.

     #docker logs mysql

    Next, in order to more easily handle the administration of our MySQL Server, we can run phpmyadmin(https://www.phpmyadmin.com) as a Docker container that's linked …

To install Drupal 7 from its yum repository, you may need to enable the ol7_developer_EPEL repo.  If yum-utils is installed, you can use the yum-config-manager command to do this (you may have to use sudo).

#    yum install yum-utils
#    yum-config-manager --enable ol7_developer_EPEL

    Once you have the repo installed, it's, then, just a matter of installing it from there:

#  yum install drupal7

    This command will install Drupal 7 in the /usr/share/drupal7 directory.

    It will install the Apache HTTP 2.4 web server, but you'll have to install your database separately if it is not installed already.

    Assuming a database has not been installed, we have many options to set one up.  For this installation, I chose to run MySQL as a Docker container.  I took this approach so we can use Docker environment variables to automate the creation of a Drupal database.

    The Github link to the MySQL container I used is:

https://github.com/mysql/mysql-docker

    The …

Let’s see if we can go through some simple examples starting with a typical XService/XServiceImpl example.  In this case, after creating the appropriate XService trait and XServiceImpl extending it, you could extend AppNameModule in the following way:
Listing 1.4: Example of Module binding XService and XServiceImpl package com.uequations.demo.module
import com.uequations.demo.service.{XService, XServiceImpl}
object XServiceModule extends AppNameModule {
override def configure(): Unit = {   bind(classOf[XService]).to(classOf[XServiceImpl]) } }

... This is typically done with the bind and install methods inherited from AbstractModule.  The install method is fairly straightforward, since it can only accept a parameter of type Module.  You’ll notice the bind method will take parameters of type Class, Key, or TypeLiteral.  The Key and TypeLiteral types are part of the Guice library.  
You can probably guess using the bind method takes more thought than just using the install method with a neatly packaged module.  To ease things, though, the bind method comes with a fairly intuitive Embedded Domain-Specific Language(EDSL).  We will give some examples, which will be helpful since developers typically use bind more often than install.  Both methods, as aforementioned, act on a Binder instance.
Before we get into some examples, let me just show you a simple design approach some developers have found useful.  That is to extend Guice’s AbstractModule with an Application-Specific abstract class that overrides the configure method with an…