Demo: Deploying Simple Micsoservices With Docker Compose

- Create the project directory
#mkdir simple-wordpress

-Install docker compose
#yum -y install docker-compose

-Create the following compose file as "docker-compose.yml"
version: '2'   ---> 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
      environment:
           MYSQL_ROOT_PASSWORD: somewordpress
           MYSQL_DATABASE: wordpress
           MYSQL_USER:    wordpress
           MYSQL_PASSWORD: wordpress
  web:       --->service name
       depends_on:
          -db
       image: wordpress:latest       
       restart: always
       ports:    --> expose ports to the host
           - "8000:80"
      environment:
           WORDPRESS_DB_HOST: db:3306
           WORDPRESS_DB_HOST: wordpress
           WORDPRESS_DB_PASSWORD: wordpress

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


-Build the project, on the project directory run:
#docker compose up -d
if you want to stop
#docker-compose down

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ı