Skip to main content

Git Commit

git commit saves your staged changes to the local repository as a permanent snapshot. It creates a new commit object with a unique identifier based on the changes made, along with a message that describes them. This is the fifth post in this site's Git command guide, following Git Add . (All).

Git Add

git add is the command that stages changes from your working directory into Git's index, marking them to be included in the next commit. Staging is an intermediate step that gives you precise control — you can add one file at a time, leaving other modified files unstaged until a later commit. This is the third post in this site's Git command guide, following Git Clone.

Git Clone

git clone copies an entire remote repository locally. This guide covers shallow clones with --depth, cloning specific branches, submodules, SSH vs HTTPS, and fixing a Permission denied (publickey) error.

Apache Commons Collection – MultiValuedMap

Apache Commons Collections MultiValuedMap compared against Guava Multimap and a vanilla nested Map of Lists, with a realistic form-validation-errors use case, annotated code, sample output, and FAQs.

Git Init

git init creates a new local Git repository. This guide covers the basic command, setting main as the default branch name with -b and init.defaultBranch, and a full flag reference.

Geolocation API

The browser Geolocation API explained with the HTTPS-only requirement, navigator.permissions.query usage, and full error handling for all three PositionError cases, plus FAQs and See Also.

Setting up your Angular development environment

Hey there, fellow coders! Ever wanted to build amazing web applications with Angular but felt a bit overwhelmed by the setup process? Don't worry, you're not alone! Today, we're going to walk through setting up your local environment, making it as easy as pie. What You'll Need Before We Begin Before we jump into the nitty-gritty, let's make sure you're familiar with a few basics: JavaScript, HTML, and CSS: These are the building blocks of web development. A solid understanding of these will make your Angular journey much smoother. Command Line Interface (CLI): You'll be using commands in your terminal or command prompt. Don't worry, we'll guide you through them. TypeScript (Optional): Angular is built with TypeScript, which adds static typing to JavaScript. While it's helpful, you can start without deep knowledge. Let's Get Started: Dependencies and Installation 1. Node.js and npm: Angular CLI relies on Node.js and npm (Node Package Manager). Head over to the official Node.js (https://nodejs.org/en) website and download the latest LTS (Long Term Support) version by clicking Download Node.js button. Once it is downloaded, double click on the downloaded file to start its installation. Installing Node.js will automatically install npm. As stated in the angular documentation, it is important to use an active or maintenance LTS version of node.js. Please refer to the angular version compatibility guide for more details.

Spring Cloud: Getting started with Hystrix Dashboard

⚠️ This tutorial is outdated. Hystrix Dashboard was removed from Spring Cloud and does not work with Spring Boot 3.x. The modern approach is Resilience4j metrics with Prometheus & Grafana — see the Spring Cloud Netflix migration guide. This post remains online for teams maintaining legacy systems. This is a quick tutorial on Hystrix dashboard. Hystrix dashboard allows you to view the overall status of your Spring cloud application at a single glance. It provides access to vital metrics of your application and gives you a graphical representation of those for better understanding. This post is the continuation of Spring Cloud: Adding Hystrix Circuit Breaker and Spring Cloud: Playing with Hystrix Circuit Breaker. Please go through those post, if you haven't. Those posts explain about Hystrix circuit breaker. TL;DR You can download whole project by clicking following link. Spring Cloud (V2.3.1) Hystrix DashboardDownload

Spring Cloud Config Server on Spring Boot 3.x: Git Mode, Native Mode, and Runtime Refresh

Spring Cloud Config is, alongside Eureka, one of the two survivors of the original Spring Cloud stack — still maintained, still the standard answer for centralized configuration outside Kubernetes. This post is a complete rewrite of my 2020 Config Server tutorials for Spring Boot 3.x: a Config Server backed by Git (with native/filesystem mode for local development), clients using the modern spring.config.import mechanism instead of the long-gone bootstrap.properties, and runtime refresh that actually works.

Spring Cloud: Exploring Spring Cloud Config Server (Native Mode)

⚠️ This tutorial covers an old Spring Cloud version. Spring Cloud Config is still maintained, but this setup targets Spring Boot 2.x. For Spring Boot 3.x configuration (Git and native mode), see the updated Spring Cloud Config Server guide and the Spring Cloud Netflix migration guide. This is a quick tutorial on Spring Cloud Config Server. In brief, Spring cloud config allows you to have applications/micro-services configuration at a centralized place. Since we are working on spring micro-services, in production we may have hundreds of micro-services running together. Now if we want to manage configuration for hundreds of those micro-services then it would be a big pain if we do it manually. Instead, we will use Spring cloud config server to manage that configuration from a central place. TL;DR You can download whole project by clicking following link. Spring Cloud (V2.3.1) Config Server in Native ModeDownload Spring Cloud (V2.3.1) Sample Configuration for Config Server in Native ModeDownload