Skip to content

Commit 811af3e

Browse files
committed
docs: deployment posts improvements
1 parent 3a6227f commit 811af3e

File tree

2 files changed

+5
-5
lines changed
  • adminforth/documentation/blog
    • 2025-02-19-compose-ec2-deployment-ci-registry
    • 2025-02-19-compose-ec2-deployment-ecr-ci

2 files changed

+5
-5
lines changed

adminforth/documentation/blog/2025-02-19-compose-ec2-deployment-ci-registry/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
slug: compose-ec2-deployment-github-actions-registry
3-
title: "Amazon EC2 Deployments with GitHub Actions, Terraform, Docker & Amazon ECR"
3+
title: "Amazon EC2 Deployments with GitHub Actions, Terraform, Docker & Self-hosted Registry"
44
authors: ivanb
55
tags: [aws, terraform, github-actions]
66
description: "The ultimate step-by-step guide to cost-effective, build-time-efficient, and easy managable EC2 deployments using GitHub Actions, Terraform, Docker, and a self-hosted registry."
@@ -108,7 +108,7 @@ Make sure you are not calling bundleNow in `index.ts` file for non-development m
108108
}
109109
```
110110

111-
### Step 1.3 - Make sure you have `migrateLiveAndStart` script in `package.json`
111+
### Step 1.3 - Make sure you have all required scripts in `package.json`
112112

113113
```json title="./myadmin/package.json"
114114
...

adminforth/documentation/blog/2025-02-19-compose-ec2-deployment-ecr-ci/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ image: "/ogs/ga-tf-ecr.jpg"
88
---
99

1010

11-
![alt text](ga-tf-aws.jpg)
11+
![alt text](ga-tf-ecr.jpg)
1212

1313

1414
This guide shows how to deploy own Docker apps (with AdminForth as example) to Amazon EC2 instance with Docker and Terraform involving pushing images into Amazon ECR.
@@ -40,7 +40,7 @@ Quick difference between approaches from previous post and current post:
4040
| How build happens | Source code is rsync-ed from CI to EC2 and docker build is done there | Docker build is done on CI and docker image is pushed to registry, then Docker on EC2 pulls from registry |
4141
| Where build is done | On EC2 | On CI |
4242
| How Docker build layers are cached | Cache is stored on EC2 | GitHub actions has no own Docker cache out of the box, so it should be stored in dedicated place (we use Amazon ECR) |
43-
| Advantages | Cheaper (no egrass traffik from EC2) and faster | Build is done on CI, so EC2 server is not overloaded |
43+
| Advantages | Cheaper (no egrass cache traffik from EC2) and faster | Build is done on CI, so EC2 server is not overloaded |
4444
| Disadvantages | Build on EC2 requires additional server RAM / requires swap / overloads CPU | More terraform code is needed. Extra cost for egress traffik to GitHub for cache transfer |
4545
| Initial build time\* | 3m 13.541s | 3m 54s |
4646
| Rebuild time (changed `index.ts`)\*| 0m 51.653s | 0m 54.120s |
@@ -98,7 +98,7 @@ Drawback is that buildx which is running on GitHub action server will download c
9898

9999
# Prerequisites
100100

101-
I will use you run Ubuntu (Native or WSL2).
101+
I will assume you run Ubuntu (Native or WSL2).
102102

103103
You should have terraform, here is official repository:
104104

0 commit comments

Comments
 (0)