The TechnoArt of LINUX & Windows

 This post explains migration of application from VM based deployments to containers as micro services. For example, the application runs on Java on Linux virtual machines. We need to collect some information about the application to containerize them and run as Docker images. Application Discovery: First, we need to do Application Discovery by having meetings with the application developer team to Discover and get the required information, like: Application run environment - whether the app uses java 8/9 etc. Environment variables - which environment variables are used for the application, so that same have to be configured on the container. Configurations - any OS level configurations like directory structure or path etc. Build commands - to collect the commands and parameters to build the application Start/stop commands - commands or scripts required to start and stop the application Ports - the list of ports used by the application while running on a Linux VM, so that the same ...

 The size of a Git repository increases with time. It may grow to few GB size, like 2 GB or 5GB or even more. Cloning a 2 GB Git repository may take about 10 minutes, which slows down productivity of the developers. There are three ways to save time during cloning a Git repository. 1. Cloning single Git branch: You can clone one one branch you want. This will ignore other branches and will save cloning time. git --single-repo -b <name of branch> 2. Ignoring commit history: During normal cloning, git will clone all commit history. If you don't need all the history at once, you can just clone the last one commit history only. This will save significant time and disk space during cloning. git --depth 1 3. Referencing your local cloned git repository: If you have already cloned your repository on your laptop or desktop, then you can use the --reference option in git command. This option will point to your local git repository and will reference the remote git repository only if n...