Docker Compose

Compose is a tool for defining and running multi-container Docker applications. With Compose, you use a YAML file to configure your application's services. Then, with a single command, you create and start all the services from your configuration.

 Docker Compose Use Case

When you're developing software, the ability to run an application in an isolated environment and interact with it is crucial.

The Compose file provides a way to document and configure all of the application's service dependencies (databases,queues, caches, web service APIs,etc)

Docker Compose Quickstart

There are 3 step process:

1- Define your app's environment with a Dockerfile so it can be reproduced anywhere.
2- Define the services that make up your app in docker-compose.yml so they can be run together in an isolated environment.
3- Run docker-compose up and Compose will start and run your entire app.

Docker compose file example
version: '3'   ---> compose file format version
services:   ---> defining one or multiple services definition
  db:
      image: mysql:5.7  ---> image to be run by the service
      volumes:
        - db_data: var/lib/mysql --> volume to be used by services
      restart: always

   web:       --->service name
       build: . 
        ports:    --> expose ports to the host
           - "5000:5000"

 volumes:
        db_data:                  ---> Create volume to be used by one or multiple services

Bu blogdaki popüler yayınlar

@SerializedName and @Expose annotations

The  @SerializedName  annotation is needed for Gson to map the JSON keys with our fields. In keeping with Java's camelCase naming convention for class member properties, it is not recommended to use underscores to separate words in a variable.  @SerializedName  helps translate between the two. @SerializedName ( "quota_remaining" ) @Expose private Integer quotaRemaining; In the example above, we are telling Gson that our JSON key  quota_remaining  should be mapped to the Java field  quotaRemaining .  If both of these values were the same, i.e. if our JSON key was  quotaRemaining  just like the Java field, then there would be no need for the  @SerializedName  annotation on the field because Gson would map them automatically. The  @Expose  annotation indicates that this member should be exposed for JSON serialization or deserialization. 
Devamı

About Android padding, margin, width, height, wrap_content, match_parent, R Class

Padding and Margin padding  and  layout_margin  are two very similar attributes. Both determine the space around a View. The difference is that  padding  determines space within the boundaries of the view, and  layout_margin  determines the space outside the boundaries of the view. Width and Height Some of the most important properties are the width property and height property - those must be defined for every view. Remember that all views occupy a rectangular area on the screen - the width and height are the width and height of that area. You can define this in pixels, or better yet dp (stands for density-independent pixels): android:layout_width="200dp" android:layout_height="300dp" For the sake of having a layout be responsive and adjust to different devices, two common values are not numbers at all, but  wrap_content  and  match_parent  used as shown here: android:layout_width="wrap_content" android:layout_height="match_parent"
Devamı