/app #アプリのルートディレクトリ
  ├─.circieci # CircleCIの設定ファイルを格納
  │   └─config.yml
  ├─.devcontainer # VSCodeRemoteContainerの設定ファイルを格納
  │   ├─devcontainer.json
  │   └─docker-compose.yml
  ├─.elasticbeanstalk # ElasticBeanstalkの設定ファイルを格納
  │   └─config.yml
  ├─.ebextensions # ElasticBeanstalkのオプション設定ファイルを格納
  │   └─env.config
  ├─.gitignore
  ├─Dockerfile
  ├─docker-compose.yml
  ├─.dockerignore
  ├─node_modules
  │  └─(略)
  ├─package.json
  ├─package-lock.json
  └─src # アプリのソースコード
     ├─controllers
     │  └─personsController.js
     ├─models
     │  └─person.js
     └─main.js

$ npm init -y$ npm i express -S$ npm i mongoose -S

{(略)"main":"src/main.js","scripts":{"test":"echo \"Error: no test specified\"&& exit 1","start":"node src/main"},(略)}

"use strict";constexpress=require("express");constapp=express();constpersonsController=require("./controllers/personsController");constmongoose=require("mongoose");mongoose.connect("mongodb://mongo-db:27017/testdb",{useNewUrlParser:true});constdb=mongoose.connection;db.once("open",()=>{console.log("successfully connected to mongoDB");})app.set('port',3000);app.get("/",personsController.getAllPersons,(req,res,next)=>{console.log("server get request on root");res.send(req.data);});app.listen(app.get('port'),()=>{console.log(`The Express.js server has started and is listening on port number: ${app.get('port')}`);});

"use strict";constmongoose=require("mongoose");constpersonSchema=newmongoose.Schema({name:{type:String,required:true},email:{type:String,required:true,lowercase:true,unique:true},zipCode:{type:Number,min:[10000,"Zip code too short"],max:99999},});module.exports=mongoose.model("Person",personSchema);

"use strict";constPerson=require("../models/person");exports.getAllPersons=(req,res,next)=>{Person.find({},(error,persons)=>{if(error)next(error);req.data=persons;next();});};

$ git init
$ touch .gitignore

node_modules/
.gitignore

FROM node:12WORKDIR /appCOPY package.json .COPY package-lock.json .RUN npm installCOPY . .EXPOSE 3000CMD [ "node", "src/main.js" ]

node_modules
npm-debug.log

# docker-compose記法のバージョンversion:'3.3'# 起動するコンテナの種類を定義services:#以下node.jsのアプリケーションレイヤーの設定。このコンテナには「node-web」と名前がつくnode-web:# build時にカレントディレクトリにあるDockerfileのイメージを使用するbuild:.ports:# localの8888番ポートと、コンテナの3000番ポートをつなげる-"8888:3000"# コンテナ内でのホスト名hostname:web-server# このコンテナは、以下記述する「mongo-db」コンテナが立ち上がってから作成される。depends_on:-mongo-db# 以下mongoDBのコンテナ設定。コンテナ名は「mongo-db」とつく。mongo-db:# mongo:3.6の公式コンテナイメージを元にして作成する。image:"mongo:3.6"ports:-"27017:27017"hostname:db-servervolumes:#コンテナ内の/data/dbの中身を、「db-volume」という名前のvolumeにマウント-db-volume:/data/db-db-config-volume:/data/configdb# 作成するvolumeの名前を列挙volumes:db-volume:db-config-volume:

//Forformatdetails,seehttps://aka.ms/vscode-remote/devcontainer.jsonorthisfile'sREADMEat://https://github.com/microsoft/vscode-dev-containers/tree/v0.112.0/containers/docker-existing-docker-compose//Ifyouwanttorunasanon-rootuserinthecontainer,see.devcontainer/docker-compose.yml.{"name":"Existing Docker Compose (Extend)","dockerComposeFile":["../docker-compose.yml","docker-compose.yml"],"service":"node-web","workspaceFolder":"/workspace","settings":{"terminal.integrated.shell.linux":null},"extensions":[]}

version:'3.3'services:node-web:volumes:-.:/workspace:cachedcommand:/bin/sh -c "while sleep 1000; do :; done"

.devcontainer/

{"name":"Existing Dockerfile","context":"..","dockerFile":"../Dockerfile","settings":{"terminal.integrated.shell.linux":null},"extensions":[]}

//local:portXXXX,container:portYYYY"appPort":["XXXX:YYYY"]

$ ssh ec2-user@<サーバードメイン> -i<path to key>
       __|  __|_  )
       _|  (     /   Amazon Linux 2 AMI
      ___|\___|___|

$ sudo vim /etc/yum.repos.d/mongodb.repo

# 以下を書き込んで保存[mongodb-org-3.2]
name=MongoDB Repository
baseurl=https://repo.mongodb.org/yum/amazon/2013.03/mongodb-org/3.2/x86_64/
gpgcheck=1
enabled=1
gpgkey=https://www.mongodb.org/static/pgp/server-3.2.asc

$ sudo yum install-y mongodb-org

$ sudo vim /etc/mongod.conf

# 以下をコメントアウト
# bind_ip=127.0.0.1

/*
mongoose.connect(
    mongodb://mongo-db:27017/testdb,
    {useNewUrlParser: true}
);
*/constmongoDB=process.env.NODE_ENV==="production"?'mongodb://[mongoDBをインストールしたインスタンスのIP address]:27017/testdb':'mongodb://mongo-db:27017/testdb';mongoose.connect(mongoDB,{useNewUrlParser:true});// app.set('port', 3000);の部分を以下のように修正app.set('port',process.env.PORT||3000);

$ eb init

# どこのリージョンにアプリをデプロイするか選択
Select a default region
1) us-east-1 : US East (N. Virginia)
2) us-west-1 : US West (N. California)
3) us-west-2 : US West (Oregon)(略)
9) ap-northeast-1 : Asia Pacific (Tokyo)(略)(default is 3): 9

# 初めてCLIを使う場合で、アクセスキーとCLIが紐づいていない場合はここで聞かれます。# 一度でもこれを入力したことがある場合はこの項目はスキップされます。
You have not yet set up your credentials or your credentials are incorrect.
You must provide your credentials.
(aws-access-id): your-access-key-id
(aws-secret-key): your-access-secret-key
# 入力したら、~/.aws/configファイルの中に設定が保存されて、以降はそれが参照されます。# アプリの名前を決める
Enter Application Name
(default is "app"): 
Application app has been created.

# Dockerfileがディレクトリ内にあったことから、Dockerアプリだと自動で判断してくれた。# あっているのでYを入力
It appears you are using Docker. Is this correct?
(Y/n): Y

# 使うDockerの種類を選択
Select a platform version.
1) Docker 18.09.9-ce
2) Docker
(default is 1): 

# アプリのコードの置き場所としてCodeCommitを使うかどうか。# Noを選択すると、S3のバケットが自動で用意されてそこに格納されるようになる。
Do you wish to continue with CodeCommit? (y/N)(default is n): n

# アプリがデプロイされるインスタンスにSSH接続できるようにするかの設定# SSH接続できれば、何かあったときにサーバー内に入って調べられるようになるのでYが無難
Do you want to set up SSH for your instances?
(Y/n): Y

# SSH接続するためのキーペアを何にするかを選択
Select a keypair.
1) your-keypair
2)[ Create new KeyPair ](default is 1): 1

branch-defaults:master:environment:nullgroup_suffix:nullglobal:application_name:appbranch:nulldefault_ec2_keyname:my-keynamedefault_platform:Dockerdefault_region:ap-northeast-1include_git_submodules:trueinstance_profile:nullplatform_name:nullplatform_version:nullprofile:eb-clirepository:nullsc:gitworkspace_type:Application

option_settings:
  - option_name: NODE_ENV
    value: production

$ git commit -m"first commit"

$ eb create
Enter Environment Name
(default is app-dev):

Enter DNS CNAME prefix
(default is app-dev): 

Select a load balancer type
1) classic
2) application
3) network
(default is 2): 

Creating application version archive "your-app-deployed-version".
Uploading [your-app-file].zip to S3. This may take a while.
Upload Complete.

Environment details for: app-dev
  Application name: app
  Region: ap-northeast-1
  Deployed Version: your-app-deployed-version
  Environment ID: xxxxxxxxxxx
  Platform: arn:aws:elasticbeanstalk:ap-northeast-1::platform/Docker running on 64bit Amazon Linux 2/0.1.0
  Tier: WebServer-Standard-1.0
  CNAME: app-dev.ap-northeast-1.elasticbeanstalk.com
  Updated: yyyy-mm-dd hh:mm:ss

Printing Status:
yyyy-mm-dd hh:mm:ss    INFO    createEnvironment is starting.
yyyy-mm-dd hh:mm:ss    INFO    Using elasticbeanstalk-ap-northeast-1-[your bucket ID] as Amazon S3 storage bucket for environment data.
yyyy-mm-dd hh:mm:ss    INFO    Created target group named: [your-target-group-name]
yyyy-mm-dd hh:mm:ss    INFO    Created security group named: [your-security-group-name]
yyyy-mm-dd hh:mm:ss    INFO    Created security group named: [your-security-group-name-2]
yyyy-mm-dd hh:mm:ss    INFO    Created Auto Scaling launch configuration named: [your-configuration-name]
yyyy-mm-dd hh:mm:ss    INFO    Created Auto Scaling group named: [your-auto-scaling-group-name]
yyyy-mm-dd hh:mm:ss    INFO    Waiting for EC2 instances to launch. This may take a few minutes.
yyyy-mm-dd hh:mm:ss    INFO    Created Auto Scaling group policy named: [yout-auto-scaling-policy-name]
yyyy-mm-dd hh:mm:ss    INFO    Created Auto Scaling group policy named: [yout-auto-scaling-policy-name-2]
yyyy-mm-dd hh:mm:ss    INFO    Created CloudWatch alarm named: [your-cloudwatch-alarm-name]
yyyy-mm-dd hh:mm:ss    INFO    Created CloudWatch alarm named: [your-cloudwatch-alarm-name-2]
yyyy-mm-dd hh:mm:ss    INFO    Created load balancer named: [your-load-balancer-name]
yyyy-mm-dd hh:mm:ss    INFO    Created Load Balancer listener named: [your-load-balancer-listener-name]
yyyy-mm-dd hh:mm:ss    INFO    Successfully pulled node:12
yyyy-mm-dd hh:mm:ss    INFO    Successfully built aws_beanstalk/staging-app
yyyy-mm-dd hh:mm:ss    INFO    Docker container [docker-ID] is running aws_beanstalk/current-app.

$ eb status
Environment details for: app-env
  Application name: app
  Region: ap-northeast-1
  Deployed Version: your-app-deployed-version
  Environment ID: xxxxxxxxxxx
  Platform: arn:aws:elasticbeanstalk:ap-northeast-1::platform/Docker running on 64bit Amazon Linux 2/0.1.0
  Tier: WebServer-Standard-1.0
  CNAME: app-dev.ap-northeast-1.elasticbeanstalk.com
  Updated: yyyy-mm-dd hh:mm:ss
  Status: Ready
  Health: Green

$ git commit -m"bug fix"$ eb deploy
Creating application version archive "your-app-deployed-version".
Uploading [your-fixed-app-file] to S3. This may take a while.
Upload Complete.
yyyy-mm-dd hh:mm:ss    INFO    Environment update is starting.      
yyyy-mm-dd hh:mm:ss    INFO    Deploying new version to instance(s).
yyyy-mm-dd hh:mm:ss    INFO    Successfully pulled node:12          
yyyy-mm-dd hh:mm:ss    INFO    Successfully built aws_beanstalk/staging-app
yyyy-mm-dd hh:mm:ss    INFO    Docker container [docker ID] is running aws_beanstalk/current-app.
yyyy-mm-dd hh:mm:ss    INFO    New application version was deployed to running EC2 instances.
yyyy-mm-dd hh:mm:ss    INFO    Environment update completed successfully.

$ eb terminate --all
The application "app" and all its resources will be deleted.
This application currently has the following:
Running environments: xxx
Configuration templates: xx
Application versions: xxx

To confirm, type the application name: app

Removing application versions from s3.
yyyy-mm-dd hh:mm:ss    INFO    deleteApplication is starting.
yyyy-mm-dd hh:mm:ss    INFO    Invoking Environment Termination workflows.
yyyy-mm-dd hh:mm:ss    INFO    The environment termination step is done.
yyyy-mm-dd hh:mm:ss    INFO    The application has been deleted successfully.

!.elasticbeanstalk/config.yml

# circleciのバージョンversion:2# jobの設定jobs:# deployという名前のjobの定義を以下記述deploy:# circleciが検証用に用意するコンテナ内でのソースコードの置き場working_directory:~/app# circleciが建てるdocker imageの種類docker:-image:circleci/node:12# deployというjobを行うためにcircleciのdocker内で動作させるコマンドsteps:-checkout-run:npm install-save_cache:paths:-node_moduleskey:v1-dependencies-{{ checksum "package.json" }}-run:name:Installing EB CLIworking_directory:/command:|sudo apt-get -y -qq updatesudo apt-get install python-pip python-dev build-essentialsudo pip install awsebcli --upgrade-run:name:Deployingcommand:eb deploy [created-my-env-name]# workflow(jobを順番どうりに実行する一連のフロー)の定義workflows:version:2# workflowの名前をbuildとするbuild:# build workflowで実行するjobの順番jobs:-deploy:# deploy jobを行うのは、Githubのmasterブランチにpushが行われたときのみfilters:branches:only:-master

$ git remote add origin <git url>
$ git push -u origin master