<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:series="https://publishpress.com/"
	>

<channel>
	<title>Nginx Archives - 아빠프로그래머의 좌충우돌 개발하기!</title>
	<atom:link href="https://www.daddyprogrammer.org/post/tag/nginx/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.daddyprogrammer.org/post/tag/nginx/</link>
	<description>기저귀 갈면서 코딩해야 프로다!</description>
	<lastBuildDate>Thu, 17 Feb 2022 09:53:46 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>

<image>
	<url>https://www.daddyprogrammer.org/wp-content/uploads/2019/04/cropped-spring-bird-2295431_960_720-300x300.jpg</url>
	<title>Nginx Archives - 아빠프로그래머의 좌충우돌 개발하기!</title>
	<link>https://www.daddyprogrammer.org/post/tag/nginx/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Ansible을 이용한 시스템 구성관리(4) – wordpress (nginx+mariadb+php) 설치 자동화</title>
		<link>https://www.daddyprogrammer.org/post/8393/ansible-wordpress-nginx-mariadb-php/</link>
					<comments>https://www.daddyprogrammer.org/post/8393/ansible-wordpress-nginx-mariadb-php/#comments</comments>
		
		<dc:creator><![CDATA[happydaddy]]></dc:creator>
		<pubDate>Tue, 05 Nov 2019 05:01:20 +0000</pubDate>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[DevOps]]></category>
		<category><![CDATA[Ansible]]></category>
		<category><![CDATA[Vagrant]]></category>
		<category><![CDATA[Mariadb]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Nginx]]></category>
		<guid isPermaLink="false">http://3.36.120.4/?p=8393</guid>

					<description><![CDATA[<p>이전 장에서 실습한 nginx, mariadb 설치 내용을 기반으로 하여 php를 추가로 설치하고 wordpress를 구축하는 실습을 해보겠습니다. 이 실습을 통하여 총 4개의 task가 순차적으로 실행되어 wordpress 환경을 구축하는 경험을 할 수 있습니다. wordpress를 설치할 가상환경 추가 Vagrantfile 수정 Vagrant를 이용하여 wordpress를 설치할 VM을 하나더 생성합니다. 해당 VM에는 nginx, mariadb, php, wordpress가 ansible에 의하여 순차적으로 설치되며 wordpress가 [&#8230;]</p>
<p>The post <a href="https://www.daddyprogrammer.org/post/8393/ansible-wordpress-nginx-mariadb-php/">Ansible을 이용한 시스템 구성관리(4) – wordpress (nginx+mariadb+php) 설치 자동화</a> appeared first on <a href="https://www.daddyprogrammer.org">아빠프로그래머의 좌충우돌 개발하기!</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">이전 장에서 실습한 nginx, mariadb 설치 내용을 기반으로 하여 php를 추가로 설치하고 wordpress를 구축하는 실습을 해보겠습니다. 이 실습을 통하여 총 4개의 task가 순차적으로 실행되어 wordpress 환경을 구축하는 경험을 할 수 있습니다.</p>



<figure class="wp-block-image is-resized"><img fetchpriority="high" decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2019/11/ansible-ansible-wordpress.png" alt="" class="wp-image-8674" width="793" height="622" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2019/11/ansible-ansible-wordpress.png 1585w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/ansible-ansible-wordpress-1024x803.png 1024w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/ansible-ansible-wordpress-768x602.png 768w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/ansible-ansible-wordpress-1536x1205.png 1536w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/ansible-ansible-wordpress-150x118.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/ansible-ansible-wordpress-300x235.png 300w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/ansible-ansible-wordpress-696x546.png 696w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/ansible-ansible-wordpress-536x420.png 536w" sizes="(max-width: 793px) 100vw, 793px" /></figure>



<h2 class="wp-block-heading">wordpress를 설치할 가상환경 추가</h2>



<h3 class="wp-block-heading">Vagrantfile 수정</h3>



<p class="wp-block-paragraph">Vagrant를 이용하여 wordpress를 설치할 VM을 하나더 생성합니다. 해당 VM에는 nginx, mariadb, php, wordpress가 ansible에 의하여 순차적으로 설치되며 wordpress가 설치 완료되면 nginx의 80 port로 서비스를 하게 되는데 호스트 PC의 60084 포트로 접근 가능하도록 아래와 같이 작성합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">#ansible-client004
config.vm.define "ansible-client004" do |cfg|
cfg.vm.box = "centos/7"
cfg.vm.provider "virtualbox" do |vb|
vb.name = "ansible-client004"
end
cfg.vm.host_name = "ansible-client004"
cfg.vm.network "public_network", ip: "192.168.1.4"
cfg.vm.network "forwarded_port", guest: 80, host: 60084, auto_correct: true
cfg.vm.synced_folder "../shared_data", "/shared_data", disabled: true
cfg.vm.provision "shell", path: "enable_ssh_password_auth.sh"
end</pre>



<h3 class="wp-block-heading"> wordpress inventory 추가</h3>



<p class="wp-block-paragraph">Vagrant에서 생성한 VM을 ansible inventory에 추가합니다. setup-ansible-env.yml 열고 아래와 같이 [wordpress] inventory를 추가합니다. 해당 설정을 적용하면 ansible server의 /etc/ansible/hosts에 [wordpress] 내용이 추가됩니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
- name: Setup for the Ansible's Environment
  hosts: localhost
  gather_facts: no

  tasks:
    - name: Add "/ect/ansible/hosts"
      blockinfile:
        path: /etc/ansible/hosts
        block: |
            [webservers]
            192.168.1.1
            [dbservers]
            192.168.1.2
            [cacheservers]
            192.168.1.3
            [wordpress]
            192.168.1.4
    - name: Configure Bashrc
      lineinfile:
        path: /home/vagrant/.bashrc
        line: "{{ item }}"
      with_items:
        - "alias ans='ansible'"
        - "alias anp='ansible-playbook'"
        - "alias ang='ansible-galaxy'"</pre>



<p class="wp-block-paragraph">vm을 새로 생성하고 관련 설정을 적용하기 위해 다음 명령어를 실행합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ vagrant up ansible-client004
$ vagrant provision</pre>



<h2 class="wp-block-heading">playbook 작성</h2>



<p class="wp-block-paragraph">새로 생성한 서버에 다음 애플리케이션을 설치하는 ansible playbook을 작성해 보겠습니다.</p>



<ul class="wp-block-list"><li>nginx 설치</li><li>mariadb 설치</li><li>php 설치</li><li>wordpress 설치</li></ul>



<h3 class="wp-block-heading">role 생성 및 task 작성</h3>



<p class="wp-block-paragraph">ansible-galaxy 명령을 이용하여 wordpress role을 생성합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ cd roles
$ ang init wordpress
- wordpress was created successfully
$ $ tree wordpress
wordpress/
|-- README.md
|-- defaults
|   `-- main.yml
|-- files
|-- handlers
|   `-- main.yml
|-- meta
|   `-- main.yml
|-- tasks
|   `-- main.yml
|-- templates
|-- tests
|   |-- inventory
|   `-- test.yml
`-- vars
    `-- main.yml</pre>



<h3 class="wp-block-heading">1. nginx 설치</h3>



<h4 class="wp-block-heading">1.1. task 작성</h4>



<ul class="wp-block-list"><li>epel 저장소 업데이트</li><li>nginx 설치</li><li>nginx.conf 템플릿 적용</li><li>nginx 재시작</li></ul>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ cd wordpress/tasks
$ vi nginx_install.yml</pre>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
  - name: install epel-release
    action: "{{ ansible_pkg_mgr }} name=epel-release state=latest"
  - name: install nginx web server
    action: "{{ ansible_pkg_mgr }} name=nginx state=present"
  - name: write nginx.conf
    action: template src=../templates/nginx.conf.j2 dest=/etc/nginx/nginx.conf
    notify:
        - restart nginx web server</pre>



<h4 class="wp-block-heading">1.2. template 작성</h4>



<p class="wp-block-paragraph">nginx.conf 파일은 이전장의 내용을 활용하였고 wordpress설치를 위해 추가된 설정이 존재합니다. </p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ cd wordpress/templates
$ vi nginx.conf.j2</pre>



<p class="wp-block-paragraph">nginx root를 wordpress 설치 디렉터리로 변경합니다. 그리고 index접근시 php 확장자도 인식하도록 설정합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">root         /usr/share/nginx/wordpress;
index        index.php index.html index.htm;</pre>



<p class="wp-block-paragraph">php 처리 가속을 위해 다음과 같이 설정을 추가합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">        location ~ \.php$ {
            fastcgi_pass unix:/var/run/php-fpm/php-fpm.sock;
            fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
            include fastcgi_params;
            fastcgi_read_timeout 300;
        }</pre>



<p class="wp-block-paragraph">변경된 내용이 적용된 nginx.conf.j2는 다음과 같습니다. 아래에서는 샘플로 몇개의 변수만 적용하였지만 실제 서비스에는 더 많은 변수를 적용하여 사용하면 됩니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">user nginx;
worker_processes {{ nginx.processor_count }};
error_log /var/log/nginx/error.log;
pid /run/nginx.pid;

include /usr/share/nginx/modules/*.conf;

events {
    worker_connections {{ nginx.max_worker_connection }};
}

http {
    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

    access_log  {{ nginx.log_dir }}/{{ nginx.access_log_name }}  main;

    sendfile            on;
    tcp_nopush          on;
    tcp_nodelay         on;
    keepalive_timeout   65;
    types_hash_max_size 2048;

    include             /etc/nginx/mime.types;
    default_type        application/octet-stream;

    include /etc/nginx/conf.d/*.conf;

    server {
        listen       {{ nginx.port }} default_server;
        listen       [::]:{{ nginx.port }} default_server;
        server_name  _;
        root         /usr/share/nginx/wordpress;
        index        index.php index.html index.htm;

        # Load configuration files for the default server block.
        include /etc/nginx/default.d/*.conf;

        location / {
            try_files $uri $uri/ =404;
        }

        location ~ \.php$ {
            fastcgi_pass unix:/var/run/php-fpm/php-fpm.sock;
            fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
            include fastcgi_params;
            fastcgi_read_timeout 300;
        }

        location ~ /\.ht {
            deny all;
        }

        error_page 404 /404.html;
            location = /40x.html {
        }

        error_page 500 502 503 504 /50x.html;
            location = /50x.html {
        }
    }
}</pre>



<h4 class="wp-block-heading">1.3. variable 파일 작성</h4>



<p class="wp-block-paragraph">nginx.conf.j2에 사용되는 변수 정보를 세팅합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ cd wordpress/vars
$ vi main.yml</pre>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
# vars file for nginx
nginx:
    processor_count: 30
    max_worker_connection: 512
    log_dir: /var/log/nginx
    access_log_name: access.log
    port: 80</pre>



<h4 class="wp-block-heading">1.4. handler 파일 작성</h4>



<p class="wp-block-paragraph">nginx task 수행시 사용할 시작, 재 시작 처리 handler를 작성합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ cd wordpress/handlers
$ vi main.yml</pre>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
# handlers for nginx
- name: start nginx web server
  action: service name=nginx state=started
- name: restart nginx web server
  action: service name=nginx state=restarted</pre>



<h4 class="wp-block-heading">1.5. role 실행을 위한 playbook 작성</h4>



<p class="wp-block-paragraph">playbook에 위에서 작성한 task를 추가합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ cd roles/wordpress
$ vi install_wordpress.yml</pre>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
    - hosts: wordpress
      become: yes
      vars_files:
          - vars/main.yml
      tasks:
          - include: tasks/nginx_install.yml
      handlers:
          - include: handlers/main.yml</pre>



<h3 class="wp-block-heading">2. mariadb 설치</h3>



<h4 class="wp-block-heading">2.1. task 작성</h4>



<ul class="wp-block-list"><li>epel 저장소 업데이트</li><li>mariadb 설치</li><li>python mysql support library 추가</li><li>my.cnf 템플릿 적용</li><li>mysql 서버 시작</li><li>root 패스워드 및 접근권한 수정</li><li>test db 삭제</li><li>wordpress db 신규 생성 </li><li>익명 유저 삭제</li><li>wordpress user 신규 생성 및 접근권한 부여</li></ul>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ cd wordpress/tasks
$ vi mariadb_install.yml</pre>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
  - name: install epel-release
    action: "{{ ansible_pkg_mgr }} name=epel-release state=latest"

  - name: install mariadb
    action: "{{ ansible_pkg_mgr }} name=mariadb-server state=present"

  - name: install python mysql support library
    action: "{{ ansible_pkg_mgr }} name=MySQL-python state=latest"

  - name: copy my.cnf file
    template:
        src=my.cnf.j2 dest=/etc/my.cnf mode=0600

  - name: start mysql server
    action: service name=mariadb state=started enabled=true

  - name: update mysql root password
    mysql_user:
        login_user: root
        login_password: "{{ mysql.root_password }}"
        name: root
        host: "{{ item }}"
        password: "{{ mysql.root_password }}"
        check_implicit_admin: yes
        priv: "*.*:ALL,GRANT"
    with_items:
        - "{{ ansible_hostname }}"
        - 127.0.0.1
        - ::1
        - localhost

  - name: remove test db
    mysql_db:
        login_user: root
        login_password: "{{ mysql.root_password }}"
        db: test
        state: absent

  - name: create a new db
    mysql_db:
        login_user: root
        login_password: "{{ mysql.root_password }}"
        name: "{{ mysql.user_db_name }}"
        collation: "{{ mysql.collation }}"
        encoding: "{{ mysql.encoding }}"
        state: present

  - name: delete anonymouse user
    mysql_user:
        login_user: root
        login_password: "{{ mysql.root_password }}"
        name: ""
        host_all: yes
        state: absent

  - name: create a new user
    mysql_user:
        login_user: root
        login_password: "{{ mysql.root_password }}"
        name: "{{ mysql.user }}"
        password: "{{ mysql.user_password }}"
        priv: "{{ mysql.user_db_name }}.*:ALL,GRANT"
        host: "%"
        state: present</pre>



<h4 class="wp-block-heading">2.2. template 작성</h4>



<p class="wp-block-paragraph">이전 장에서 사용한 my.cnf.j2를 재활용 합니다. 서비스 사용시에는 필요한 설정을 추가하거나 변수를 추가로 적용한다음 vars/main.yml에 값을 추가하면 됩니다. </p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ cd wordpress/templates
$ vi my.cnf.j2</pre>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">[client]
port            = 3306
socket          = /var/run/mysqld/mysqld.sock

[mysqld_safe]
socket          = /var/run/mysqld/mysqld.sock
nice            = 0

[mysqld]
user            = mysql
pid-file        = /var/run/mysqld/mysqld.pid
socket          = /var/run/mysqld/mysqld.sock
port            = 3306
basedir         = /usr
datadir         = /var/lib/mysql
tmpdir          = /tmp
lc_messages_dir = /usr/share/mysql
lc_messages     = en_US
skip-external-locking

bind-address            = {{ mysql.bind_address }}
max_connections         = {{ mysql.max_connections }}
connect_timeout         = 5
wait_timeout            = 600
max_allowed_packet      = 16M
thread_cache_size       = 128
sort_buffer_size        = 4M
bulk_insert_buffer_size = 16M
tmp_table_size          = 32M
max_heap_table_size     = 32M

# * InnoDB
default_storage_engine  = InnoDB
# you can't just change log file size, requires special procedure
#innodb_log_file_size   = 50M
innodb_buffer_pool_size = 256M
innodb_log_buffer_size  = 8M
innodb_file_per_table   = 1
innodb_open_files       = 400
innodb_io_capacity      = 400
innodb_flush_method     = O_DIRECT</pre>



<h4 class="wp-block-heading">2.3. variable 파일 작성</h4>



<p class="wp-block-paragraph">task 및 my.cnf.j2에 설정한 변수에 적용할 값을 세팅합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ cd wordpress/vars
$ vi main.yml</pre>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
# vars file for nginx
nginx:
    processor_count: 30
    max_worker_connection: 512
    log_dir: /var/log/nginx
    access_log_name: access.log
    port: 80
# vars file for mysql
mysql:
    collation: utf8mb4_unicode_ci
    encoding: utf8mb4
    bind_address: 0.0.0.0
    max_connections: 200
    root_password: cjstk1
    user_db_name: wordpress
    user: wordpress
    user_password: wordpress123!</pre>



<h4 class="wp-block-heading">2.4. role 실행을 위한 playbook 수정</h4>



<p class="wp-block-paragraph">playbook에 위에서 작성한 task를 추가합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ cd roles/wordpress
$ vi install_wordpress.yml</pre>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
    - hosts: wordpress
      become: yes
      vars_files:
          - vars/main.yml
      tasks:
          - include: tasks/nginx_install.yml
          - include: tasks/mariadb_install.yml
      handlers:
          - include: handlers/main.yml</pre>



<h3 class="wp-block-heading">3. php 설치</h3>



<ul class="wp-block-list"><li>최신 php 설치를 위해 yum_repository 모듈을 이용하여 remi repository를 등록</li><li>yum_repository 모듈을 이용하여 php repository를 등록</li><li>package 모듈을 이용하여 wordpress에 필요한 라이브러리 설치</li><li>php 가속을 위한 php-fpm 설치</li><li>php-fpm 설정 파일 수정</li><li>php 재시작</li></ul>



<p class="wp-block-paragraph">task 작성시 사용한 모듈은 다음 링크에서 자세한 내용을 확인 할 수 있습니다.</p>



<p class="wp-block-paragraph"><strong>yum repository module</strong><br><a rel="noreferrer noopener" aria-label="https://docs.ansible.com/ansible/latest/modules/yum_repository_module.html (새탭으로 열기)" href="https://docs.ansible.com/ansible/latest/modules/yum_repository_module.html" target="_blank">https://docs.ansible.com/ansible/latest/modules/yum_repository_module.html</a><br><strong>package module</strong><br><a rel="noreferrer noopener" aria-label=" (새탭으로 열기)" href="https://docs.ansible.com/ansible/latest/modules/package_module.html" target="_blank">https://docs.ansible.com/ansible/latest/modules/package_module.html</a><br><strong>replace module</strong><br><a rel="noreferrer noopener" aria-label="https://docs.ansible.com/ansible/latest/modules/replace_module.html (새탭으로 열기)" href="https://docs.ansible.com/ansible/latest/modules/replace_module.html" target="_blank">https://docs.ansible.com/ansible/latest/modules/replace_module.html</a></p>



<h4 class="wp-block-heading">3.1. task 작성</h4>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ cd wordpress/tasks
$ vi php_install.yml</pre>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
  - name: add repository remi-repo
    yum_repository:
       name: remi
       description: "remi repository"
       mirrorlist: http://rpms.remirepo.net/enterprise/$releasever/remi/mirror
       enabled: yes
       gpgcheck: no
       file: remi
  - name: add repository php
    yum_repository:
       name: php73
       description: php73 repo
       file: remi
       mirrorlist: http://rpms.remirepo.net/enterprise/$releasever/php73/mirror
       enabled: no
       gpgcheck: no
  - name: install php packages
    package:
        name:
           - php-cli
           - php-curl
           - php-common
           - php-mysql
           - php-gd
           - php-fpm
           - php-mbstring
           - zip
           - unzip
        enablerepo: php73
        state: present
  - name: setting php-fpm
    replace:
       dest: "/etc/php-fpm.d/www.conf"
       regexp: "{{ item.find }}"
       replace: "{{ item.replace }}"
    with_items:
       - { find: 'user = apache', replace: 'user = nginx'}
       - { find: 'group = apache', replace: 'group = nginx'}
       - { find: 'listen = 127.0.0.1:9000', replace: 'listen = /var/run/php-fpm/php-fpm.sock'}
       - { find: ';listen.owner = nobody', replace: 'listen.owner = nginx'}
       - { find: ';listen.group = nobody', replace: 'listen.group = nginx'}
       - { find: ';listen.mode = 0660', replace: 'listen.mode = 0660'}
    notify:
       - restart php</pre>



<h4 class="wp-block-heading">3.2 handler 파일 작성</h4>



<p class="wp-block-paragraph">php-fpm을 재시작하는 handler를 작성합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ cd wordpress/handlers
$ vi main.yml</pre>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
# handlers for nginx
- name: start nginx web server
  action: service name=nginx state=started
- name: restart nginx web server
  action: service name=nginx state=restarted
# handlers for php
- name: restart php
  action: service name=php-fpm state=restarted</pre>



<h4 class="wp-block-heading">3.3. role 실행을 위한 playbook 수정</h4>



<p class="wp-block-paragraph">playbook에 위에서 작성한 task를 추가합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ cd roles/wordpress
$ vi install_wordpress.yml</pre>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
    - hosts: wordpress
      become: yes
      vars_files:
          - vars/main.yml
      tasks:
          - include: tasks/nginx_install.yml
          - include: tasks/mariadb_install.yml
          - include: tasks/php_install.yml
      handlers:
          - include: handlers/main.yml</pre>



<h3 class="wp-block-heading">4. wordpress 설치</h3>



<ul class="wp-block-list"><li>최신 워드 프레스를 다운로드 받을 디렉터리 생성</li><li>최신 워드 프레스 파일 다운로드</li><li>nginx 기본 디렉터리에 wordpress 압축해제</li><li>wordpress config 파일 생성(wp-config.php)</li><li>database 접속을 위해 wp-config.php 내용 수정</li></ul>



<p class="wp-block-paragraph">task 작성시 사용한 모듈은 다음 링크에서 자세한 내용을 확인 할 수 있습니다.</p>



<p class="wp-block-paragraph"><strong>file module</strong><br>https://docs.ansible.com/ansible/latest/modules/file_module.html<br><strong>get_url module</strong><br>https://docs.ansible.com/ansible/latest/modules/get_url_module.html<br><strong>unarchive module</strong><br>https://docs.ansible.com/ansible/latest/modules/unarchive_module.html<br><strong>command module</strong><br>https://docs.ansible.com/ansible/latest/modules/command_module.html</p>



<h4 class="wp-block-heading">4.1. task 작성</h4>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ cd wordpress/tasks
$ vi wordpress_install.yml</pre>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
  - name: create download/install directory
    file:
       path: "{{ wp.downloadpath }}"
       state: directory
    with_items:
       - "{{ wp.downloadpath }}"

  - name: download latest wordpress
    get_url:
       url: https://wordpress.org/latest.zip
       dest: "{{ wp.downloadpath }}/{{ wp.filename }}"

  - name: extract to /usr/share/nginx
    unarchive:
        src: "{{ wp.downloadpath }}/{{ wp.filename }}"
        dest: "{{ wp.installpath }}"
        remote_src: yes

  - name: copy wp-config-sample.php to wp-config.php
    command: cp "{{ wp.installpath }}/wordpress/wp-config-sample.php" "{{ wp.installpath }}/wordpress/wp-config.php"

  - name: setup wordpress database connection
    replace:
       dest: "{{ wp.installpath }}/wordpress/wp-config.php"
       regexp: "{{ item.find }}"
       replace: "{{ item.replace }}"
    with_items:
       - { find: 'database_name_here', replace: '{{ mysql.user_db_name }}' }
       - { find: 'username_here', replace: '{{ mysql.user }}' }
       - { find: 'password_here', replace: '{{ mysql.user_password }}' }</pre>



<h4 class="wp-block-heading">4.2. variable 파일 작성</h4>



<p class="wp-block-paragraph">task 작성시 설정한 변수에 적용할 값을 세팅합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ cd wordpress/vars
$ vi main.yml</pre>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
# vars file for nginx
nginx:
    processor_count: 30
    max_worker_connection: 512
    log_dir: /var/log/nginx
    access_log_name: access.log
    port: 80
# vars file for mysql
mysql:
    collation: utf8mb4_unicode_ci
    encoding: utf8mb4
    bind_address: 0.0.0.0
    max_connections: 200
    root_password: cjstk1
    user_db_name: wordpress
    user: wordpress
    user_password: wordpress123!
# vars file for wordpress
wp:
    downloadpath: /home/vagrant/downloads
    filename: wordpress-latest.zip
    installpath: /usr/share/nginx</pre>



<h4 class="wp-block-heading">4.3. role 실행을 위한 playbook 수정</h4>



<p class="wp-block-paragraph">playbook에 위에서 작성한 task를 추가합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ cd roles/wordpress
$ vi install_wordpress.yml</pre>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
    - hosts: wordpress
      become: yes
      vars_files:
          - vars/main.yml
      tasks:
          - include: tasks/nginx_install.yml
          - include: tasks/mariadb_install.yml
          - include: tasks/php_install.yml
          - include: tasks/wordpress_install.yml
      handlers:
          - include: handlers/main.yml</pre>



<h3 class="wp-block-heading">playbook 실행</h3>



<p class="wp-block-paragraph">vm에서 ansible playbook을 한번이라도 수행한적이 있다면, 초기상태에서 진행하기 위해 vm을 삭제후 다시 생성하도록 합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ vagrant destroy ansible-client004
$ vagrant up ansible-client004
$ vagrant provision</pre>



<p class="wp-block-paragraph">지금까지 작성한 task를 모두 수행하는 playbook을 실행합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ cd roles/wordpress
$ anp install_wordpress.yml
PLAY [wordpress] **************************************************************************************************************************************************************

TASK [Gathering Facts] ********************************************************************************************************************************************************
ok: [192.168.1.4]

TASK [install epel-release] ***************************************************************************************************************************************************
changed: [192.168.1.4]

TASK [install nginx web server] ***********************************************************************************************************************************************
changed: [192.168.1.4]

TASK [write nginx.conf] *******************************************************************************************************************************************************
changed: [192.168.1.4]

TASK [install epel-release] ***************************************************************************************************************************************************
changed: [192.168.1.4]

TASK [install mariadb] ********************************************************************************************************************************************************
changed: [192.168.1.4]

TASK [install python mysql support library] ***********************************************************************************************************************************
changed: [192.168.1.4]

TASK [copy my.cnf file] *******************************************************************************************************************************************************
changed: [192.168.1.4]

TASK [start mysql server] *****************************************************************************************************************************************************
changed: [192.168.1.4]

TASK [update mysql root password] *********************************************************************************************************************************************
changed: [192.168.1.4] => (item=ansible-client004)
changed: [192.168.1.4] => (item=127.0.0.1)
changed: [192.168.1.4] => (item=::1)
changed: [192.168.1.4] => (item=localhost)

TASK [remove test db] *********************************************************************************************************************************************************
changed: [192.168.1.4]

TASK [create a new db] ********************************************************************************************************************************************************
changed: [192.168.1.4]

TASK [delete anonymouse user] *************************************************************************************************************************************************
changed: [192.168.1.4]

TASK [create a new user] ******************************************************************************************************************************************************
changed: [192.168.1.4]

TASK [add repository remi-repo] ***********************************************************************************************************************************************
changed: [192.168.1.4]

TASK [add repository php] *****************************************************************************************************************************************************
changed: [192.168.1.4]

TASK [install php packages] ***************************************************************************************************************************************************
changed: [192.168.1.4]

TASK [setting php-fpm] ********************************************************************************************************************************************************
changed: [192.168.1.4] => (item={u'find': u'user = apache', u'replace': u'user = nginx'})
changed: [192.168.1.4] => (item={u'find': u'group = apache', u'replace': u'group = nginx'})
changed: [192.168.1.4] => (item={u'find': u'listen = 127.0.0.1:9000', u'replace': u'listen = /var/run/php-fpm/php-fpm.sock'})
changed: [192.168.1.4] => (item={u'find': u';listen.owner = nobody', u'replace': u'listen.owner = nginx'})
changed: [192.168.1.4] => (item={u'find': u';listen.group = nobody', u'replace': u'listen.group = nginx'})
changed: [192.168.1.4] => (item={u'find': u';listen.mode = 0660', u'replace': u'listen.mode = 0660'})

TASK [create download/install directory] **************************************************************************************************************************************
changed: [192.168.1.4] => (item=/home/vagrant/downloads)

TASK [download latest wordpress] **********************************************************************************************************************************************
changed: [192.168.1.4]

TASK [extract to /usr/share/nginx] ********************************************************************************************************************************************
changed: [192.168.1.4]

TASK [copy wp-config-sample.php to wp-config.php] *****************************************************************************************************************************
changed: [192.168.1.4]

TASK [setup wordpress database connection] ************************************************************************************************************************************
changed: [192.168.1.4] => (item={u'find': u'database_name_here', u'replace': u'wordpress'})
changed: [192.168.1.4] => (item={u'find': u'username_here', u'replace': u'wordpress'})
changed: [192.168.1.4] => (item={u'find': u'password_here', u'replace': u'wordpress123!'})

RUNNING HANDLER [restart nginx web server] ************************************************************************************************************************************
changed: [192.168.1.4]

RUNNING HANDLER [restart php] *************************************************************************************************************************************************
changed: [192.168.1.4]

PLAY RECAP ********************************************************************************************************************************************************************
192.168.1.4                : ok=25   changed=24   unreachable=0    failed=0    skipped=0    rescued=0    ignored=0</pre>



<h3 class="wp-block-heading">wordpress 확인</h3>



<p class="wp-block-paragraph">vagrant에서 ansible-client004의 80포트를 60084 port로 접근할수 있도록 세팅하였으므로 다음과 같이 브라우저에서 접근하면 wordpress 첫 세팅 화면을 볼수 있습니다. 초기 세팅을 마치고 로그인하면 관리시스템으로 이동하여 wordpress에 글을 남기거나 추가 기능을 세팅할 수 있습니다. 홈페이지로 이동하면 wordpress 기본 테마 화면을 볼 수 있습니다.</p>



<p class="wp-block-paragraph">http://localhost:60084</p>



<figure class="wp-block-image is-resized"><img decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-1-2048x1746.png" alt="" class="wp-image-8481" width="1024" height="873" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-1-2048x1746.png 2048w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-1-1024x873.png 1024w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-1-768x655.png 768w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-1-1536x1310.png 1536w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-1-150x128.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-1-300x256.png 300w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-1-696x593.png 696w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-1-493x420.png 493w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>



<figure class="wp-block-image is-resized"><img decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-2-2048x929.png" alt="" class="wp-image-8482" width="1024" height="465" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-2-2048x929.png 2048w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-2-1024x465.png 1024w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-2-768x348.png 768w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-2-1536x697.png 1536w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-2-150x68.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-2-300x136.png 300w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-2-696x316.png 696w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-2-926x420.png 926w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>



<figure class="wp-block-image is-resized"><img loading="lazy" decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-3-2048x1100.png" alt="" class="wp-image-8483" width="1024" height="550" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-3-2048x1100.png 2048w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-3-1024x550.png 1024w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-3-768x412.png 768w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-3-1536x825.png 1536w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-3-150x81.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-3-300x161.png 300w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-3-696x374.png 696w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-3-782x420.png 782w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<figure class="wp-block-image is-resized"><img loading="lazy" decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-4-2048x1955.png" alt="" class="wp-image-8484" width="1024" height="978" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-4-2048x1955.png 2048w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-4-1024x977.png 1024w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-4-768x733.png 768w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-4-1536x1466.png 1536w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-4-150x143.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-4-300x286.png 300w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-4-696x664.png 696w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-4-440x420.png 440w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<figure class="wp-block-image is-resized"><img loading="lazy" decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-5-1712x2048.png" alt="" class="wp-image-8485" width="856" height="1024" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-5-1712x2048.png 1712w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-5-856x1024.png 856w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-5-768x919.png 768w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-5-1284x1536.png 1284w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-5-150x179.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-5-300x359.png 300w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-5-696x832.png 696w, https://www.daddyprogrammer.org/wp-content/uploads/2019/11/wp-5-351x420.png 351w" sizes="auto, (max-width: 856px) 100vw, 856px" /></figure>



<p class="wp-block-paragraph">여기까지 ansible을 이용하여 애플리케이션 설치를 자동화하고 wordpress 환경을 구축하는 실습을 진행하였습니다. ansible이 없었다면 wordpress 설치를 위한 여러가지 애플리케이션 설치를 수동으로 진행하거나 복잡한 shell script를 작성해야 했을 것입니다. playbook 작성을 통해 여러대의 시스템에 wordpress 구축이 가능하게 되었으며  관련 애플리케이션의 버전업또한 ansible을 통해 쉽게 관리할 수 있게 되었습니다.</p>



<p class="wp-block-paragraph">실습시 사용한 소스는 아래 github에서 확인할 수 있습니다.</p>



<p class="wp-block-paragraph"><a href="https://github.com/codej99/ansible-web-application.git" target="_blank" rel="noreferrer noopener" aria-label=" (새탭으로 열기)">https://github.com/codej99/ansible-web-application.git</a></p>
<p>The post <a href="https://www.daddyprogrammer.org/post/8393/ansible-wordpress-nginx-mariadb-php/">Ansible을 이용한 시스템 구성관리(4) – wordpress (nginx+mariadb+php) 설치 자동화</a> appeared first on <a href="https://www.daddyprogrammer.org">아빠프로그래머의 좌충우돌 개발하기!</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.daddyprogrammer.org/post/8393/ansible-wordpress-nginx-mariadb-php/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		
		<series:name><![CDATA[Ansible 알아보기]]></series:name>
	</item>
		<item>
		<title>Ansible을 이용한 시스템 구성관리(2) – ansible로 nginx 설치 &#8211; roles, handler, template, vars</title>
		<link>https://www.daddyprogrammer.org/post/7615/ansible-nginx-roles-handler-template-vars/</link>
					<comments>https://www.daddyprogrammer.org/post/7615/ansible-nginx-roles-handler-template-vars/#comments</comments>
		
		<dc:creator><![CDATA[happydaddy]]></dc:creator>
		<pubDate>Wed, 02 Oct 2019 08:15:28 +0000</pubDate>
				<category><![CDATA[DevOps]]></category>
		<category><![CDATA[Ansible]]></category>
		<category><![CDATA[Vagrant]]></category>
		<category><![CDATA[Nginx]]></category>
		<category><![CDATA[Playbook]]></category>
		<guid isPermaLink="false">http://3.36.120.4/?p=7615</guid>

					<description><![CDATA[<p>이번장에는 ansible playbook을 작성하여 nginx를 구축하고 role을 이용하여 playbook 구조를 개선해 보겠습니다. 아래 이미지는 ansible server의 hosts파일에 정의된 [webserver] inventory를 읽어 nginx 애플리케이션을 설치하는 과정을 도식화한 것입니다. 실습에서는 여건상 1대의 서버에만 playbook을 적용해보겠습니다. gather facts 이전까지는 yml 작성시 gather_facts: no로 설정하여 사용하였습니다. 이번장에서는 해당 설정을 제거하고 사용할 것입니다. gather facts를 설정하지 않으면 ansible 서버에 사전 [&#8230;]</p>
<p>The post <a href="https://www.daddyprogrammer.org/post/7615/ansible-nginx-roles-handler-template-vars/">Ansible을 이용한 시스템 구성관리(2) – ansible로 nginx 설치 &#8211; roles, handler, template, vars</a> appeared first on <a href="https://www.daddyprogrammer.org">아빠프로그래머의 좌충우돌 개발하기!</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">이번장에는 ansible playbook을 작성하여 nginx를 구축하고 role을 이용하여 playbook 구조를 개선해 보겠습니다. 아래 이미지는 ansible server의 hosts파일에 정의된 [webserver] inventory를 읽어 nginx 애플리케이션을 설치하는 과정을 도식화한 것입니다. 실습에서는 여건상 1대의 서버에만 playbook을 적용해보겠습니다.  </p>



<figure class="wp-block-image is-resized"><img loading="lazy" decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2019/10/ansible-ansible-nginx.png" alt="" class="wp-image-7820" width="536" height="476" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2019/10/ansible-ansible-nginx.png 714w, https://www.daddyprogrammer.org/wp-content/uploads/2019/10/ansible-ansible-nginx-150x133.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2019/10/ansible-ansible-nginx-300x266.png 300w, https://www.daddyprogrammer.org/wp-content/uploads/2019/10/ansible-ansible-nginx-696x618.png 696w, https://www.daddyprogrammer.org/wp-content/uploads/2019/10/ansible-ansible-nginx-473x420.png 473w" sizes="auto, (max-width: 536px) 100vw, 536px" /></figure>



<h3 class="wp-block-heading">gather facts</h3>



<p class="wp-block-paragraph">이전까지는 yml 작성시 gather_facts: no로 설정하여 사용하였습니다. 이번장에서는 해당 설정을 제거하고 사용할 것입니다. gather facts를 설정하지 않으면 ansible 서버에 사전 정의된 변수들을 수집하여 여러가지 용도로 사용할 수 있습니다. 아래와 같이 입력하면 ansible-client001에 사전 정의된 변수를 볼 수 있습니다. </p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ vagrant ssh ansible-server
$ ans -m setup 192.168.1.1
localhost | SUCCESS => {
    "ansible_facts": {
        "ansible_all_ipv4_addresses": [
            "192.168.1.10",
            "10.0.2.15"
        ],
        "ansible_all_ipv6_addresses": [
            "fe80::a00:27ff:fe75:8f4",
            "fe80::5054:ff:fe8a:fee6"
        ],
        "ansible_apparmor": {
            "status": "disabled"
        },
        "ansible_architecture": "x86_64",
        "ansible_bios_date": "12/01/2006",
        "ansible_bios_version": "VirtualBox",
        "ansible_cmdline": {
            "BOOT_IMAGE": "/boot/vmlinuz-3.10.0-957.12.2.el7.x86_64",
            "LANG": "en_US.UTF-8",
            "biosdevname": "0",
            "console": "ttyS0,115200n8",
            "crashkernel": "auto",
            "elevator": "noop",
            "net.ifnames": "0",
            "no_timer_check": true,
            "ro": true,
            "root": "UUID=8ac075e3-1124-4bb6-bef7-a6811bf8b870"
        },
        ............. 생략
}</pre>



<p class="wp-block-paragraph">nginx 설치시엔 ansible_pkg_mgr(패키지 매니져) 변수를 사용할 것인데 해당 변수를 검색하면 yum 인것을 확인 할 수 있습니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ ans -m setup 192.168.1.1 | grep ansible_pkg_mgr
"ansible_pkg_mgr": "yum"</pre>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"><p><strong>gather facts를 사용하는 이유는 여러가지 운영체제에 동일한 애플리케이션을 설치할때 OS마다 다른 명령어나 용어를 사용하게 되는데 이것을 ansible에서 한가지로 통일해 관리하기 위함입니다. </strong></p></blockquote>



<p class="wp-block-paragraph">Ubuntu에서 ansible_pkg_mgr를 조회하면 &#8220;apt&#8221;로 조회되는것을 확인할 수 있습니다.</p>



<h3 class="wp-block-heading">nginx 설치</h3>



<p class="wp-block-paragraph">ansible 환경이 구성되었으므로 ansible-server에 접속하여 클라이언트 서버에 설치할 nginx playbook을 작성합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ vagrant ssh ansible-server</pre>



<h4 class="wp-block-heading">install_webserver.yml 작성</h4>



<p class="wp-block-paragraph">hosts에 webservers라고 지정하면 /etc/ansible/hosts의 내용을 참고하여 ansible-client001(192.168.1.1)서버에 nginx가 설치됩니다. become: yes로 설정하면 명령어를 sudo로 실행합니다. 작업(tasks)은 순서대로 다음과 같이 진행됩니다.</p>



<ul class="wp-block-list"><li>epel 저장소를 최신으로 업데이트(state=latest) </li><li>nginx 설치(state=present)</li><li>nginx 시작(state=started)합니다.</li></ul>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
- name: install nginx on the client
  hosts: webservers
  become: yes
  
  tasks:
      - name: install epel-release
        action: "{{ ansible_pkg_mgr }} name=epel-release state=latest"
      - name: install nginx web server
        action: "{{ ansible_pkg_mgr }} name=nginx state=present"
      - name: start nginx web server
        service: name=nginx state=started</pre>



<h4 class="wp-block-heading">yum module</h4>



<p class="wp-block-paragraph">{{ ansible_pkg_mgr }}은 centos의 경우 yum 모듈을 이용하게 되고 다음 링크에서 자세한 내용을 확인 할 수 있습니다. yum 모듈의 경우 아래와 같은 state를 사용할 수 있습니다.</p>



<p class="wp-block-paragraph"><a href="https://docs.ansible.com/ansible/latest/modules/yum_module.html" target="_blank" rel="noreferrer noopener" aria-label=" (새탭으로 열기)">https://docs.ansible.com/ansible/latest/modules/yum_module.html</a></p>



<h5 class="wp-block-heading"><span class="has-inline-color has-vivid-cyan-blue-color">설치 관련 state</span></h5>



<ul class="wp-block-list"><li>present, installed &#8211; 둘다 같은 의미로 사용합니다. 패키지를 설치합니다.</li><li>latest &#8211; 설치되어있어도 최신 버전이 아닌 경우 지정된 패키지를 업데이트 합니다.</li></ul>



<h5 class="wp-block-heading"><span class="has-inline-color has-vivid-cyan-blue-color">삭제관련 state</span></h5>



<ul class="wp-block-list"><li>absent, removed  &#8211; 둘다 같은 의미로 사용됩니다. 지정한 패키지를 삭제합니다.</li></ul>



<h4 class="wp-block-heading">service module</h4>



<p class="wp-block-paragraph">service 모듈은 다음 링크에서 자세한 내용을 확인할 수 있고. 아래와 같은 state를 사용할 수 있습니다.</p>



<p class="wp-block-paragraph"><a href="https://docs.ansible.com/ansible/latest/modules/service_module.html" target="_blank" rel="noreferrer noopener" aria-label=" (새탭으로 열기)">https://docs.ansible.com/ansible/latest/modules/service_module.html</a></p>



<ul class="wp-block-list"><li><span class="has-inline-color has-vivid-cyan-blue-color"><strong>started </strong></span>&#8211; 서비스를 시작합니다. 필요한 경우만 동작합니다.</li><li><span class="has-inline-color has-vivid-cyan-blue-color"><strong>stopped </strong></span>&#8211; 서비스를 종료합니다. 필요한 경우만 동작합니다.</li><li><span class="has-inline-color has-vivid-cyan-blue-color"><strong>restarted </strong></span>&#8211; 항상 서비스를 재시작 합니다.</li><li><span class="has-inline-color has-vivid-cyan-blue-color"><strong>reloaded</strong></span> &#8211; 서비스 실행을 중단하지 않고 변경된 설정만 적용합니다.</li></ul>



<h4 class="wp-block-heading">playbook 명령으로 nginx 설치</h4>



<p class="wp-block-paragraph">anp(ansible-playbook) 명령을 실행하면 task가 실행됩니다. 우선 syntax-check 옵션으로 playbook 문법 유효성을 체크하고 list-hosts 옵션을 통해 적용될 클라이언트를 확인한 후에 playbook을 실행합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ anp --syntax-check install_webserver.yml

playbook: install_webserver.yml
$ anp --list-hosts install_webserver.yml

playbook: install_webserver.yml

  play #1 (webservers): webservers	TAGS: []
    pattern: [u'webservers']
    hosts (1):
      192.168.1.1
$ anp install_webserver.yml

PLAY [install nginx on the client] *****************************************************************************************************************************

TASK [Gathering Facts] *****************************************************************************************************************************************
ok: [192.168.1.1]

TASK [install epel-release] ************************************************************************************************************************************
changed: [192.168.1.1]

TASK [install nginx web server] ********************************************************************************************************************************
changed: [192.168.1.1]

TASK [start nginx web server] **********************************************************************************************************************************
changed: [192.168.1.1]

PLAY RECAP *****************************************************************************************************************************************************
192.168.1.1                : ok=4    changed=3    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0</pre>



<h4 class="wp-block-heading">nginx 설치 확인</h4>



<p class="wp-block-paragraph">Vagrant에서 ansible-client001의 80포트를 로컬 PC의 60081포트로 forwarded_port 해두어 로컬 PC의 브라우저에서 localhost:60081로 접속하여 아래와 같은 화면을 확인할 수 있습니다.</p>



<figure class="wp-block-image is-resized"><img loading="lazy" decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2019/10/ansible_nginx.png" alt="" class="wp-image-7628" width="793" height="280" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2019/10/ansible_nginx.png 1057w, https://www.daddyprogrammer.org/wp-content/uploads/2019/10/ansible_nginx-1024x361.png 1024w, https://www.daddyprogrammer.org/wp-content/uploads/2019/10/ansible_nginx-768x271.png 768w, https://www.daddyprogrammer.org/wp-content/uploads/2019/10/ansible_nginx-150x53.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2019/10/ansible_nginx-300x106.png 300w, https://www.daddyprogrammer.org/wp-content/uploads/2019/10/ansible_nginx-696x246.png 696w" sizes="auto, (max-width: 793px) 100vw, 793px" /></figure>



<h4 class="wp-block-heading">nginx 삭제</h4>



<h4 class="wp-block-heading">remove_webserver.yml 작성</h4>



<p class="wp-block-paragraph">install task와 내용은 별반 다르지 않습니다. state=absent로 지정하면 적용된 내용이 삭제 처리됩니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
- name: Remove nginx to ansible client
  hosts: webservers
  become: yes
  
  tasks:
      - name: remove epel-release
        action: "{{ ansible_pkg_mgr }} name=epel-release state=absent"
        
      - name: remove nginx
        action: "{{ ansible_pkg_mgr }} name=nginx state=absent"</pre>



<p class="wp-block-paragraph">작성한 내용을 playbook 명령으로 실행하여 nginx가 삭제되는지 확인 합니다. 처리가 완료된후 localhost:60081에 다시 접속해보면 Page Not Found를 확인할 수 있습니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ anp --syntax-check remove_webserver.yml

playbook: remove_webserver.yml
$ anp remove_webserver.yml
PLAY [Remove nginx to ansible client] **************************************************************************************************************************

TASK [Gathering Facts] *****************************************************************************************************************************************
ok: [192.168.1.1]

TASK [remove epel-release] *************************************************************************************************************************************
changed: [192.168.1.1]

TASK [remove nginx] ********************************************************************************************************************************************
changed: [192.168.1.1]

PLAY RECAP *****************************************************************************************************************************************************
192.168.1.1                : ok=3    changed=2    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0</pre>



<h3 class="wp-block-heading">Role을 이용한 ansible 구조 개선</h3>



<p class="wp-block-paragraph">ansible에서는 role이라고 하여 표준화된 구성 방식을 제공합니다. role을 사용하면 각각의 역할별로 디렉토리를 구조화하고 task 및 handler를 자동으로 로드할 수 있습니다. 그리고 정해진 형식대로 작성되기 때문에 다른 유저에게 쉽게 공유할 수 있습니다.</p>



<p class="wp-block-paragraph">role을 이용하여 nginx 설치/삭제를 개선해 보겠습니다. 아래와 같이 ansible-galaxy 명령어를 이용하면 정해진 role 구조를 자동으로 생성할 수 있습니다. <br><br>이전에 약어를 등록하였기 때문에 ang로 ang init [role이름] 명령을 실행하면 자동으로 디렉토리 구조 및 파일이 생성 됩니다. 이전 장에서 tree 패키지를 설치하였기 때문에 다음과 같이 생성된 디렉토리 구조를 확인할 수 있습니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ mkdir roles
$ cd roles
$ ang init nginx
- nginx was created successfully
$ $ tree nginx
nginx
├── README.md
├── defaults
│   └── main.yml
├── files
├── handlers
│   └── main.yml
├── meta
│   └── main.yml
├── tasks
│   └── main.yml
├── templates
├── tests
│   ├── inventory
│   └── test.yml
└── vars
    └── main.yml</pre>



<h4 class="wp-block-heading">각 디렉토리의 역할</h4>



<ul class="wp-block-list"><li><strong><span class="has-inline-color has-vivid-cyan-blue-color">tasks&nbsp;</span></strong>&#8211;&nbsp;role에&nbsp;의해&nbsp;실행될&nbsp;주요&nbsp;작업&nbsp;목록을&nbsp;포함하고 있습니다.&nbsp;지금까지&nbsp;작성했던&nbsp;yml들이&nbsp;tasks에&nbsp;들어간다고 보면 됩니다.<br><strong><span class="has-inline-color has-vivid-cyan-blue-color">defaults&nbsp;</span></strong>&#8211;&nbsp;우선순위가&nbsp;낮은&nbsp;기본&nbsp;변수&nbsp;집합이&nbsp;들어갑니다.&nbsp;보통&nbsp;공용으로&nbsp;사용하는&nbsp;변수를&nbsp;세팅합니다.<br><strong><span class="has-inline-color has-vivid-cyan-blue-color">files&nbsp;</span></strong>&#8211;&nbsp;role로&nbsp;배포할 수 있는&nbsp;파일이&nbsp;들어&nbsp;있습니다.&nbsp;role을&nbsp;구성하는&nbsp;동안&nbsp;클라이언트로&nbsp;보내야 하는&nbsp;파일이&nbsp;들어&nbsp;있습니다.<br><strong><span class="has-inline-color has-vivid-cyan-blue-color">handlers&nbsp;</span></strong>&#8211;&nbsp;role&nbsp;또는&nbsp;role&nbsp;외부에서&nbsp;사용될&nbsp;수 있는&nbsp;핸들러가&nbsp;위치하고&nbsp;있습니다.<br><strong><span class="has-inline-color has-vivid-cyan-blue-color">meta&nbsp;</span></strong>&#8211;&nbsp;role에&nbsp;대한&nbsp;메타&nbsp;데이터를&nbsp;정의합니다.&nbsp;기본적으로&nbsp;role&nbsp;종속성을&nbsp;설정하는&nbsp;파일이&nbsp;포함되어&nbsp;있습니다.&nbsp;작성자,&nbsp;지원&nbsp;플랫폼,&nbsp;종속성과&nbsp;같은&nbsp;role의&nbsp;메타&nbsp;데이터를&nbsp;포함합니다.<br><strong><span class="has-inline-color has-vivid-cyan-blue-color">templates&nbsp;</span></strong>&#8211;&nbsp;role&nbsp;구성시&nbsp;수정을&nbsp;지원하는&nbsp;파일&nbsp;템플릿이&nbsp;위치합니다.&nbsp;템플릿을&nbsp;만들&nbsp;때&nbsp;Jinja2&nbsp;템플릿&nbsp;언어를&nbsp;사용하여&nbsp;작성하며&nbsp;조건에 따라 유동적으로&nbsp;내용이&nbsp;변경되야 하는&nbsp;파일을&nbsp;만들 수&nbsp;있습니다.<br><span class="has-inline-color has-vivid-cyan-blue-color"><strong>vars</strong></span>&nbsp;&#8211;&nbsp;변수&nbsp;집합이&nbsp;저장됩니다.&nbsp;defaults에 설정된 변수 보다&nbsp;우선순위가&nbsp;높게&nbsp;적용됩니다.</li></ul>



<h4 class="wp-block-heading">기존 nginx 설치/삭제 작업 playbook을 tasks 하위로 이동</h4>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ cp install_webserver.yml ./roles/nginx/tasks/install.yml
$ cp remove_webserver.yml ./roles/nginx/tasks/remove.yml</pre>



<h4 class="wp-block-heading">tasks 하위 내용만 남기고 삭제</h4>



<ul class="wp-block-list"><li>roles/nginx/tasks/install.yml</li></ul>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
  - name: install epel-release
    action: "{{ ansible_pkg_mgr }} name=epel-release state=latest"
  - name: install nginx web server
    action: "{{ ansible_pkg_mgr }} name=nginx state=present"
  - name: start nginx web server
    service: name=nginx state=started</pre>



<ul class="wp-block-list"><li>roles/nginx/tasks/remove.yml</li></ul>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
  - name: remove epel-release
    action: "{{ ansible_pkg_mgr }} name=epel-release state=absent"
  - name: remove nginx
    action: "{{ ansible_pkg_mgr }} name=nginx state=absent"</pre>



<h4 class="wp-block-heading">task를 실행하는 playbook 생성</h4>



<ul class="wp-block-list"><li>roles/nginx/install_webserver.yml</li></ul>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
   - hosts: webservers
     become: yes

     tasks:
        - include: tasks/install.yml</pre>



<ul class="wp-block-list"><li>roles/nginx/remove_webserver.yml</li></ul>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
   - hosts: webservers
     become: yes

     tasks:
        - include: tasks/remove.yml</pre>



<h4 class="wp-block-heading">playbook 실행</h4>



<p class="wp-block-paragraph">role을 실행하면 기존과 동일하게 동작하는 것을 확인할 수 있습니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ anp install_webserver.yml
PLAY [webservers] **********************************************************************************************************************************************

TASK [Gathering Facts] *****************************************************************************************************************************************
ok: [192.168.1.1]

TASK [install epel-release] ************************************************************************************************************************************
changed: [192.168.1.1]

TASK [install nginx web server] ********************************************************************************************************************************
changed: [192.168.1.1]

TASK [start nginx web server] **********************************************************************************************************************************
changed: [192.168.1.1]

PLAY RECAP *****************************************************************************************************************************************************
192.168.1.1                : ok=4    changed=3    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0

$ anp remove_webserver.yml
PLAY [webservers] **********************************************************************************************************************************************

TASK [Gathering Facts] *****************************************************************************************************************************************
ok: [192.168.1.1]

TASK [remove epel-release] *************************************************************************************************************************************
changed: [192.168.1.1]

TASK [remove nginx] ********************************************************************************************************************************************
changed: [192.168.1.1]

PLAY RECAP *****************************************************************************************************************************************************
192.168.1.1                : ok=3    changed=2    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0</pre>



<h4 class="wp-block-heading">디렉토리 구조</h4>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ tree nginx
nginx
|-- README.md
|-- defaults
|   `-- main.yml
|-- files
|-- handlers
|   `-- main.yml
|-- install_webserver.yml
|-- meta
|   `-- main.yml
|-- remove_webserver.yml
|-- tasks
|   |-- install.yml
|   |-- main.yml
|   `-- remove.yml
|-- templates
|-- tests
|   |-- inventory
|   `-- test.yml
`-- vars
    `-- main.yml</pre>



<h4 class="wp-block-heading">Handler로 기능 분리</h4>



<p class="wp-block-paragraph">handler를 이용하면 작업을 분리하여 재사용 할수 있습니다. handlers 디렉토리 하위의 main.yml에  nginx start, restart task를 작성합니다.</p>



<ul class="wp-block-list"><li>roles/nginx/handlers/main.yml</li></ul>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">- name: start nginx web server
  action: service name=nginx state=started
- name: restart nginx web server
  action: service name=nginx state=restarted</pre>



<ul class="wp-block-list"><li>roles/nginx/install_webserver.yml에 handlers 경로를 include 합니다</li></ul>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
   - hosts: webservers
     become: yes

     tasks:
        - include: tasks/install.yml

     handlers:
        - include: handlers/main.yml</pre>



<ul class="wp-block-list"><li>roles/nginx/task/install.yml에 notify로 handler를 호출하여 nginx를 시작하도록 추가합니다.</li></ul>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
  - name: install epel-release
    action: "{{ ansible_pkg_mgr }} name=epel-release state=latest"
  - name: install nginx web server
    action: "{{ ansible_pkg_mgr }} name=nginx state=present"
    notify:
       - start nginx web server</pre>



<p class="wp-block-paragraph">ansible playbook명령으로 nginx를 다시 설치해봅니다. log에 &#8216;RUNNING HANDLER&#8217;라고 표시되며 handler가 작동되는 것을 확인할 수 있습니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ anp install_webserver.yml
PLAY [webservers] **********************************************************************************************************************************************

TASK [Gathering Facts] *****************************************************************************************************************************************
ok: [192.168.1.1]

TASK [install epel-release] ************************************************************************************************************************************
changed: [192.168.1.1]

TASK [install nginx web server] ********************************************************************************************************************************
changed: [192.168.1.1]

RUNNING HANDLER [start nginx web server] ***********************************************************************************************************************
changed: [192.168.1.1]

PLAY RECAP *****************************************************************************************************************************************************
192.168.1.1                : ok=4    changed=3    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0</pre>



<h4 class="wp-block-heading">Template 사용하기</h4>



<p class="wp-block-paragraph">어떤&nbsp;애플리케이션을&nbsp;설치하든&nbsp;설정값의&nbsp;수정이&nbsp;빈번하게&nbsp;발생합니다.&nbsp;설정값을&nbsp;default로&nbsp;사용하는&nbsp;경우도&nbsp;있지만&nbsp;대부분&nbsp;값을&nbsp;상황에 맞게 튜닝하여&nbsp;사용하는&nbsp;경우가&nbsp;대부분입니다.&nbsp;이와&nbsp;같은 경우에&nbsp;nginx가&nbsp;설치된&nbsp;각&nbsp;서버에&nbsp;접속하여&nbsp;conf&nbsp;파일&nbsp;내용을&nbsp;수정할 수도&nbsp;있겠지만&nbsp;template화&nbsp;하면&nbsp;ansible을&nbsp;통해&nbsp;설정을 빠르게 수정하고 모든&nbsp;클라이언트에&nbsp;쉽게&nbsp;적용할&nbsp;수&nbsp;있습니다.</p>



<p class="wp-block-paragraph">template이란&nbsp;정형화된&nbsp;틀이라고&nbsp;생각하면&nbsp;됩니다.&nbsp;ansible에서는&nbsp;template&nbsp;디렉터리&nbsp;하위에&nbsp;template&nbsp;파일들을&nbsp;위치시키는데&nbsp;jinja2&nbsp;형식의&nbsp;파일이며. j2&nbsp;확장자를&nbsp;붙입니다.&nbsp;공통으로&nbsp;클라이언트에&nbsp;배포되어야&nbsp;하는&nbsp;파일들(&nbsp;예를 들면&nbsp;conf&nbsp;파일등&nbsp;)을&nbsp;template화&nbsp;하는 것이&nbsp;적합합니다.&nbsp;또한&nbsp;jinja2&nbsp;파일은&nbsp;변경되는&nbsp;값을&nbsp;변수로&nbsp;지정하여&nbsp;외부에서&nbsp;주입할 수&nbsp;있도록&nbsp;되어있으므로,&nbsp;파일&nbsp;내용을&nbsp;유동적으로&nbsp;생성할&nbsp;수&nbsp;있습니다.</p>



<p class="wp-block-paragraph">자세한 내용은 아래 링크에서 확인 할 수 있습니다.</p>



<p class="wp-block-paragraph"><a rel="noreferrer noopener" aria-label=" (새탭으로 열기)" href="https://docs.ansible.com/ansible/latest/user_guide/playbooks_templating.html" target="_blank">https://docs.ansible.com/ansible/latest/user_guide/playbooks_templating.html</a></p>



<h4 class="wp-block-heading">nginx.conf 파일을 jinja2 파일로 변경</h4>



<p class="wp-block-paragraph">nginx 설치 후 변경을 가하지 않은 상태의 nginx.conf 파일의 원본 내용은 다음과 같습니다.</p>



<ul class="wp-block-list"><li>/etc/nginx/nginx.conf</li></ul>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group=""># For more information on configuration, see:
#   * Official English Documentation: http://nginx.org/en/docs/
#   * Official Russian Documentation: http://nginx.org/ru/docs/

user nginx;
worker_processes auto;
error_log /var/log/nginx/error.log;
pid /run/nginx.pid;

# Load dynamic modules. See /usr/share/nginx/README.dynamic.
include /usr/share/nginx/modules/*.conf;

events {
    worker_connections 1024;
}

http {
    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

    access_log  /var/log/nginx/access.log  main;

    sendfile            on;
    tcp_nopush          on;
    tcp_nodelay         on;
    keepalive_timeout   65;
    types_hash_max_size 2048;

    include             /etc/nginx/mime.types;
    default_type        application/octet-stream;

    # Load modular configuration files from the /etc/nginx/conf.d directory.
    # See http://nginx.org/en/docs/ngx_core_module.html#include
    # for more information.
    include /etc/nginx/conf.d/*.conf;

    server {
        listen       80 default_server;
        listen       [::]:80 default_server;
        server_name  _;
        root         /usr/share/nginx/html;

        # Load configuration files for the default server block.
        include /etc/nginx/default.d/*.conf;

        location / {
        }

        error_page 404 /404.html;
            location = /40x.html {
        }

        error_page 500 502 503 504 /50x.html;
            location = /50x.html {
        }
    }

# Settings for a TLS enabled server.
#
#    server {
#        listen       443 ssl http2 default_server;
#        listen       [::]:443 ssl http2 default_server;
#        server_name  _;
#        root         /usr/share/nginx/html;
#
#        ssl_certificate "/etc/pki/nginx/server.crt";
#        ssl_certificate_key "/etc/pki/nginx/private/server.key";
#        ssl_session_cache shared:SSL:1m;
#        ssl_session_timeout  10m;
#        ssl_ciphers HIGH:!aNULL:!MD5;
#        ssl_prefer_server_ciphers on;
#
#        # Load configuration files for the default server block.
#        include /etc/nginx/default.d/*.conf;
#
#        location / {
#        }
#
#        error_page 404 /404.html;
#            location = /40x.html {
#        }
#
#        error_page 500 502 503 504 /50x.html;
#            location = /50x.html {
#        }
#    }
}</pre>



<p class="wp-block-paragraph">ansible-server에 구성한 roles/nginx/template 하위에 nginx.conf.j2를 작성합니다. 유동적인 값에 대해서는 {{ 변수명 }}으로 처리를 합니다. 아래에서는 간단한 실습을 위해 변수의 대체만 사용했지만 if문을 이용한 조건 주입이나 for문을 이용한 반복 처리도 가능합니다. 필요한 부분만 남기고 유동적인 부분을 변수화 시킨 jinja2 파일 내용은 다음과 같습니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ vi ./roles/nginx/templates/nginx.conf.j2
user nginx;
worker_processes {{ nginx.processor_count }};
error_log /var/log/nginx/error.log;
pid /run/nginx.pid;

include /usr/share/nginx/modules/*.conf;

events {
    worker_connections {{ nginx.max_worker_connection }};
}

http {
    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

    access_log  {{ nginx.log_dir }}/{{ nginx.access_log_name }}  main;

    sendfile            on;
    tcp_nopush          on;
    tcp_nodelay         on;
    keepalive_timeout   65;
    types_hash_max_size 2048;

    include             /etc/nginx/mime.types;
    default_type        application/octet-stream;

    include /etc/nginx/conf.d/*.conf;

    server {
        listen       {{ nginx.port }} default_server;
        listen       [::]:{{ nginx.port }} default_server;
        server_name  _;
        root         /usr/share/nginx/html;

        # Load configuration files for the default server block.
        include /etc/nginx/default.d/*.conf;

        location / {
        }

        error_page 404 /404.html;
            location = /40x.html {
        }

        error_page 500 502 503 504 /50x.html;
            location = /50x.html {
        }
    }
}</pre>



<p class="wp-block-paragraph">template에 사용한 변수에 적용할 값은 vars 디렉토리 하위의 main.yml에 작성합니다.</p>



<ul class="wp-block-list"><li>roles/nginx/vars/main.yml</li></ul>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
# vars file for nginx
nginx:
    processor_count: 30
    max_worker_connection: 512
    log_dir: /var/log/nginx
    access_log_name: access.log
    port: 80</pre>



<p class="wp-block-paragraph">변수를 사용할 수 있도록 playbook에 vars/main.yml을 include 합니다.</p>



<ul class="wp-block-list"><li>roles/nginx/install_webserver.yml</li></ul>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
   - hosts: webservers
     become: yes
     vars_files:
        - vars/main.yml
     tasks:
        - include: tasks/install.yml
     handlers:
        - include: handlers/main.yml</pre>



<p class="wp-block-paragraph">install task에 nginx.conf.j2의 내용을 client서버에 적용하도록 액션을 추가합니다.</p>



<ul class="wp-block-list"><li>roles/nginx/tasks/install.yml</li></ul>



<pre class="EnlighterJSRAW" data-enlighter-language="yaml" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">---
  - name: install epel-release
    action: "{{ ansible_pkg_mgr }} name=epel-release state=latest"
  - name: install nginx web server
    action: "{{ ansible_pkg_mgr }} name=nginx state=present"
  - name: write nginx.conf
    action: template src=templates/nginx.conf.j2 dest=/etc/nginx/nginx.conf
    notify:
       - start nginx web server</pre>



<h4 class="wp-block-heading">playbook 테스트</h4>



<p class="wp-block-paragraph">기존에 nginx가 설치되어있다면 삭제 후 재설치 합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ anp remove_webserver.yml
PLAY [webservers] **********************************************************************************************************************************************

TASK [Gathering Facts] *****************************************************************************************************************************************
ok: [192.168.1.1]

TASK [remove epel-release] *************************************************************************************************************************************
changed: [192.168.1.1]

TASK [remove nginx] ********************************************************************************************************************************************
changed: [192.168.1.1]

PLAY RECAP *****************************************************************************************************************************************************
192.168.1.1                : ok=3    changed=2    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0

$ anp install_webserver.yml
PLAY [webservers] **********************************************************************************************************************************************

TASK [Gathering Facts] *****************************************************************************************************************************************
ok: [192.168.1.1]

TASK [install epel-release] ************************************************************************************************************************************
changed: [192.168.1.1]

TASK [install nginx web server] ********************************************************************************************************************************
changed: [192.168.1.1]

TASK [write nginx.conf] ****************************************************************************************************************************************
changed: [192.168.1.1]

RUNNING HANDLER [start nginx web server] ***********************************************************************************************************************
changed: [192.168.1.1]

PLAY RECAP *****************************************************************************************************************************************************
192.168.1.1                : ok=5    changed=4    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0</pre>



<p class="wp-block-paragraph">클라이언트 서버에 접속하여 nginx.conf의 내용을 확인해 봅니다. ansible로 적용한 내용이 반영된 것을 확인할 수 있습니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ vagrant ssh ansible-client001
$ cat /etc/nginx/nginx.conf
user nginx;
worker_processes 30;
error_log /var/log/nginx/error.log;
pid /run/nginx.pid;

include /usr/share/nginx/modules/*.conf;

events {
    worker_connections 512;
}

http {
    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

    access_log  /var/log/nginx/access.log  main;

    sendfile            on;
    tcp_nopush          on;
    tcp_nodelay         on;
    keepalive_timeout   65;
    types_hash_max_size 2048;

    include             /etc/nginx/mime.types;
    default_type        application/octet-stream;

    include /etc/nginx/conf.d/*.conf;

    server {
        listen       80 default_server;
        listen       [::]:80 default_server;
        server_name  _;
        root         /usr/share/nginx/html;

        # Load configuration files for the default server block.
        include /etc/nginx/default.d/*.conf;

        location / {
        }

        error_page 404 /404.html;
            location = /40x.html {
        }

        error_page 500 502 503 504 /50x.html;
            location = /50x.html {
        }
    }
}</pre>



<p class="wp-block-paragraph">실습을&nbsp;통해&nbsp;nginx&nbsp;애플리케이션&nbsp;설치를&nbsp;자동화해보았습니다.&nbsp;한번&nbsp;작성한&nbsp;playbook은&nbsp;재사용이&nbsp;가능합니다.&nbsp;실무에서는&nbsp;간단하게&nbsp;hosts 파일의 inventory에&nbsp;클라이언트&nbsp;서버를&nbsp;추가하는 것만으로&nbsp;다수의&nbsp;서버에&nbsp;nginx 애플리케이션을&nbsp;손쉽게 구축할&nbsp;수&nbsp;있습니다.</p>



<p class="wp-block-paragraph">실습시 사용한 소스는 아래 github에서 확인할 수 있습니다.</p>



<p class="wp-block-paragraph"><a href="https://github.com/codej99/ansible-web-application.git" target="_blank" rel="noreferrer noopener" aria-label=" (새탭으로 열기)">https://github.com/codej99/ansible-web-application.git</a></p>
<p>The post <a href="https://www.daddyprogrammer.org/post/7615/ansible-nginx-roles-handler-template-vars/">Ansible을 이용한 시스템 구성관리(2) – ansible로 nginx 설치 &#8211; roles, handler, template, vars</a> appeared first on <a href="https://www.daddyprogrammer.org">아빠프로그래머의 좌충우돌 개발하기!</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.daddyprogrammer.org/post/7615/ansible-nginx-roles-handler-template-vars/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		
		<series:name><![CDATA[Ansible 알아보기]]></series:name>
	</item>
		<item>
		<title>Spring websocket chatting server(6) – Nginx+Certbot 무료 SSL인증서로 WSS(Websocket Secure) 구축하기</title>
		<link>https://www.daddyprogrammer.org/post/5353/spring-websocket-chatting-server-ngix-certbot-ssl-websocket-secure/</link>
					<comments>https://www.daddyprogrammer.org/post/5353/spring-websocket-chatting-server-ngix-certbot-ssl-websocket-secure/#comments</comments>
		
		<dc:creator><![CDATA[happydaddy]]></dc:creator>
		<pubDate>Fri, 21 Jun 2019 01:43:16 +0000</pubDate>
				<category><![CDATA[Websocket]]></category>
		<category><![CDATA[Nginx]]></category>
		<category><![CDATA[WSS]]></category>
		<category><![CDATA[Websocket secure]]></category>
		<guid isPermaLink="false">http://3.36.120.4/?p=5353</guid>

					<description><![CDATA[<p>이번&#160;장에서는&#160;지금까지&#160;만든&#160;웹소켓&#160;채팅 서버를&#160;실제&#160;서버에&#160;올려보고&#160;SSL을&#160;적용하는&#160;실습을&#160;진행해보겠습니다.&#160;실습&#160;내용은&#160;다음과&#160;같습니다. 서버에서 Executable Jar로 Websocket 채팅서버를 실행 CertBot을 설치하여 무료 SSL 인증서 발급 Nginx의 ReverseProxy를 이용한 WSS( WebsocketSecure ) 구축 실습 환경 Instance &#8211; AWS Freetier EC2 OS &#8211; Amazone Linux AMI(CentOs) Java &#8211; jdk8 ~ jdk11 필요 요구 사항 이번 실습은 실제 도메인을 필요로 합니다. 필자는 godaddy(https://kr.godaddy.com/)에서 daddyprogrammer.org 도메인을 이미 구매하여 사용하고 있는 [&#8230;]</p>
<p>The post <a href="https://www.daddyprogrammer.org/post/5353/spring-websocket-chatting-server-ngix-certbot-ssl-websocket-secure/">Spring websocket chatting server(6) – Nginx+Certbot 무료 SSL인증서로 WSS(Websocket Secure) 구축하기</a> appeared first on <a href="https://www.daddyprogrammer.org">아빠프로그래머의 좌충우돌 개발하기!</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">이번&nbsp;장에서는&nbsp;지금까지&nbsp;만든&nbsp;웹소켓&nbsp;채팅 서버를&nbsp;실제&nbsp;서버에&nbsp;올려보고&nbsp;SSL을&nbsp;적용하는&nbsp;실습을&nbsp;진행해보겠습니다.&nbsp;실습&nbsp;내용은&nbsp;다음과&nbsp;같습니다.</p>



<ul class="wp-block-list"><li><span class="has-inline-color has-vivid-cyan-blue-color"><strong>서버에서 Executable Jar로 Websocket 채팅서버를 실행</strong></span></li><li><span class="has-inline-color has-vivid-cyan-blue-color"><strong>CertBot을 설치하여 무료 SSL 인증서 발급</strong></span></li><li><span class="has-inline-color has-vivid-cyan-blue-color"><strong>Nginx의 ReverseProxy를 이용한 WSS( WebsocketSecure ) 구축</strong></span></li></ul>



<h3 class="wp-block-heading">실습 환경</h3>



<ul class="wp-block-list"><li> Instance &#8211; AWS Freetier EC2</li><li>OS &#8211; Amazone Linux AMI(CentOs)</li><li>Java &#8211;  jdk8 ~ jdk11</li></ul>



<h3 class="wp-block-heading">필요 요구 사항</h3>



<p class="wp-block-paragraph">이번 실습은 실제 도메인을 필요로 합니다. 필자는 godaddy(https://kr.godaddy.com/)에서 daddyprogrammer.org 도메인을 이미 구매하여 사용하고 있는 상태이므로 서브도메인 <strong><span class="has-inline-color has-vivid-purple-color">chat.daddyprogrammer.org</span></strong>을 생성하여 실습하겠습니다. </p>



<p class="wp-block-paragraph">Godaddy DNS설정에서 채팅 서브 도메인을 추가로 설정하였습니다. 적용에는 시간이 필요하므로 시간이 좀 흐른 후에 해당 도메인으로 접속이 되는지 확인합니다.</p>



<figure class="wp-block-image is-resized"><img loading="lazy" decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2019/06/goddaddy.png" alt="" class="wp-image-5357" width="623" height="185" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2019/06/goddaddy.png 831w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/goddaddy-768x228.png 768w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/goddaddy-150x45.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/goddaddy-300x89.png 300w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/goddaddy-696x207.png 696w" sizes="auto, (max-width: 623px) 100vw, 623px" /></figure>



<h3 class="wp-block-heading">서버에서 Executable Jar로 Websocket 채팅서버를 실행</h3>



<h4 class="wp-block-heading">git 설치 </h4>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ sudo yum install git</pre>



<h4 class="wp-block-heading">채팅 프로젝트 clone</h4>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ mkdir chat
$ cd chat
$ git clone https://github.com/codej99/websocket-chat-server.git
$ ls
websocket-chat-server</pre>



<h4 class="wp-block-heading">빌드 &amp; Executable Jar 생성</h4>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ cd websocket-chat-server
$ ./gradlew bootJar
BUILD SUCCESSFUL in 13s
3 actionable tasks: 3 up-to-date
$ cd build/libs/
$ ls
chat-0.0.1-SNAPSHOT.jar</pre>



<h4 class="wp-block-heading">채팅 서버 실행</h4>



<p class="wp-block-paragraph">필자는 자체 구축한 redis서버가 있어 3번째 방법으로 서버를 실행하였습니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">// 내장 redis로 띄우는 경우
$ java -jar chat-0.0.1-SNAPSHOT.jar
// 포트를 기본 8080이 아닌 다른 포트로 띄우고 싶은경우
$ java -jar -Dserver.port=8100 chat-0.0.1-SNAPSHOT.jar
// redis를 자체 구축하고 application-alpha.yml에 redis 접속정보를 설정한경우 
$ java -jar -Dspring.profiles.active=alpha chat-0.0.1-SNAPSHOT.jar</pre>



<h3 class="wp-block-heading">CertBot을 설치하여 무료 SSL 인증서 발급</h3>



<p class="wp-block-paragraph">CertBot 프로그램을 이용하면 Let&#8217;s Encrypt에서 무료로 SSL 인증서를 발급 받을 수 있습니다.</p>



<h4 class="wp-block-heading">Certbot 설치</h4>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ sudo yum install certbot</pre>



<h4 class="wp-block-heading">인증서 발급</h4>



<p class="wp-block-paragraph">$ sudo certbot certonly &#8211;standalone -m 이메일주소 -d 인증서 적용할 도메인</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ sudo certbot certonly --standalone -m happydaddy@naver.com -d chat.daddyprogrammer.org
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Please read the Terms of Service at
https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must
agree in order to register with the ACME server at
https://acme-v02.api.letsencrypt.org/directory
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(A)gree/(C)ancel: A 입력후 엔터

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Would you be willing to share your email address with the Electronic Frontier
Foundation, a founding partner of the Let's Encrypt project and the non-profit
organization that develops Certbot? We'd like to send you email about our work
encrypting the web, EFF news, campaigns, and ways to support digital freedom.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(Y)es/(N)o: Y 입력 후 엔터
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for chat.daddyprogrammer.org
Waiting for verification...
Cleaning up challenges

IMPORTANT NOTES:
- Congratulations! Your certificate and chain have been saved at:
   /etc/letsencrypt/live/chat.daddyprogrammer.org/fullchain.pem
   Your key file has been saved at:
   /etc/letsencrypt/live/chat.daddyprogrammer.org/privkey.pem
   Your cert will expire on 2019-09-18. To obtain a new or tweaked
   version of this certificate in the future, simply run certbot
   again. To non-interactively renew *all* of your certificates, run
   "certbot renew"
- Your account credentials have been saved in your Certbot
   configuration directory at /etc/letsencrypt. You should make a
   secure backup of this folder now. This configuration directory will
   also contain certificates and private keys obtained by Certbot so
   making regular backups of this folder is ideal.
- If you like Certbot, please consider supporting our work by:

   Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
   Donating to EFF:                    https://eff.org/donate-le


Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Please read the Terms of Service at
https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must
agree in order to register with the ACME server at
https://acme-v02.api.letsencrypt.org/directory
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(A)gree/(C)ancel: A

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Would you be willing to share your email address with the Electronic Frontier
Foundation, a founding partner of the Let's Encrypt project and the non-profit
organization that develops Certbot? We'd like to send you email about our work
encrypting the web, EFF news, campaigns, and ways to support digital freedom.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(Y)es/(N)o: Y
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for chat.daddyprogrammer.org
Waiting for verification...
Cleaning up challenges

IMPORTANT NOTES:
- Congratulations! Your certificate and chain have been saved at:
   /etc/letsencrypt/live/chat.daddyprogrammer.org/fullchain.pem
   Your key file has been saved at:
   /etc/letsencrypt/live/chat.daddyprogrammer.org/privkey.pem
   Your cert will expire on 2019-09-18. To obtain a new or tweaked
   version of this certificate in the future, simply run certbot
   again. To non-interactively renew *all* of your certificates, run
   "certbot renew"
- Your account credentials have been saved in your Certbot
   configuration directory at /etc/letsencrypt. You should make a
   secure backup of this folder now. This configuration directory will
   also contain certificates and private keys obtained by Certbot so
   making regular backups of this folder is ideal.
- If you like Certbot, please consider supporting our work by:

   Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
   Donating to EFF:                    https://eff.org/donate-le</pre>



<h4 class="wp-block-heading">발급받은 인증서 확인</h4>



<p class="wp-block-paragraph">생성 위치 : /etc/letsencrypt/live/도메인명/</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ sudo ls /etc/letsencrypt/live/chat.daddyprogrammer.org/
README	cert.pem  chain.pem  fullchain.pem  privkey.pem</pre>



<h3 class="wp-block-heading">Nginx의 ReverseProxy를 이용한 WSS( WebsocketSecure ) 구축</h3>



<p class="wp-block-paragraph">이제 위에서 생성한 도메인과 SSL인증서를 바탕으로 WSS ReverseProxy 서버를 구축해보겠습니다.</p>



<h4 class="wp-block-heading">nginx 설치</h4>



<p class="wp-block-paragraph">다음 링크의 내용을 참고하여 nginx를 설치합니다.<br><a href="http://www.daddyprogrammer.org/post/2348/aws-ec2-install-nginx-mariadb/" target="_blank" rel="noreferrer noopener" aria-label="http://www.daddyprogrammer.org/post/2348/aws-ec2-install-nginx-mariadb/ (새탭으로 열기)">http://www.daddyprogrammer.org/post/2348/aws-ec2-install-nginx-mariadb/</a></p>



<h4 class="wp-block-heading">nginx ReverseProxy 및 SSL+ Websocket 설정 추가</h4>



<p class="wp-block-paragraph">nginx.conf 파일을 열어 ReverseProxy 및 SSL+ Websocket 설정을 추가합니다.</p>



<p class="wp-block-paragraph">http 설정 하위에 두개의 server{} server{} 구문으로 이루어져 있으며 첫번째 server구문 안에는 http(80)으로 요청이 들어올때의 설정입니다. https를 이용할 것이므로 http로 들어와도 return 301 ~~ 구문을 이용하여 https 주소로 리다이렉트 되도록 합니다.</p>



<p class="wp-block-paragraph">두번째 server구문 안에는 https(443)으로 들어올때의 설정이 담겨 있습니다. server_name에는 도메인 주소를 적습니다. ssl_certificate에는 위에서 발급받은 무료 도메인 인증서의 위치를 설정합니다.</p>



<p class="wp-block-paragraph">location / 안에서는 실제로 요청을 어떻게 처리할지 내용을 적습니다. nginx는 reverse_proxy서버의 역할을 해야하므로 관련 내용을 적습니다. proxy_pass http://localhost:8080; 설정의 경우 websocket 서버를 8080이 아닌 다른 포트로 띄운경우 수정해야 합니다. Websocket의 경우 http 프로토콜로 접속한 후에 Websocket 프로토콜로 Upgrade하는 과정을 거치는데 해당 내용을 처리하기 위해 nginx에 설정을 추가해줍니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">http {
    // 생략 ..........

    server {
        listen       80 default_server;
        listen       [::]:80 default_server;
        server_name  chat.daddyprogrammer.org;
        root         /usr/share/nginx/html;

        location / {
                 return 301 https://chat.daddyprogrammer.org$request_uri;
        }
    }

    server {
        listen 443 ssl;
        server_name chat.daddyprogrammer.org;

        ssl_certificate /etc/letsencrypt/live/chat.daddyprogrammer.org/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/chat.daddyprogrammer.org/privkey.pem;

        location / {
                proxy_set_header    HOST $http_host;
                proxy_set_header    X-Real-IP $remote_addr;
                proxy_set_header    X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header    X-Forwarded-Proto $scheme;
                proxy_set_header    X-NginX-Proxy true;
                proxy_pass http://localhost:8080; // 요청을 웹소켓 서버로 전달. 위에서 websocket서버를 8080이 아닌 다른 포트로 띄운경우 수정합니다.
                proxy_redirect  off;
                charset utf-8;

                # WebSocket support
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "upgrade";
        }
    }
    // 생략 ..........
}                                                                                                                                           
</pre>



<p class="wp-block-paragraph">설정이 모두 끝났습니다. nginx를 띄우고 서버를 테스트 해보겠습니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="" data-enlighter-highlight="" data-enlighter-linenumbers="" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">// nginx.conf 설정파일 문법 오류 검사
$ sudo nginx -t 
nginx: configuration file /etc/nginx/nginx.conf test is successful
$ sudo service nginx start</pre>



<h4 class="wp-block-heading">EC2 Security Group Inbound port 설정</h4>



<p class="wp-block-paragraph">AWS를 이용한다면 기본적으로 EC2 서버의 외부 접근이 막혀있으므로, 접속을 허용하기 위해 Inbound 80, 443 port를 개방해 두어야 합니다.  </p>



<h4 class="wp-block-heading">테스트</h4>



<p class="wp-block-paragraph">http://chat.daddyprogrammer.org를 접속합니다. 자동으로 https로 리다이렉트 됨을 확인할 수 있습니다.<br>인증서를 확인해보면 Let&#8217;s Encrypt에서 발급받은 인증서 내용을 확인 할 수 있습니다.</p>



<figure class="wp-block-image size-large is-resized"><img loading="lazy" decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2020/04/wss_1.png" alt="" class="wp-image-9919" width="796" height="427" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2020/04/wss_1.png 1592w, https://www.daddyprogrammer.org/wp-content/uploads/2020/04/wss_1-1024x549.png 1024w, https://www.daddyprogrammer.org/wp-content/uploads/2020/04/wss_1-768x412.png 768w, https://www.daddyprogrammer.org/wp-content/uploads/2020/04/wss_1-1536x824.png 1536w, https://www.daddyprogrammer.org/wp-content/uploads/2020/04/wss_1-150x80.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2020/04/wss_1-300x161.png 300w, https://www.daddyprogrammer.org/wp-content/uploads/2020/04/wss_1-696x373.png 696w, https://www.daddyprogrammer.org/wp-content/uploads/2020/04/wss_1-783x420.png 783w" sizes="auto, (max-width: 796px) 100vw, 796px" /></figure>



<figure class="wp-block-image is-resized"><img loading="lazy" decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_2.png" alt="" class="wp-image-5391" width="477" height="527" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_2.png 477w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_2-150x166.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_2-300x331.png 300w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_2-380x420.png 380w" sizes="auto, (max-width: 477px) 100vw, 477px" /></figure>



<p class="wp-block-paragraph">로그인 후 채팅 테스트를 해봅니다. 아래 이미지는 휴대폰을 통해 채팅을 진행한 화면입니다. 반대편에서는 웹브라우저를 통해 접속하여 채팅을 진행하였습니다. 문제없이 채팅이 진행되는것을 확인할 수 있습니다.</p>



<figure class="wp-block-image is-resized"><img loading="lazy" decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2019/06/phone_chat-946x2048.png" alt="" class="wp-image-5393" width="237" height="512" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2019/06/phone_chat-946x2048.png 946w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/phone_chat-473x1024.png 473w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/phone_chat-768x1663.png 768w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/phone_chat-709x1536.png 709w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/phone_chat-150x325.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/phone_chat-696x1507.png 696w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/phone_chat-194x420.png 194w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/phone_chat.png 1125w" sizes="auto, (max-width: 237px) 100vw, 237px" /></figure>



<p class="wp-block-paragraph">그렇다면 websocket이 wss로 접속되었다는것을 어떻게 알수 있을까요? 브라우저의 Network접속 로그를 보면 다음과 같은 내용을 확인할 수 있습니다. 리퀘스트 URL이 wss로 시작하고 Status Code는 101임을 확인 할수 있습니다.</p>



<figure class="wp-block-image is-resized"><img loading="lazy" decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_upgrade_1.png" alt="" class="wp-image-5395" width="1113" height="819" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_upgrade_1.png 1113w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_upgrade_1-1024x754.png 1024w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_upgrade_1-768x565.png 768w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_upgrade_1-150x110.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_upgrade_1-300x221.png 300w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_upgrade_1-696x512.png 696w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_upgrade_1-571x420.png 571w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_upgrade_1-80x60.png 80w" sizes="auto, (max-width: 1113px) 100vw, 1113px" /></figure>



<p class="wp-block-paragraph">Status Code 101의 의미는 다음과 같습니다. 아래 내용에 따르면 https로 접속은 하되 접속후에 Upgrade를 통해 WSS프로토콜로 변경 한다는 것을 알 수 있습니다.</p>



<figure class="wp-block-image is-resized"><img loading="lazy" decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_upgrade_2.png" alt="" class="wp-image-5396" width="707" height="692" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_upgrade_2.png 707w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_upgrade_2-150x147.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_upgrade_2-300x294.png 300w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_upgrade_2-696x681.png 696w, https://www.daddyprogrammer.org/wp-content/uploads/2019/06/wss_upgrade_2-429x420.png 429w" sizes="auto, (max-width: 707px) 100vw, 707px" /></figure>



<p class="wp-block-paragraph">이번 실습에서는 도메인에 SSL인증서를 적용하여 보안이 적용된 Websocket(WSS)을 구축해 보았습니다. 기능 추가를 통해 안전한 채팅 메시지 교환이 가능하게 되었습니다!!</p>
<p>The post <a href="https://www.daddyprogrammer.org/post/5353/spring-websocket-chatting-server-ngix-certbot-ssl-websocket-secure/">Spring websocket chatting server(6) – Nginx+Certbot 무료 SSL인증서로 WSS(Websocket Secure) 구축하기</a> appeared first on <a href="https://www.daddyprogrammer.org">아빠프로그래머의 좌충우돌 개발하기!</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.daddyprogrammer.org/post/5353/spring-websocket-chatting-server-ngix-certbot-ssl-websocket-secure/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		
		<series:name><![CDATA[웹소켓(websocket)으로 채팅서버 만들기]]></series:name>
	</item>
		<item>
		<title>SpringBoot2로 Rest api 만들기(12) – Deploy &#038; Nginx 연동 &#038; 무중단 배포 하기</title>
		<link>https://www.daddyprogrammer.org/post/2445/springboot2-blue-green-deploy-nginx/</link>
					<comments>https://www.daddyprogrammer.org/post/2445/springboot2-blue-green-deploy-nginx/#comments</comments>
		
		<dc:creator><![CDATA[happydaddy]]></dc:creator>
		<pubDate>Tue, 30 Apr 2019 07:25:04 +0000</pubDate>
				<category><![CDATA[SpringBoot]]></category>
		<category><![CDATA[Deploy]]></category>
		<category><![CDATA[배포]]></category>
		<category><![CDATA[Nginx]]></category>
		<category><![CDATA[Blue green deploy]]></category>
		<guid isPermaLink="false">http://3.36.120.4/?p=2445</guid>

					<description><![CDATA[<p>이번 장에서는 SpringBoot 프로젝트를 실제 AWS EC2 서버에 배포하고 Nginx와 연동하여 서버를 실행해 보는 실습을 하겠습니다. 이번 실습에서는 AWS에 EC2서버를 ssh로 접속할 준비가 되어있거나 Spring을 배포할 서버가 한대는 준비되어 있어야 합니다. AWS는 신규가입시 1년동안 무료로 서버를 제공하므로 이번 기회에 한번 가입해서 사용해 보는것도 좋습니다. EC2서버가 준비되었다면 톰켓과 연동할 Nginx를 설치합니다. 설치하는김에 Mysql(mariadb)도 같이 설치 합니다. [&#8230;]</p>
<p>The post <a href="https://www.daddyprogrammer.org/post/2445/springboot2-blue-green-deploy-nginx/">SpringBoot2로 Rest api 만들기(12) – Deploy &#038; Nginx 연동 &#038; 무중단 배포 하기</a> appeared first on <a href="https://www.daddyprogrammer.org">아빠프로그래머의 좌충우돌 개발하기!</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">이번 장에서는 SpringBoot 프로젝트를 실제 AWS EC2 서버에 배포하고 Nginx와 연동하여 서버를 실행해 보는 실습을 하겠습니다. 이번 실습에서는 AWS에 EC2서버를 ssh로 접속할 준비가 되어있거나 Spring을 배포할 서버가 한대는 준비되어 있어야 합니다. AWS는 신규가입시 1년동안 무료로 서버를 제공하므로 이번 기회에 한번 가입해서 사용해 보는것도 좋습니다.</p>



<p class="wp-block-paragraph">EC2서버가 준비되었다면 톰켓과 연동할 Nginx를 설치합니다. 설치하는김에 Mysql(mariadb)도 같이 설치 합니다.</p>



<figure class="wp-block-embed-wordpress wp-block-embed is-type-wp-embed is-provider-아빠프로그래머의-좌충우돌-개발하기"><div class="wp-block-embed__wrapper">
<blockquote class="wp-embedded-content" data-secret="B4C5ExnnVP"><a href="https://www.daddyprogrammer.org/post/2348/aws-ec2-install-nginx-mariadb/">AWS EC2 &#8211; install nginx, mariadb</a></blockquote><iframe loading="lazy" class="wp-embedded-content" sandbox="allow-scripts" security="restricted"  title="&#8220;AWS EC2 &#8211; install nginx, mariadb&#8221; &#8212; 아빠프로그래머의 좌충우돌 개발하기!" src="https://www.daddyprogrammer.org/post/2348/aws-ec2-install-nginx-mariadb/embed/#?secret=A2jyfaD3IT#?secret=B4C5ExnnVP" data-secret="B4C5ExnnVP" width="600" height="338" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe>
</div></figure>



<p class="wp-block-paragraph">SpringBoot는 실행가능한 jar파일을 생성하여 자체적으로 웹 컨테이너를 구동할 수 있습니다. 별다른 설정을 하지 않으면 Embeded Tomcat으로 구동됩니다.</p>



<h2 class="wp-block-heading">Executable jar 생성</h2>



<p class="wp-block-paragraph">프로젝트 루트 디렉터리에서 bootJar task를 실행하면 ./build/libs 아래에 실행가능한 jar가 생성됩니다. </p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ ./gradlew bootJar</pre>



<h2 class="wp-block-heading">Executable jar 서버 업로드</h2>



<p class="wp-block-paragraph">scp 명령을 이용하여 ec2 서버에 jar파일을 전송 합니다. scp(secure copy)는 ssh와 같은 프로토콜을 사용하며 원격지로 안전하게 파일을 복사하는 명령입니다. 리눅스나 Mac에서는 scp를 바로 쓸 수 있지만 윈도에서는 Linux bash shell을 먼저 활성화해야 합니다. 다행히도 윈도10 최신 버전에서 쉽게 Ubuntu Linux를 사용할 수 있도록 제공하고 있으니 아래 링크를 참고하여 Linux shell 환경을 구축합니다.</p>



<figure class="wp-block-embed-wordpress wp-block-embed is-type-wp-embed is-provider-아빠프로그래머의-좌충우돌-개발하기"><div class="wp-block-embed__wrapper">
<blockquote class="wp-embedded-content" data-secret="E4jB9ziaM0"><a href="https://www.daddyprogrammer.org/post/1489/windows10-ubuntu-bash-shell/">Windows10 OpenSSH 클라이언트 활성화, 개발자 모드 + Ubuntu Linux 활성화</a></blockquote><iframe loading="lazy" class="wp-embedded-content" sandbox="allow-scripts" security="restricted"  title="&#8220;Windows10 OpenSSH 클라이언트 활성화, 개발자 모드 + Ubuntu Linux 활성화&#8221; &#8212; 아빠프로그래머의 좌충우돌 개발하기!" src="https://www.daddyprogrammer.org/post/1489/windows10-ubuntu-bash-shell/embed/#?secret=oLc9nPHC5N#?secret=E4jB9ziaM0" data-secret="E4jB9ziaM0" width="600" height="338" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe>
</div></figure>



<p class="wp-block-paragraph">scp 명령어로 서버에 jar 파일을 업로드 합니다.</p>



<p class="wp-block-paragraph">$ scp -i 서버인증서.pem 프로젝트경로/build/libs/api-0.0.1-SNAPSHOT.jar ec2-user@서버IP:~/업로드경로    </p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ scp -i AwsKeyPair.pem /Users/happydaddy/git/SpringRestApi/build/libs/api-0.0.1-SNAPSHOT.jar ec2-user@10.20.30.40:~/api                                                            </pre>



<h2 class="wp-block-heading">Tomcat 실행</h2>



<p class="wp-block-paragraph">업로드한 Jar파일은 Tomcat서버를 내장하고 있습니다. java -jar 명령으로 서버를 띄울수 있습니다. nohup과 마지막의 &amp;를 붙이면 Tomcat이 background process로 실행됩니다. Jar실행시 Port 설정, Profile설정, JVM 옵션 설정 등도 같이 해줍니다. </p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ nohup java -jar -Dserver.port=8083 -Dspring.profiles.active=alpha -XX:MaxMetaspaceSize=128m -XX:+UseG1GC -Xss1024k -Xms256m -Xmx384m -Dfile.encoding=UTF-8 api-0.0.1-SNAPSHOT.jar &amp;</pre>



<h2 class="wp-block-heading">Nginx 설정 수정 및 실행</h2>



<p class="wp-block-paragraph">Nginx의 ReverseProxy기능으로 Tomcat의 8083 port를 80으로 서비스 할 수 있도록 세팅하고 nginx를 reload 합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ sudo vim nginx.conf
// server 설정 위에 upstream 추가
upstream tomcat {
        ip_hash;
        server 127.0.0.1:8083;
}
// location 내용 수정
location / {
        proxy_set_header    HOST $http_host;
        proxy_set_header    X-Real-IP $remote_addr;
        proxy_set_header    X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header    X-Forwarded-Proto $scheme;
        proxy_set_header    X-NginX-Proxy true;
        proxy_pass http://tomcat;
        proxy_redirect  off;
        charset utf-8;
}
$ sudo nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
$ sudo service nginx reload</pre>



<h2 class="wp-block-heading">웹 페이지 확인</h2>



<p class="wp-block-paragraph">정상적으로 설정하였다면 다음과 같은 화면을 볼수 있습니다.<br>http://서버IP/swagger-ui.html</p>



<figure class="wp-block-image is-resized"><img loading="lazy" decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2019/05/swagger.png" alt="" class="wp-image-2688" width="675" height="218" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2019/05/swagger.png 900w, https://www.daddyprogrammer.org/wp-content/uploads/2019/05/swagger-768x247.png 768w, https://www.daddyprogrammer.org/wp-content/uploads/2019/05/swagger-150x48.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2019/05/swagger-300x97.png 300w, https://www.daddyprogrammer.org/wp-content/uploads/2019/05/swagger-696x224.png 696w" sizes="auto, (max-width: 675px) 100vw, 675px" /></figure>



<h2 class="wp-block-heading">Gracefully shutdown</h2>



<p class="wp-block-paragraph">executable jar로 웹 컨테이너를 띄운후에 업데이트등의 이슈로 서버를 재시작해야 하는 경우가 있습니다. 이런 경우엔 좀더 주의가 필요합니다. 왜냐하면 서버를 그냥 종료시켜 버리면 서버에서 열심히 처리중이었던 작업을 응답 못하고 종료해 버리기 때문입니다. 이런점을 고려하여 처리중인 작업이 있다면 잘 마무리하고 종료시키는 작업이 필요합니다. 이것을 Gracefully Shutdown이라고 부릅니다. Linux에서는 작업을 종료시킬때 몇가지 옵션을 제공하는데요. kill 명령에 -TERM 혹은 -15를 옵션으로 주면 서버를 바로 종료시키지 않고 서버에게 종료 요청을 보내게 됩니다. 해당 서버는 TERMINATE 요청을 받으면 현재 처리중인 작업을 모두 마무리하고 서버를 종료시키게 됩니다.</p>



<h3 class="wp-block-heading">Terminate 요청을 처리할 수 있도록 GracefulShutdown 작성</h3>



<p class="wp-block-paragraph">다음과 같이 GracefulShutdown을 작성합니다. 해당 코드는 실행중인 작업을 마치고 종료하는 내용을 담고 있으며 30초안에 종료되지 않으면 강제로 작업을 종료하도록 처리하고 있습니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="java" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">package com.rest.api.config;

import lombok.extern.slf4j.Slf4j;
import org.apache.catalina.connector.Connector;
import org.springframework.boot.web.embedded.tomcat.TomcatConnectorCustomizer;
import org.springframework.context.ApplicationListener;
import org.springframework.context.event.ContextClosedEvent;

import java.util.concurrent.Executor;
import java.util.concurrent.ThreadPoolExecutor;
import java.util.concurrent.TimeUnit;

@Slf4j
public class GracefulShutdown implements TomcatConnectorCustomizer, ApplicationListener&lt;ContextClosedEvent> {

    private static final int TIMEOUT = 30;

    private volatile Connector connector;

    @Override
    public void customize(Connector connector) {
        this.connector = connector;
    }

    @Override
    public void onApplicationEvent(ContextClosedEvent event) {
        this.connector.pause();
        Executor executor = this.connector.getProtocolHandler().getExecutor();
        if (executor instanceof ThreadPoolExecutor) {
            try {
                ThreadPoolExecutor threadPoolExecutor = (ThreadPoolExecutor) executor;
                threadPoolExecutor.shutdown();
                if (!threadPoolExecutor.awaitTermination(TIMEOUT, TimeUnit.SECONDS)) {
                    log.warn("Tomcat thread pool did not shut down gracefully within "
                            + TIMEOUT + " seconds. Proceeding with forceful shutdown");

                    threadPoolExecutor.shutdownNow();

                    if (!threadPoolExecutor.awaitTermination(TIMEOUT, TimeUnit.SECONDS)) {
                        log.error("Tomcat thread pool did not terminate");
                    }
                } else {
                    log.info("Tomcat thread pool has been gracefully shutdown");
                }
            } catch (InterruptedException ex) {
                Thread.currentThread().interrupt();
            }
        }
    }
}</pre>



<h3 class="wp-block-heading">Boot 설정에 GracefulShutdown 추가</h3>



<p class="wp-block-paragraph">위에서 작성한 GracefulShutdown을 SpringRestApiApplication 설정에 추가합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="java" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">@SpringBootApplication
public class SpringRestApiApplication {
    public static void main(String[] args) {
        SpringApplication.run(SpringRestApiApplication.class, args);
    }

// 다른 설정 생략

    @Bean
    public GracefulShutdown gracefulShutdown() {
        return new GracefulShutdown();
    }

    @Bean
    public ConfigurableServletWebServerFactory webServerFactory(final GracefulShutdown gracefulShutdown) {
        TomcatServletWebServerFactory factory = new TomcatServletWebServerFactory();
        factory.addConnectorCustomizers(gracefulShutdown);
        return factory;
    }
}</pre>



<h3 class="wp-block-heading">테스트 코드 작성</h3>



<p class="wp-block-paragraph">오랫동안 지속되는 작업을 하나 만듭니다. 아래는 10초의 딜레이를 주고 결과를 내보내는 코드입니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="java" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">@GetMapping("/helloworld/long-process")
@ResponseBody
public String pause() throws InterruptedException {
    Thread.sleep(10000);
    return "Process finished";
}</pre>



<h3 class="wp-block-heading">종료 테스트</h3>



<p class="wp-block-paragraph">서버에 해당 내용을 배포하기 전에 수행중인 작업이 있는 상태에서 서버를 종료시키면 다음과 같은 오류를 맞이하게 됩니다.</p>



<figure class="wp-block-image is-resized"><img loading="lazy" decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2019/05/nginx_error.png" alt="" class="wp-image-2752" width="602" height="308" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2019/05/nginx_error.png 802w, https://www.daddyprogrammer.org/wp-content/uploads/2019/05/nginx_error-768x394.png 768w, https://www.daddyprogrammer.org/wp-content/uploads/2019/05/nginx_error-150x77.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2019/05/nginx_error-300x154.png 300w, https://www.daddyprogrammer.org/wp-content/uploads/2019/05/nginx_error-696x357.png 696w" sizes="auto, (max-width: 602px) 100vw, 602px" /></figure>



<p class="wp-block-paragraph">GracefullyShutdown 내용을 빌드 후 재 배포 한다음 다시 종료 테스트를 하면 다음과 같이 작업을 마무리 한후에 서버가 종료 됩니다. <br>http://서버IP/helloworld/long-process</p>



<figure class="wp-block-image is-resized"><img loading="lazy" decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2019/05/gracefullyshutdown-1.png" alt="" class="wp-image-2756" width="574" height="117" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2019/05/gracefullyshutdown-1.png 1148w, https://www.daddyprogrammer.org/wp-content/uploads/2019/05/gracefullyshutdown-1-1024x209.png 1024w, https://www.daddyprogrammer.org/wp-content/uploads/2019/05/gracefullyshutdown-1-768x157.png 768w, https://www.daddyprogrammer.org/wp-content/uploads/2019/05/gracefullyshutdown-1-150x31.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2019/05/gracefullyshutdown-1-300x61.png 300w, https://www.daddyprogrammer.org/wp-content/uploads/2019/05/gracefullyshutdown-1-696x142.png 696w" sizes="auto, (max-width: 574px) 100vw, 574px" /></figure>



<p class="wp-block-paragraph">Was로그에서도 정상적으로 종료된것을 확인 할 수 있습니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">2019-05-02 12:01:38.821  INFO 3333 --- [Thread-2] com.rest.api.config.GracefulShutdown     : Tomcat thread pool has been gracefully shutdown</pre>



<h2 class="wp-block-heading">무중단 배포(Blue / Green Deployment)</h2>



<p class="wp-block-paragraph">지금까지의 방식은 배포시 Was가 완전히 로딩 될때까지 서비스가 불가능한 이슈가 있습니다. 배포시에도 서비스가 가능한 무중단 배포로 수정 해보도록 하겠습니다.</p>



<p class="wp-block-paragraph">무중단 배포 관련한 내용은 아래 링크를 참고 하였습니다.<br><a href="https://jojoldu.tistory.com/267">https://jojoldu.tistory.com/267</a></p>



<h3 class="wp-block-heading">Spring Actuator 추가</h3>



<p class="wp-block-paragraph">springboot에서는 actuator를 제공하여 서비스의 상태 정보를 실시간으로 모니터링 할수 있도록  제공하고 있습니다. build.gradle에 아래 내용을 추가합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">implementation 'org.springframework.boot:spring-boot-starter-actuator'</pre>



<h3 class="wp-block-heading">SpringSecurity 설정 수정</h3>



<p class="wp-block-paragraph">actuator가 제공하는 endpoint에 접근할수 있도록 &#8220;/actuator/health&#8221;를 permitAll() 처리합니다. actuator가 제공하는 모니터링 endpoint는 이외에도 많으니 아래 링크를 참고해 보시기 바랍니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="java" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">.antMatchers(HttpMethod.GET, "/helloworld/**","/actuator/health").permitAll()</pre>



<figure class="wp-block-embed-wordpress wp-block-embed is-type-wp-embed is-provider-baeldung"><div class="wp-block-embed__wrapper">
<blockquote class="wp-embedded-content" data-secret="efta8k6R0J"><a href="https://www.baeldung.com/spring-boot-actuators">Spring Boot Actuator</a></blockquote><iframe loading="lazy" class="wp-embedded-content" sandbox="allow-scripts" security="restricted"  title="&#8220;Spring Boot Actuator&#8221; &#8212; Baeldung" src="https://www.baeldung.com/spring-boot-actuators/embed/#?secret=efta8k6R0J" data-secret="efta8k6R0J" width="600" height="338" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe>
</div></figure>



<p class="wp-block-paragraph">서버를 스타트 하고 localhost:8080/actuator/health에 접근하면 현재 서버 상태를 json으로 볼 수 있습니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">{"status":"UP"}</pre>



<h3 class="wp-block-heading">배포 환경 구성</h3>



<p class="wp-block-paragraph">배포를 위한 환경을 구성합니다. 로컬 PC또는 배포를 위해 마련한 서버에서 배포 디렉터리를 생성하고 git repository를 clone 받습니다. AwsFreetierKeyPair.pem은 AWS EC2에 ssh로 접속하기위해 사용되는 인증서라고 보면 됩니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ mkdir deploy
$ cd deploy
$ git clone https://github.com/codej99/SpringRestApi.git
$ ls
AwsFreetierKeyPair.pem  SpringRestApi</pre>



<h3 class="wp-block-heading">배포 대상 서버리스트 작성</h3>



<p class="wp-block-paragraph">배포는 여러서버에 배포 될 수 있으므로 관련 서버 주소를 담은 파일을 하나 만듭니다.<br>환경별로 서버 리스트가 나뉘어질 수 있으므로 파일명에 _{환경명}으로 생성합니다.  </p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ vi server_alpha.list
123.456.789.100
234.567.333.444</pre>



<h3 class="wp-block-heading">배포 shell script 작성</h3>



<p class="wp-block-paragraph">deploy.sh 란 이름으로 파일을 하나 만들고 실행 권한을 부여합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ touch deploy.sh
$ chmod +x deploy.sh</pre>



<p class="wp-block-paragraph">배포는 다음과 같은 순서로 진행됩니다.</p>



<ul class="wp-block-list"><li>타겟 서버에 배포 디렉토리(/home/ec2-user/app/dist)를 생성합니다.</li><li>scp 명령어로 로컬 build 디렉터리에서 jar파일을 타겟서버 배포 디렉터리로 전송합니다.</li><li>전송한 jar파일에 대한 심볼릭 링크를 생성합니다. 배포시 버전에 따른 Jar파일명을 하나의 이름으로만 관리함으로써 Jar실행시 최신 버전의 Jar파일 이름을 알아내야할 필요가 없게 해주는 용도입니다.</li><li>현재 실행중인 서버를 조회합니다. 8083이 띄워져 있으면 새로 업데이트된 jar파일로 8084로 서버를 한대 더 실행합니다.</li><li>신규 서버 스타트가 완료되면(health체크를 5초마다 실행) 기존에 실행되고 있던 서버는 종료합니다. 위에서 Gracefully shutdown을 적용했으므로 연결되어있던 커넥션은 모두 처리되고 서버가 종료됩니다. </li><li>서버리스트에 여러개의 서버가 나열되어 있었다면 위의 작업이 서버수만큼 반복됩니다.</li></ul>



<h3 class="wp-block-heading">deploy.sh</h3>



<p class="wp-block-paragraph">deploy shell은 인자로 profile을 받습니다. $ ./deploy.sh alpha<br>위에서 생성한 배포 환경의 디렉토리로 PROJECT관련 정보를 세팅합니다.<br>PROJECT_HOME은 배포에 필요한 여러가지 파일이나 정보를 모아두는 배포 홈 디렉터리 입니다.<br>SVR_LIST는 server_alpha.list파일을 읽어서 배포 대상 서버 리스트를 가져옵니다. <br>DEPLOY_PATH는 배포 대상 서버에 생성되는 디렉토리입니다. 각자의 환경에 맞게 변경합니다. AWS_ID도 환경에 맞게 변경합니다.<br>그외 현재 일자, JVM설정 옵션, PEM파일 위치 등을 세팅합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="shell" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">#!/bin/bash
PROFILE=$1                                                                                                                                       
PROJECT=SpringRestApi                                                                                                                             
PROJECT_HOME=/Users/happydaddy/deploy/${PROJECT}                                                                                                      
JAR_PATH=${PROJECT_HOME}/build/libs/api-0.0.1-SNAPSHOT.jar                                                                                       
SVR_LIST=server_${PROFILE}.list                                                                                                                   
SERVERS=`cat $SVR_LIST`                                                                                                                           
DEPLOY_PATH=/home/ec2-user/app                                                                                                                   
AWS_ID=ec2-user                             
DATE=`date +%Y-%m-%d-%H-%M-%S`        
JAVA_OPTS="-XX:MaxMetaspaceSize=128m -XX:+UseG1GC -Xss1024k -Xms128m -Xmx128m -Dfile.encoding=UTF-8"
PEM=AwsFreetierKeyPair.pem                                                                                                                       
PORT=8083                                                                                                             

echo Deploy Start                     
for server in $SERVERS; do                              
    echo Target server - $server
    # Target Server에 배포 디렉터리 생성           
    ssh -i $PEM $AWS_ID@$server "mkdir -p $DEPLOY_PATH/dist"                                                                                
    # Target Server에 jar 이동
    echo 'Executable Jar Copying...'
    scp -i $PEM $JAR_PATH $AWS_ID@$server:~/app/dist/$PROJECT-$DATE.jar
    # 이동한 jar파일의 바로가기(SymbolicLink)생성                             
    ssh -i $PEM $AWS_ID@$server "ln -Tfs $DEPLOY_PATH/dist/$PROJECT-$DATE.jar $DEPLOY_PATH/$PROJECT"      
    echo 'Executable Jar Copyed'
    # 현재 실행중인 서버 PID 조회
    runPid=$(ssh -i $PEM $AWS_ID@$server pgrep -f $PROJECT)
    if [ -z $runPid ]; then            
        echo "No servers are running"                             
    fi                                                                                                                                       
    # 현재 실행중인 서버의 포트를 조회. 추가로 실행할 서버의 포트 선정                              
    runPortCount=$(ssh -i $PEM $AWS_ID@$server ps -ef | grep $PROJECT | grep -v grep | grep $PORT | wc -l)
    if [ $runPortCount -gt 0 ]; then        
        PORT=8084                             
    fi                                                                                                                                                                     
    echo "Server $PORT Starting..."
    # 새로운 서버 실행
    ssh -i $PEM $AWS_ID@$server "nohup java -jar -Dserver.port=$PORT -Dspring.profiles.active=$PROFILE $JAVA_OPTS $DEPLOY_PATH/$PROJECT &lt; /dev/null > std.out 2> std.err &amp;"
    # 새롭게 실행한 서버의 health check
    echo "Health check $PORT"                             
    for retry in {1..10}
    do    
        health=$(ssh -i $PEM $AWS_ID@$server curl -s http://localhost:$PORT/actuator/health)                      
        checkCount=$(echo $health | grep 'UP' | wc -l)
        echo "Check count - $checkCount"    
        if [ $checkCount -ge 1 ]; then      
           echo "Server $PORT Started Normaly"                  
           # 기존 서버 Stop
           if [ $runPid -gt 0 ]; then             
                echo "Server $runPid Stopping..."           
                ssh -i $PEM $AWS_ID@$server "kill -TERM $runPid"
                sleep 5
                echo "Server $runPid Stopped"           
           fi
           break;                         
        fi                         
        sleep 5     
    done                   
done                      
echo Deploy End</pre>



<p class="wp-block-paragraph">위의 shell script를 실행하면 tomcat이 8083&lt;-&gt;8084로 전환되면서 실행되는 것을 확인할 수 있습니다.</p>



<h3 class="wp-block-heading">무중단 서비스를 위한 개선</h3>



<p class="wp-block-paragraph">Java 서블릿 컨테이너 기반의 프레임워크는 서버 구동 속도가 느리다는 단점을 가지고 있습니다. 그것은 서버를 띄우기 위한 시간이 꽤 걸린다는 것입니다. 다른 언어의 서버들에 비해  Java기반의 tomcat은 적어도 30초 이상의 서버 Startup 시간을 필요로 하므로 배포시엔 신중을 가해서 해야합니다. 이 시간 동안에는 서비스의 응답을 처리할 수 없으므로 추가적인 처리가 필요한데 여기에서 무중단 배포라는 용어가 나오게 되었습니다. 실습에서는 2개의 tomcat 인스턴스를 nginx의 설정에서 순간적으로 교체하는 방법으로 무중단을 구현할 것입니다.</p>



<p class="wp-block-paragraph">현재 nginx는 8083 port의 톰켓을 서비스하고 있는것으로 가정하고 순서는 다음과 같습니다.</p>



<ul class="wp-block-list"><li>8083 port가 실행중인 상태에서 최신버전의 Jar로 8084 port Was를 하나 더 실행합니다.</li><li>8084의 Startup이 완료되면 nginx 설정을 8084로 변경하여 실시간 반영합니다.</li><li>8083 Was는 종료(Gracefully Shutdown) 처리합니다.</li></ul>



<h3 class="wp-block-heading">Nginx에서 서비스할 서버 정보 파일 생성</h3>



<p class="wp-block-paragraph">/etc/nginx/conf.d에 service_addr.inc를 생성하고 다음 한줄을 추가합니다.<br>$service_addr이라는 환경변수를 추가하는 작업입니다.<br></p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">set $service_addr http://127.0.0.1:8083;</pre>



<h3 class="wp-block-heading">nginx.conf 수정</h3>



<p class="wp-block-paragraph">서비스 URL은 다이나믹하게 변경되어야 하므로 아래 내용은 삭제합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">upstream tomcat {
        ip_hash;
        server 127.0.0.1:8083;
}</pre>



<h3 class="wp-block-heading">service_addr.inc를 정보를 보도록 추가</h3>



<p class="wp-block-paragraph">include /etc/nginx/conf.d/service_addr.inc; 을 추가하여 서버 정보를 읽을수 있게 합니다. proxy_pass는 http://tomcat; -&gt; $service_addr;로 수정하여 service_addr.inc에서 설정한 환경 변수로 처리되도록  합니다.<br></p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">include /etc/nginx/conf.d/service_addr.inc;

location / {
     proxy_set_header    HOST $http_host;
     proxy_set_header    X-Real-IP $remote_addr;
     proxy_set_header    X-Forwarded-For $proxy_add_x_forwarded_for;
     proxy_set_header    X-Forwarded-Proto $scheme;
     proxy_set_header    X-NginX-Proxy true;
     proxy_pass $service_addr;
     proxy_redirect  off;
     charset utf-8;
}</pre>



<h3 class="wp-block-heading">배포 shell script 수정</h3>



<p class="wp-block-paragraph">8083, 8084 서버가 띄워져 있는 상태에서 nginx가 바라보는 was를 변경하기 위해 shell내용을 수정합니다. 기존 deploy.sh와 거의 동일하며 nignx의 was를 실시간으로 변경하는 내용이 추가되었습니다.</p>



<p class="wp-block-paragraph"># 새롭게 띄워진 Port의 정보로 service_addr.inc를 갱신합니다.<br>ssh -i $PEM $AWS_ID@$server &#8220;echo &#8216;set \$service_addr http://127.0.0.1:$PORT;&#8217; | sudo tee /etc/nginx/conf.d/service_addr.inc&#8221;<br> # nginx를 reload하여 설정 내용을 바로 반영합니다.              <br>ssh -i $PEM $AWS_ID@$server &#8220;sudo service nginx reload&#8221;</p>



<pre class="EnlighterJSRAW" data-enlighter-language="shell" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">#!/bin/bash
PROFILE=$1                                                                                                                                       
PROJECT=SpringRestApi                                                                                                                             
PROJECT_HOME=/Users/happydaddy/deploy/${PROJECT}                                                                                                     
JAR_PATH=${PROJECT_HOME}/build/libs/api-0.0.1-SNAPSHOT.jar                                                                                       
SVR_LIST=server_${PROFILE}.list                                                                                                                   
SERVERS=`cat $SVR_LIST`                                                                                                                           
DEPLOY_PATH=/home/ec2-user/app                                                                                                                   
AWS_ID=ec2-user                             
DATE=`date +%Y-%m-%d-%H-%M-%S`        
JAVA_OPTS="-XX:MaxMetaspaceSize=128m -XX:+UseG1GC -Xss1024k -Xms128m -Xmx128m -Dfile.encoding=UTF-8"
PEM=AwsFreetierKeyPair.pem                                                                                                                       
PORT=8083                                                                                                             

echo Deploy Start                     
for server in $SERVERS; do                              
    echo Target server - $server
    # Target Server에 배포 디렉터리 생성           
    ssh -i $PEM $AWS_ID@$server "mkdir -p $DEPLOY_PATH/dist"                                                                                
    # Target Server에 jar 이동
    echo 'Executable Jar Copying...'
    scp -i $PEM $JAR_PATH $AWS_ID@$server:~/app/dist/$PROJECT-$DATE.jar
    # 이동한 jar파일의 바로가기(SymbolicLink)생성                             
    ssh -i $PEM $AWS_ID@$server "ln -Tfs $DEPLOY_PATH/dist/$PROJECT-$DATE.jar $DEPLOY_PATH/$PROJECT"      
    # 현재 실행중인 서버 PID 조회
    runPid=$(ssh -i $PEM $AWS_ID@$server pgrep -f $PROJECT)
    if [ -z $runPid ]; then            
        echo "No servers are running"                             
    fi                                                                                                                                       
    # 현재 실행중인 서버의 포트를 조회. 추가로 실행할 서버의 포트 선정                              
    runPortCount=$(ssh -i $PEM $AWS_ID@$server ps -ef | grep $PROJECT | grep -v grep | grep $PORT | wc -l)
    if [ $runPortCount -gt 0 ]; then        
        PORT=8084                             
    fi                                                                                                                                                                     
    echo "Server $PORT Starting..."
    # 새로운 서버 실행
    ssh -i $PEM $AWS_ID@$server "nohup java -jar -Dserver.port=$PORT -Dspring.profiles.active=$PROFILE $JAVA_OPTS $DEPLOY_PATH/$PROJECT &lt; /dev/null > std.out 2> std.err &amp;"
    # 새롭게 실행한 서버의 health check
    echo "Health check $PORT"                             
    for retry in {1..10}
    do    
        health=$(ssh -i $PEM $AWS_ID@$server curl -s http://localhost:$PORT/actuator/health)                      
        checkCount=$(echo $health | grep 'UP' | wc -l)
        if [ $checkCount -ge 1 ]; then      
           echo "Server $PORT Started Normaly"                  
           # 기존 서버 Stop / Nginx 포트 변경 후 리스타트
           if [ $runPid -gt 0 ]; then             
                echo "Server $runPid Stop"           
                ssh -i $PEM $AWS_ID@$server "kill -TERM $runPid"
                sleep 5
                echo "Nginx Port Change"           
		ssh -i $PEM $AWS_ID@$server "echo 'set \$service_addr http://127.0.0.1:$PORT;' | sudo tee /etc/nginx/conf.d/service_addr.inc"
                echo "Nginx reload"           
		ssh -i $PEM $AWS_ID@$server "sudo service nginx reload"
           fi
           break;                         
	   else
	       echo "Check - false"
           fi                         
        sleep 5     
    done                   
    if [ $retry -eq 10 ]; then
	   echo "Deploy Fail"
    fi 
done                      
echo Deploy End</pre>



<p class="wp-block-paragraph">위의 shell을 반복으로 실행하면서 ec2의 프로세스를 확인해 봅니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ ./deploy.sh alpha
Deploy Start
Target server - 13.16.198.80
Executable Jar Copying...
api-0.0.1-SNAPSHOT.jar                                                                                        100%   45MB  11.2MB/s   00:04    
Executable Jar Copyed
Server 8084 Starting...
Health check 8084
Check count -        0
Check count -        0
Check count -        0
Check count -        0
Check count -        1
Server 8084 Started Normaly
Server 10191 Stopping...
Server 10191 Stopped
Deploy End</pre>



<p class="wp-block-paragraph">ec2의 로그를 보면 8083 port는 종료되고 8084 port가 실행되고 있음을 확인할 수 있습니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ ps -ef | grep SpringRestApi
ec2-user 10926     1 14 13:56 ?        00:00:19 java -jar -Dserver.port=8084 -Dspring.profiles.active=alpha -XX:MaxMetaspaceSize=128m -XX:+UseG1GC -Xss1024k -Xms128m -Xmx128m -Dfile.encoding=UTF-8 /home/ec2-user/app/SpringRestApi
ec2-user 11077  7590  0 13:58 pts/0    00:00:00 grep --color=auto SpringRestApi</pre>



<p class="wp-block-paragraph">다시 한번 배포를 실행합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ ./deploy.sh alpha
Deploy Start
Target server - 13.16.198.80
Executable Jar Copying...
api-0.0.1-SNAPSHOT.jar                                                                                        100%   45MB  11.2MB/s   00:04    
Executable Jar Copyed
Server 8083 Starting...
Health check 8083
Check count -        0
Check count -        0
Check count -        0
Check count -        0
Check count -        1
Server 8083 Started Normaly
Server 10926 Stopping...
Server 10926 Stopped
Deploy End</pre>



<p class="wp-block-paragraph">ec2의 로그를 보면 요번에는 8084 port가 종료되고 8083 port가 실행되고 있음을 확인할 수 있습니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ ps -ef | grep SpringRestApi
ec2-user 11173     1 18 14:00 ?        00:00:19 java -jar -Dserver.port=8083 -Dspring.profiles.active=alpha -XX:MaxMetaspaceSize=128m -XX:+UseG1GC -Xss1024k -Xms128m -Xmx128m -Dfile.encoding=UTF-8 /home/ec2-user/app/SpringRestApi
ec2-user 11336  7590  0 14:01 pts/0    00:00:00 grep --color=auto SpringRestApi</pre>



<p class="wp-block-paragraph">여기까지 무중단 배포를 구현하기 위한 절차를 실습해보았습니다. 다음 시간에는 이러한 절차를 Jenkins를 이용하여 좀 더 편리하게 사용할 수 있도록 변경하는 실습을 진행해보겠습니다.</p>



<p class="wp-block-paragraph">최신 소스는 GitHub 사이트를 참고해 주세요.<br><a href="https://github.com/codej99/SpringRestApi/tree/feature/gracefullyshutdown">https://github.com/codej99/SpringRestApi/tree/feature/gracefullyshutdown</a></p>



<p class="wp-block-paragraph">GitHub Repository를 import하여 Intellij 프로젝트를 구성하는 방법은 다음 포스팅을 참고해주세요.</p>



<figure class="wp-block-embed-wordpress wp-block-embed is-type-wp-embed is-provider-아빠프로그래머의-좌충우돌-개발하기"><div class="wp-block-embed__wrapper">
<blockquote class="wp-embedded-content" data-secret="SzZSjxeYl5"><a href="https://www.daddyprogrammer.org/post/1215/intellij-github-spring-gradle-project-import/">Intellij에서 Github의 Spring Gradle Project import 하기</a></blockquote><iframe loading="lazy" class="wp-embedded-content" sandbox="allow-scripts" security="restricted"  title="&#8220;Intellij에서 Github의 Spring Gradle Project import 하기&#8221; &#8212; 아빠프로그래머의 좌충우돌 개발하기!" src="https://www.daddyprogrammer.org/post/1215/intellij-github-spring-gradle-project-import/embed/#?secret=HvGQ4iHM5T#?secret=SzZSjxeYl5" data-secret="SzZSjxeYl5" width="600" height="338" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe>
</div></figure>



<p class="wp-block-paragraph">Docker로 개발 환경을 빠르게 구축하는 것도 가능합니다. 다음 블로그 내용을 읽어보세요!</p>



<figure class="wp-block-embed-wordpress wp-block-embed is-type-wp-embed is-provider-아빠프로그래머의-좌충우돌-개발하기"><div class="wp-block-embed__wrapper">
<blockquote class="wp-embedded-content" data-secret="BJXl4TAhjq"><a href="https://www.daddyprogrammer.org/post/1994/docker-kitematic-mysql-redis-rabbitmq-mongo/">Docker로 빠르게 개발환경 구성하기(mysql, redis, rabbitmq, mongoDB)</a></blockquote><iframe loading="lazy" class="wp-embedded-content" sandbox="allow-scripts" security="restricted"  title="&#8220;Docker로 빠르게 개발환경 구성하기(mysql, redis, rabbitmq, mongoDB)&#8221; &#8212; 아빠프로그래머의 좌충우돌 개발하기!" src="https://www.daddyprogrammer.org/post/1994/docker-kitematic-mysql-redis-rabbitmq-mongo/embed/#?secret=V8NGiFTFRs#?secret=BJXl4TAhjq" data-secret="BJXl4TAhjq" width="600" height="338" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe>
</div></figure>



<p class="wp-block-paragraph">스프링 api 서버를 이용하여 웹사이트를 만들어보고 싶으시면 아래 포스팅을 참고해 주세요.</p>



<figure class="wp-block-embed-wordpress wp-block-embed is-type-wp-embed is-provider-아빠프로그래머의-좌충우돌-개발하기"><div class="wp-block-embed__wrapper">
<blockquote class="wp-embedded-content" data-secret="kKFQw0S9G2"><a href="https://www.daddyprogrammer.org/post/6237/rest-api-angular-framework-make-website/">Spring Rest api + Angular framework로 웹사이트 만들기(1) &#8211; 프로젝트 구성 및 반응형 레이아웃 구현</a></blockquote><iframe loading="lazy" class="wp-embedded-content" sandbox="allow-scripts" security="restricted"  title="&#8220;Spring Rest api + Angular framework로 웹사이트 만들기(1) &#8211; 프로젝트 구성 및 반응형 레이아웃 구현&#8221; &#8212; 아빠프로그래머의 좌충우돌 개발하기!" src="https://www.daddyprogrammer.org/post/6237/rest-api-angular-framework-make-website/embed/#?secret=ExA8U3ODqN#?secret=kKFQw0S9G2" data-secret="kKFQw0S9G2" width="600" height="338" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe>
</div></figure>



<p class="wp-block-paragraph"></p>
<p>The post <a href="https://www.daddyprogrammer.org/post/2445/springboot2-blue-green-deploy-nginx/">SpringBoot2로 Rest api 만들기(12) – Deploy &#038; Nginx 연동 &#038; 무중단 배포 하기</a> appeared first on <a href="https://www.daddyprogrammer.org">아빠프로그래머의 좌충우돌 개발하기!</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.daddyprogrammer.org/post/2445/springboot2-blue-green-deploy-nginx/feed/</wfw:commentRss>
			<slash:comments>3</slash:comments>
		
		
		
		<series:name><![CDATA[SpringBoot2로 Rest api 만들기]]></series:name>
	</item>
		<item>
		<title>AWS EC2 &#8211; install nginx, mariadb</title>
		<link>https://www.daddyprogrammer.org/post/2348/aws-ec2-install-nginx-mariadb/</link>
					<comments>https://www.daddyprogrammer.org/post/2348/aws-ec2-install-nginx-mariadb/#comments</comments>
		
		<dc:creator><![CDATA[happydaddy]]></dc:creator>
		<pubDate>Tue, 30 Apr 2019 01:39:53 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[AWS]]></category>
		<category><![CDATA[DevOps]]></category>
		<category><![CDATA[데이터베이스]]></category>
		<category><![CDATA[웹서버]]></category>
		<category><![CDATA[Nginx]]></category>
		<category><![CDATA[Mariadb]]></category>
		<category><![CDATA[EC2]]></category>
		<guid isPermaLink="false">http://3.36.120.4/?p=2348</guid>

					<description><![CDATA[<p>AWS EC2에 nginx와 mariadb를 설치하는 방법에 대하여 정리합니다. 서버 타임존 변경 aws는 기본적으로 os설치시 타임존이 UTC로 맞춰져있으므로 nginx/mariadb 설치전에 TimeZone을 변경해 줍시다. nginx 설치 &#8211; amazon-linux-extras install nginx yum으로는 nginx 패키지를 찾지 못합니다. amazon-linux-extras 명령어로 nginx를 설치합니다. nginx 관련 파일 위치 설정 &#8211; /etc/nginx/nginx.conf로그 &#8211; /var/log/nginx 방화벽 오픈 웹서버에 접근하기 위해 80 port를 열어줍니다.ec2 security [&#8230;]</p>
<p>The post <a href="https://www.daddyprogrammer.org/post/2348/aws-ec2-install-nginx-mariadb/">AWS EC2 &#8211; install nginx, mariadb</a> appeared first on <a href="https://www.daddyprogrammer.org">아빠프로그래머의 좌충우돌 개발하기!</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">AWS EC2에 nginx와 mariadb를 설치하는 방법에 대하여 정리합니다.</p>



<h2 class="wp-block-heading">서버 타임존 변경</h2>



<p class="wp-block-paragraph">aws는 기본적으로 os설치시 타임존이 UTC로 맞춰져있으므로 nginx/mariadb 설치전에 TimeZone을 변경해 줍시다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ date
2019. 04. 30. (화) 04:23:00 UTC
$ sudo rm /etc/localtime
$ sudo ln -s /usr/share/zoneinfo/Asia/Seoul /etc/localtime
$ date
2019. 04. 30. (화) 13:45:00 KST</pre>



<h2 class="wp-block-heading"><strong>nginx 설치</strong></h2>



<h3 class="wp-block-heading">&#8211; amazon-linux-extras install nginx</h3>



<p class="wp-block-paragraph">yum으로는 nginx 패키지를 찾지 못합니다. amazon-linux-extras 명령어로 nginx를 설치합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ amazon-linux-extras list
  0  ansible2                 available    [ =2.4.2  =2.4.6 ]
  2  httpd_modules            available    [ =1.0 ]
  3  memcached1.5             available    [ =1.5.1 ]
  4  nginx1.12                available    [ =1.12.2 ]
  5  postgresql9.6            available    [ =9.6.6  =9.6.8 ]
  6  postgresql10             available    [ =10 ]
  8  redis4.0                 available    [ =4.0.5  =4.0.10 ]
  9  R3.4                     available    [ =3.4.3 ]
 10  rust1                    available    \
        [ =1.22.1  =1.26.0  =1.26.1  =1.27.2  =1.31.0 ]
 11  vim                      available    [ =8.0 ]
................. 생략
$ sudo amazon-linux-extras install nginx1.12
$ sudo service nginx start
Redirecting to /bin/systemctl start nginx.service</pre>



<h3 class="wp-block-heading">nginx 관련 파일 위치</h3>



<p class="wp-block-paragraph"><span class="has-inline-color has-vivid-cyan-blue-color"><strong>설정 </strong></span>&#8211; /etc/nginx/nginx.conf<br><span class="has-inline-color has-vivid-cyan-blue-color"><strong>로그 </strong></span>&#8211; /var/log/nginx</p>



<h3 class="wp-block-heading">방화벽 오픈</h3>



<p class="wp-block-paragraph">웹서버에 접근하기 위해 80 port를 열어줍니다.<br>ec2 security groups 설정에서 inbound에 80 port를 추가합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">Type : HTTP
Protocol : TCP
Port range : 80
Source : 0.0.0.0/0</pre>



<h3 class="wp-block-heading">nginx 실행</h3>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ sudo service nginx start</pre>



<h3 class="wp-block-heading">확인</h3>



<figure class="wp-block-image is-resized"><img loading="lazy" decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2019/05/nginx.png" alt="" class="wp-image-2549" width="869" height="266" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2019/05/nginx.png 1158w, https://www.daddyprogrammer.org/wp-content/uploads/2019/05/nginx-1024x314.png 1024w, https://www.daddyprogrammer.org/wp-content/uploads/2019/05/nginx-768x235.png 768w, https://www.daddyprogrammer.org/wp-content/uploads/2019/05/nginx-150x46.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2019/05/nginx-300x92.png 300w, https://www.daddyprogrammer.org/wp-content/uploads/2019/05/nginx-696x213.png 696w" sizes="auto, (max-width: 869px) 100vw, 869px" /></figure>



<h2 class="wp-block-heading" id="mce_1"><strong>mariadb 설치</strong></h2>



<h3 class="wp-block-heading">&#8211; yum install mariadb-server</h3>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ sudo yum install mariadb-server
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
amzn2-core                                                                                                        | 2.4 kB  00:00:00     
Resolving Dependencies
--> Running transaction check
---> Package mariadb-server.x86_64 1:5.5.62-1.amzn2.0.1 will be installed
--> Processing Dependency: mariadb(x86-64) = 1:5.5.62-1.amzn2.0.1 for package: 1:mariadb-server-5.5.62-1.amzn2.0.1.x86_64
--> Processing Dependency: perl-DBI for package: 1:mariadb-server-5.5.62-1.amzn2.0.1.x86_64
............. 생략
--> Finished Dependency Resolution

Dependencies Resolved

===========================================================================
 Package                                 Arch                   Version                                 Repository                  Size
===========================================================================
Installing:
 mariadb-server                          x86_64                 1:5.5.62-1.amzn2.0.1                    amzn2-core                  11 M
Installing for dependencies:
 mariadb                                 x86_64                 1:5.5.62-1.amzn2.0.1                    amzn2-core                 9.0 M
............ 생략

Transaction Summary
===========================================================================
Install  1 Package (+9 Dependent packages)

Total download size: 22 M
Installed size: 111 M
Is this ok [y/d/N]: y

$ sudo service mariadb start
Redirecting to /bin/systemctl start mariadb.service</pre>



<h3 class="wp-block-heading">Port 변경 / 언어셋 변경</h3>



<p class="wp-block-paragraph">기본포트 3306은 잘 알려진 Port이므로 다른 포트로 변경하여 사용하는 것을 추천합니다. 언어셋을 utf8mb4로 설정하는 이유는, IOS에서 이모티콘/이모지 등을 표현할때 문자당 4byte를 사용하는데 기본설정을 사용하면 3byte까지만 받을수있어 utf8mb4로 설정해서 문자를 받을수있게 해주는 것입니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">$ sudo vim /etc/my.cnf
[mysqld]
port = 36091
character-set-server = utf8mb4
collation-server = utf8mb4_unicode_ci
character_set_server = utf8mb4
collation_server = utf8mb4_unicode_ci
$ sudo service mariadb restart</pre>



<h3 class="wp-block-heading">root 패스워드 변경</h3>



<p class="wp-block-paragraph">root패스워드는 처음엔 설정이 안되어 있으므로 설정을 해주도록 합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">// root 패스워드 설정
$ mysqladmin -u root -p password 'xxRootPwd^&amp;*'
Enter password: 그냥 엔터
$ mysql -u root -p
Enter password:설정한 비밀번호 입력
MariaDB [(none)]> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| mysql              |
| performance_schema |
| test               |
+--------------------+
4 rows in set (0.00 sec)</pre>



<h3 class="wp-block-heading">운영용 database / id 생성</h3>



<p class="wp-block-paragraph">root를 그냥 사용해도 되지만. root의 경우 모든 권한을 가지고 있고 외부에서 접속 가능하게 설정할 경우엔 위험할 수 있으므로 운영 DB와 운영ID를 따로 만들어 권한을 격리시켜 사용하는 것을 추천합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">// root로 mariadb 접속
MariaDB [(none)]> create database daddyprogrammer;
Query OK, 1 row affected (0.00 sec)
MariaDB [(none)]> set password for happydaddy@localhost=password('xxxdaddypwd^&amp;*');
Query OK, 0 rows affected (0.00 sec)
MariaDB [(none)]> grant all privileges on daddyprogrammer.* to happydaddy@localhost identified by 'xxxdaddypwd^&amp;*';
Query OK, 0 rows affected (0.00 sec)
MariaDB [(none)]> flush privileges;
Query OK, 0 rows affected (0.00 sec)
MariaDB [(none)]> exit;

$ mysql -u happydaddy -p
Enter password:설정한 비밀번호 입력
MariaDB [(none)]> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| daddyprogrammer    |
| test               |
+--------------------+
3 rows in set (0.00 sec)</pre>



<h3 class="wp-block-heading">외부 접속 설정</h3>



<p class="wp-block-paragraph">ec2 security groups 설정에서 mariadb port를 inbound에 추가합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">Type : Custom TCP Rule
Protocal : TCP
Port range : 위에서 설정한 myriadb의 port
Source : 0.0.0.0/0</pre>



<h3 class="wp-block-heading">운영 계정 외부 접속 권한 설정</h3>



<p class="wp-block-paragraph">daddyprogrammer database에 대하여 happydaddy 유저가 103.xxx.200. 으로 시작하는 IP에서만 비밀번호를 넣어 접근가능하도록 설정합니다.</p>



<pre class="EnlighterJSRAW" data-enlighter-language="generic" data-enlighter-theme="atomic" data-enlighter-highlight="" data-enlighter-linenumbers="false" data-enlighter-lineoffset="" data-enlighter-title="" data-enlighter-group="">// root 로그인
MariaDB [(none)]> grant all privileges on daddyprogrammer.* to happydaddy@'103.xxx.200.%' identified by 'xxxdaddypwd^&amp;*';
Query OK, 0 rows affected (0.00 sec)

MariaDB [(none)]> flush privileges;
Query OK, 0 rows affected (0.00 sec)</pre>



<h3 class="wp-block-heading">접속 확인</h3>



<p class="wp-block-paragraph">아래 링크에서 mysql workbench를 다운로드 받아 설치합니다.<br><a href="https://dev.mysql.com/downloads/workbench/">https://dev.mysql.com/downloads/workbench/</a></p>



<p class="wp-block-paragraph">외부 접속 권한 설정한 운영계정으로 접속할 커넥션을 하나 생성합니다.</p>



<figure class="wp-block-image is-resized"><img loading="lazy" decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2019/04/mysqlworkbench.png" alt="" class="wp-image-2416" width="600" height="377" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2019/04/mysqlworkbench.png 800w, https://www.daddyprogrammer.org/wp-content/uploads/2019/04/mysqlworkbench-768x482.png 768w, https://www.daddyprogrammer.org/wp-content/uploads/2019/04/mysqlworkbench-150x94.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2019/04/mysqlworkbench-300x188.png 300w, https://www.daddyprogrammer.org/wp-content/uploads/2019/04/mysqlworkbench-696x437.png 696w, https://www.daddyprogrammer.org/wp-content/uploads/2019/04/mysqlworkbench-669x420.png 669w" sizes="auto, (max-width: 600px) 100vw, 600px" /></figure>



<p class="wp-block-paragraph">접속에 성공하면 다음과 같은 화면을 볼 수 있습니다.</p>



<figure class="wp-block-image is-resized"><img loading="lazy" decoding="async" src="http://www.daddyprogrammer.org/wp-content/uploads/2019/04/mysqlworkbench_2.png" alt="" class="wp-image-2417" width="629" height="461" srcset="https://www.daddyprogrammer.org/wp-content/uploads/2019/04/mysqlworkbench_2.png 838w, https://www.daddyprogrammer.org/wp-content/uploads/2019/04/mysqlworkbench_2-768x564.png 768w, https://www.daddyprogrammer.org/wp-content/uploads/2019/04/mysqlworkbench_2-150x110.png 150w, https://www.daddyprogrammer.org/wp-content/uploads/2019/04/mysqlworkbench_2-300x220.png 300w, https://www.daddyprogrammer.org/wp-content/uploads/2019/04/mysqlworkbench_2-696x511.png 696w, https://www.daddyprogrammer.org/wp-content/uploads/2019/04/mysqlworkbench_2-572x420.png 572w, https://www.daddyprogrammer.org/wp-content/uploads/2019/04/mysqlworkbench_2-80x60.png 80w" sizes="auto, (max-width: 629px) 100vw, 629px" /></figure>
<p>The post <a href="https://www.daddyprogrammer.org/post/2348/aws-ec2-install-nginx-mariadb/">AWS EC2 &#8211; install nginx, mariadb</a> appeared first on <a href="https://www.daddyprogrammer.org">아빠프로그래머의 좌충우돌 개발하기!</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.daddyprogrammer.org/post/2348/aws-ec2-install-nginx-mariadb/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
	</channel>
</rss>
