-
Notifications
You must be signed in to change notification settings - Fork 1
224 lines (199 loc) · 8.49 KB
/
docker-image.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
name: Build, Push Docker Images., Deploy
on:
push:
branches: [ "dev", "main" ]
# pull_request:
# branches: [ "dev" ]
jobs:
# Start the Build
build:
runs-on: ubuntu-latest
strategy:
matrix:
node-version: [16.x]
steps:
-
name: Checkout
uses: actions/checkout@v3
-
name: Set up QEMU
uses: docker/setup-qemu-action@v2
-
name: Set up Docker Buildx
uses: docker/setup-buildx-action@v2
-
name: Login to Docker Hub
uses: docker/login-action@v2
with:
username: ${{ secrets.DOCKER_HUB_USER }}
password: ${{ secrets.DOCKERHUB_TOKEN }}
-
name: Build and push Frontend image
uses: docker/build-push-action@v3
with:
context: ./frontend
push: true
tags: celnet1/salesaccount-fe:latest
-
name: Build and push backend image
uses: docker/build-push-action@v3
with:
context: ./Backend
push: true
tags: celnet1/salesaccount-be:latest
-
name: Build and push nginx image
uses: docker/build-push-action@v3
with:
context: ./nginx
push: true
tags: celnet1/salesaccount-nginx:latest
#Start Github Runner
# start-runner:
# name: Start self-hosted EC2 runner
# runs-on: ubuntu-latest
# outputs:
# label: ${{ steps.start-ec2-runner.outputs.label }}
# ec2-instance-id: ${{ steps.start-ec2-runner.outputs.ec2-instance-id }}
# steps:
# - name: Configure AWS credentials
# uses: aws-actions/configure-aws-credentials@v1
# with:
# aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
# aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
# aws-region: ${{ secrets.AWS_REGION }}
# - name: Start EC2 runner
# id: start-ec2-runner
# uses: machulav/ec2-github-runner@v2
# with:
# mode: start
# github-token: ${{ secrets.GH_PERSONAL_ACCESS_TOKEN }}
# ec2-image-id: ami-00312eb2e6a5b268b
# ec2-instance-type: t2.micro
# subnet-id: subnet-0674b9554f1dc2858
# security-group-id: sg-0064c27b59d58f409
# # iam-role-name: my-role-name # optional, requires additional permissions
# # aws-resource-tags: > # optional, requires additional permissions
# # [
# # {"Key": "Name", "Value": "ec2-github-runner"},
# # {"Key": "GitHubRepository", "Value": "${{ github.repository }}"}
# # ]
#Run Runner
do-the-job:
name: Stop and Start Docker Containers
needs: build # required to build to finish
runs-on: self-hosted # run the job on the AWS EC2
steps:
- name: Stop Docker Containers
working-directory: /home/ubuntu/salesaccount.web
run: |
git pull
docker compose down
- name: Start Docker Containers
working-directory: /home/ubuntu/salesaccount.web
run: |
docker compose up -d
# stop-runner:
# name: Stop self-hosted EC2 runner
# needs:
# - build # required to get output from the start-runner job
# - do-the-job # required to wait when the main job is done
# runs-on: ubuntu-latest
# if: ${{ always() }} # required to stop the runner even if the error happened in the previous jobs
# steps:
# - name: Configure AWS credentials
# uses: aws-actions/configure-aws-credentials@v1
# with:
# aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
# aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
# aws-region: ${{ secrets.AWS_REGION }}
# - name: Stop EC2 runner
# uses: machulav/ec2-github-runner@v2
# with:
# mode: stop
# github-token: ${{ secrets.GH_PERSONAL_ACCESS_TOKEN }}
# label: ${{ needs.start-runner.outputs.label }}
# ec2-instance-id: ${{ needs.start-runner.outputs.ec2-instance-id }}
# This workflow will build and push a new container image to Amazon ECR,
# and then will deploy a new task definition to Amazon ECS, when there is a push to the "dev" branch.
#
# To use this workflow, you will need to complete the following set-up steps:
#
# 1. Create an ECR repository to store your images.
# For example: `aws ecr create-repository --repository-name my-ecr-repo --region us-east-2`.
# Replace the value of the `ECR_REPOSITORY` environment variable in the workflow below with your repository's name.
# Replace the value of the `AWS_REGION` environment variable in the workflow below with your repository's region.
#
# 2. Create an ECS task definition, an ECS cluster, and an ECS service.
# For example, follow the Getting Started guide on the ECS console:
# https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/firstRun
# Replace the value of the `ECS_SERVICE` environment variable in the workflow below with the name you set for the Amazon ECS service.
# Replace the value of the `ECS_CLUSTER` environment variable in the workflow below with the name you set for the cluster.
#
# 3. Store your ECS task definition as a JSON file in your repository.
# The format should follow the output of `aws ecs register-task-definition --generate-cli-skeleton`.
# Replace the value of the `ECS_TASK_DEFINITION` environment variable in the workflow below with the path to the JSON file.
# Replace the value of the `CONTAINER_NAME` environment variable in the workflow below with the name of the container
# in the `containerDefinitions` section of the task definition.
#
# 4. Store an IAM user access key in GitHub Actions secrets named `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`.
# See the documentation for each action used below for the recommended IAM policies for this IAM user,
# and best practices on handling the access key credentials.
# name: Deploy to Amazon ECS
# on:
# push:
# branches: [ "dev" ]
# env:
# AWS_REGION: MY_AWS_REGION # set this to your preferred AWS region, e.g. us-west-1
# ECR_REPOSITORY: MY_ECR_REPOSITORY # set this to your Amazon ECR repository name
# ECS_SERVICE: MY_ECS_SERVICE # set this to your Amazon ECS service name
# ECS_CLUSTER: MY_ECS_CLUSTER # set this to your Amazon ECS cluster name
# ECS_TASK_DEFINITION: MY_ECS_TASK_DEFINITION # set this to the path to your Amazon ECS task definition
# # file, e.g. .aws/task-definition.json
# CONTAINER_NAME: MY_CONTAINER_NAME # set this to the name of the container in the
# # containerDefinitions section of your task definition
# permissions:
# contents: read
# jobs:
# deploy:
# name: Deploy
# runs-on: ubuntu-latest
# environment: production
# steps:
# - name: Checkout
# uses: actions/checkout@v3
# - name: Configure AWS credentials
# uses: aws-actions/configure-aws-credentials@v1
# with:
# aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
# aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
# aws-region: ${{ env.AWS_REGION }}
# - name: Login to Amazon ECR
# id: login-ecr
# uses: aws-actions/amazon-ecr-login@v1
# - name: Build, tag, and push image to Amazon ECR
# id: build-image
# env:
# ECR_REGISTRY: ${{ steps.login-ecr.outputs.registry }}
# IMAGE_TAG: ${{ github.sha }}
# run: |
# # Build a docker container and
# # push it to ECR so that it can
# # be deployed to ECS.
# docker build -t $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG .
# docker push $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG
# echo "image=$ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG" >> $GITHUB_OUTPUT
# - name: Fill in the new image ID in the Amazon ECS task definition
# id: task-def
# uses: aws-actions/amazon-ecs-render-task-definition@v1
# with:
# task-definition: ${{ env.ECS_TASK_DEFINITION }}
# container-name: ${{ env.CONTAINER_NAME }}
# image: ${{ steps.build-image.outputs.image }}
# - name: Deploy Amazon ECS task definition
# uses: aws-actions/amazon-ecs-deploy-task-definition@v1
# with:
# task-definition: ${{ steps.task-def.outputs.task-definition }}
# service: ${{ env.ECS_SERVICE }}
# cluster: ${{ env.ECS_CLUSTER }}
# wait-for-service-stability: true