woose/90DaysOfDevOps
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #107 from Rafat97/patch-3

Browse Source 
Update Broken Link
This commit is contained in:
Michael Cade 2022-05-14 06:51:49 +01:00 committed by GitHub
commit 604eeb52b8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Days/day19.md
View File

@ -25,7 +25,7 @@ I think another thing I am at least hearing is that hands-on scripting questions
As with a lot of things we are covering in this whole 90 days, the only real way to learn is through doing. Hands-on experience is going to help soak all of this into your muscle memory. As with a lot of things we are covering in this whole 90 days, the only real way to learn is through doing. Hands-on experience is going to help soak all of this into your muscle memory.
First of all, we are going to need a text editor. On [Day 17](Day17.md) we covered probably the two most common text editors and a little on how to use them. First of all, we are going to need a text editor. On [Day 17](day17.md) we covered probably the two most common text editors and a little on how to use them.
Let's get straight into it and create our first shell script. Let's get straight into it and create our first shell script.
@ -48,7 +48,7 @@ I sometimes use figlet, a program we installed earlier in the Linux section to c
![](Images/Day19_Linux1.png) ![](Images/Day19_Linux1.png)
All of the commands we have been through earlier in this Linux section ([Day15](Day15.md)) could be used here as a simple command to test our script. All of the commands we have been through earlier in this Linux section ([Day15](day15.md)) could be used here as a simple command to test our script.
Let's add a simple block of code to our script. Let's add a simple block of code to our script.