Semantic versioning is a crucial aspect of package management in npm (Node Package Manager). It helps developers understand the nature of changes in a package and manage dependencies effectively. This post will explore the right way to implement automatic semantic versioning in npm projects.

Just a reminder to update your permission(if you are using one)

A recent experience upgrading an old Bitnami chart highlighted this issue. Bitnami introduced breaking changes in its subchart,

ECR uses IAM authentication to control access to your repositories. When you authenticate with ECR, you receive a token that's valid for 12 hours. After this period, the token expires, and your Kubernetes pods may fail to pull images from ECR. By implementing an automatic rotation mechanism, we can avoid these potential disruptions.

If you've ever upgraded your PostgreSQL database with

Monitoring Application Load Balancer(ALB) aggregated metrics in CloudWatch is easy, but if you want more insight from the access log, it is not enabled by default.

Deploy with git was an awesome feature provided by Netlify which can do continuous deployment by connecting a Git repository and keeping them in sync. It was a breeze since it was easy to set up. but things become complex when they make a few changes: the private repository won’t work unless you upgrade to Pro plan or make the repository public.

For seamless use of S3 under on-premise or local development with minio there’s one more config you want to set up.

If you're tired of typing your password every time you want to SSH into a remote server, ssh-copy-id is the tool for you. It allows you to copy your public key to a remote server's authorized_keys file in one command

It’s good for decoupling third-party services from your codebase using Firebase Extension and Functions If you were running your infra on GCP.