Introduction
Hello there! Do you remember our last conversation about mastering Git? Now, it's time to delve into a more exciting part of your Dev...
For further actions, you may consider blocking this person and/or reporting abuse
Dunno if this is a me thing, or worth mentioning in the article, but it took me quite a while to get used to not putting spaces around the
=when defining variables.Also, any plans on making a more advanced guide too?
I did quick research and apparently the preferred way to use
=in bash is without spaces unlike many other languages. Even though it's not explicitly mentioned here, you can see that Google themselves have usedvariable=valueso many times in their official code style guide.It's not just preferred, you actually can't put spaces around the
=Thank you for the observation and thank you for reading 😊
Well noted, thank you for reading 💪
it's just for the article's sake but thanks for the observation, well noted .
Yes, I am working on advanced guide too. Thank you for reading 😊
Nice article. It is a good idea to use fenced code blocks rather than screenshots for accessibility. Screenshots make things more difficult for people who use screen readers. Other than that, fenced code blocks are easy to copy and paste and, therefore, test the proposed code.
Thank you so much, duly noted.
This is a good and straightforward tutorial, Good job Arby! However the title is a bit misleading since you didn't mention any DevOps specific commands.
Thank you so much, I am glad you found it valuable 🙏
Awesome explanation 😸 thanks 🙏
Thank you 👍 I'm glad you find my article valuable
Good Stuff. Thank you for sharing.
great !
Can I ask where you download MINGW64? I just can't find where to download it.
check these links out:
winlibs.com/
sourceforge.net/projects/mingw-w64...
Oh my gosh, thank you so much! You just made my day
Great article! Utilizing fenced code blocks instead of screenshots is a smart move for accessibility. Screenshots pose challenges for those using screen readers. Additionally, fenced code blocks are user-friendly, allowing for easy copying, pasting, and testing of the provided code.
Simple and amazing !!!
I'm not a DevOps guy, but I loved this!
I am happy to hear this! Thank you so much
Nice Post
Nice article, Straight to the point!
Awesome explanation!!
This next step in the DevOps journey promises to be both challenging and rewarding. Tiger exchange