Search for a command to run...
Vincent is a Cloud DevOps Engineer with years of hands-on experience supporting, automating, and optimizing mission-critical deployments in Azure and AWS, leveraging configuration management, CI/CD, and DevOps processes. Strong background in Technical Operations and customer relations.
No comments yet. Be the first to comment.
Yo, keeping your AWS IAM setup locked down ain't easy. You could spend hours digging through users, roles, and policies, or you could let IAMGuard do the heavy lifting. This tool scans your AWS IAM setup, flags security risks, and drops clean reports...
Introduction Hey everyone! Want to dip your toes into cloud computing without feeling overwhelmed? Let’s build something cool: A serverless website uptime monitor using AWS. Imagine a tool that checks if a site’s up or down every 5 minutes, logs the ...
Struggling to manage your AWS resources effectively? You're not alone. But what if you could simplify tasks and boost collaboration directly within your chat platform? This step-by-step video demo unveils the power of ChatOps with Microsoft Teams for...
As a mentor, one of the most insightful questions I've recently received from a mentee revolves around the journey to career success. The inquiry delves into the intricate details of navigating through a professional landscape, and it sparked a thoug...
Hey everyone, I want to discuss AWS Elastic Beanstalk in this video. This video is designed to help you learn and deploy with AWS Elastic Beanstalk, and we're going to do that by doing a follow-along and a little lecture. So that's the goal of this ...
Have you finished configuring your terminal?
Looking so cool now, but while can't I make use of my favorite tools after the Pimp?
I have encountered this issue every time I pimp my terminal, so today I have decided to share with everyone how I did it.
Why does this happen
This happens because when installing NVM it adds code to ~/.bashrc, as your default terminal now uses zsh and not bash it never reads ~/.bashrc and therefore never loads NVM.
To avoid this at installation, you can simply put zsh at the end of the curl command.
Example:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.2/install.sh | zsh
"In other words: this is NVMs fault, not yours."
Solution:
To fix this, all we need to do is tell the ~/.zshrc to load nvm on the prompt.
From your terminal, open the .zshrc file with your favorite editor, nano will be just fine.
nano .zshrc
And paste the following line of command at the top:
. "$HOME/.nvm/nvm.sh"
Save the file ctrl + s and ctrl + x to exit
Restart your terminal, everything should work just fine now.
See you soon!