Skip to content

Commit f391b43

Browse files
30.11 update app-versioning.md
create lesson-6.md
1 parent 6b37d37 commit f391b43

File tree

2 files changed

+24
-2
lines changed

2 files changed

+24
-2
lines changed

Course/app-versioning.md

Lines changed: 20 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
### After local connection to AWS EC2 instance:
1+
### Application versioning:
22
* `1 . 4 . 2` - Semantic numbering (Major . Minor . Patch)
33
* `Major changes` - related to incompatible API changes
44
* Replaced Framework
@@ -8,4 +8,22 @@
88
* Bigger Bugfix
99
* `Patch changes` - related to small bugfixes & changes, which are backward compatible
1010
* Small changes
11-
* Bugfix
11+
* Bugfix
12+
13+
### Dynamic Versioning:
14+
* Dynamically set an incremented version when we build the Docker image
15+
16+
### Pass Env Vars as Dotenv Artifact:
17+
* Best practise when use 5 or more env variables
18+
* `Dotenv file` is a lightweight npm package that automatically loads
19+
environment variables from a .env file into the process
20+
* Change in build_image:
21+
* instead of `- echo $VERSION > version-file.txt`
22+
* type `- echo "VERSION=$VERSION" >> build.env`
23+
* `Dotenv artifact` - Save the .env file as a dotenv artifact
24+
* `artifacts: reports: dotenv: build.env`
25+
* Usage of these env vars:
26+
* Collected variables are registered as runtime-created variables of the job
27+
* Jobs in later stages can use the variable in scripts
28+
* No need to `- export VERSION=$(cat version-file.txt)` in push_image or deploy_to_dev - auto export
29+
* No need to download artifacts cause they are env variables already - auto export

Course/lesson-6.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
## Build
2+
3+
### Final:
4+
* Run

0 commit comments

Comments
 (0)