Monday, August 31, 2020

Git command reference (Launchschool)

CommandDescription

  • git status Run this command any time and often to check on the status of the files in the git repository.
  • git add This command stages changed files, readying them to be wrapped into the next commit.
  • git commit This command commits staged files, wrapping them into a commit. A historical record of commits is what we refer to as a codebase's version or commit history.
  • git log View the repository's commit history.
These are common Git commands used in various situations:

start a working area (see also: git help tutorial)
   clone             Clone a repository into a new directory
   init              Create an empty Git repository or reinitialize an existing one

work on the current change (see also: git help everyday)
   add               Add file contents to the index
   mv                Move or rename a file, a directory, or a symlink
   restore           Restore working tree files
   rm                Remove files from the working tree and from the index
   sparse-checkout   Initialize and modify the sparse-checkout

examine the history and state (see also: git help revisions)
   bisect            Use binary search to find the commit that introduced a bug
   diff              Show changes between commits, commit and working tree, etc
   grep              Print lines matching a pattern
   log               Show commit logs
   show              Show various types of objects
   status            Show the working tree status

grow, mark and tweak your common history
   branch            List, create, or delete branches
   commit            Record changes to the repository
   merge             Join two or more development histories together
   rebase            Reapply commits on top of another base tip
   reset             Reset current HEAD to the specified state
   switch            Switch branches
   tag               Create, list, delete or verify a tag object signed with GPG

collaborate (see also: git help workflows)
   fetch             Download objects and refs from another repository
   pull              Fetch from and integrate with another repository or a local branch
   push              Update remote refs along with associated objects

'git help -a' and 'git help -g' list available subcommands and some
concept guides. See 'git help <command>' or 'git help <concept>'
to read about a specific subcommand or concept.
See 'git help git' for an overview of the system.

================================

abc@ubuntu:~/src/git_basics/.git$ git remote
origin
abc@ubuntu:~/src/git_basics/.git$ git remote -v
origin https://github.com/nvijaysudhakar/my-test-repository.git (fetch)
origin https://github.com/nvijaysudhakar/my-test-repository.git (push)
abc@ubuntu:~/src/git_basics/.git$ git remote rm
usage: git remote remove <name>

abc@ubuntu:~/src/git_basics/.git$ git remote remove origin
abc@ubuntu:~/src/git_basics/.git$ 

==================================

Examples
========

abc@ubuntu:~/src$ 
abc@ubuntu:~/src$ 
abc@ubuntu:~/src$ mkdir git_basics
abc@ubuntu:~/src$ cd git_basics
abc@ubuntu:~/src/git_basics$ ll
total 8
drwxrwxr-x 2 abc abc 4096 Aug 31 21:10 ./
drwxrwxr-x 9 abc abc 4096 Aug 31 21:10 ../
abc@ubuntu:~/src/git_basics$ echo '# README #' > README.md
abc@ubuntu:~/src/git_basics$ ll
total 12
drwxrwxr-x 2 abc abc 4096 Aug 31 21:10 ./
drwxrwxr-x 9 abc abc 4096 Aug 31 21:10 ../
-rw-rw-r-- 1 abc abc   11 Aug 31 21:10 README.md
abc@ubuntu:~/src/git_basics$ echo '# LICENSE #' > LICENSE.md
abc@ubuntu:~/src/git_basics$ ll
total 16
drwxrwxr-x 2 abc abc 4096 Aug 31 21:10 ./
drwxrwxr-x 9 abc abc 4096 Aug 31 21:10 ../
-rw-rw-r-- 1 abc abc   12 Aug 31 21:10 LICENSE.md
-rw-rw-r-- 1 abc abc   11 Aug 31 21:10 README.md
abc@ubuntu:~/src/git_basics$ git init
Initialized empty Git repository in /home/abc/src/git_basics/.git/
abc@ubuntu:~/src/git_basics$ ll
total 20
drwxrwxr-x 3 abc abc 4096 Aug 31 21:10 ./
drwxrwxr-x 9 abc abc 4096 Aug 31 21:10 ../
drwxrwxr-x 7 abc abc 4096 Aug 31 21:10 .git/
-rw-rw-r-- 1 abc abc   12 Aug 31 21:10 LICENSE.md
-rw-rw-r-- 1 abc abc   11 Aug 31 21:10 README.md
abc@ubuntu:~/src/git_basics$ touch .gitignore
abc@ubuntu:~/src/git_basics$ ll
total 20
drwxrwxr-x 3 abc abc 4096 Aug 31 21:11 ./
drwxrwxr-x 9 abc abc 4096 Aug 31 21:10 ../
drwxrwxr-x 7 abc abc 4096 Aug 31 21:10 .git/
-rw-rw-r-- 1 abc abc    0 Aug 31 21:11 .gitignore
-rw-rw-r-- 1 abc abc   12 Aug 31 21:10 LICENSE.md
-rw-rw-r-- 1 abc abc   11 Aug 31 21:10 README.md
abc@ubuntu:~/src/git_basics$ ll
total 24
drwxrwxr-x 3 abc abc 4096 Aug 31 21:11 ./
drwxrwxr-x 9 abc abc 4096 Aug 31 21:10 ../
drwxrwxr-x 7 abc abc 4096 Aug 31 21:10 .git/
-rw-rw-r-- 1 abc abc   43 Aug 31 21:11 .gitignore
-rw-rw-r-- 1 abc abc   12 Aug 31 21:10 LICENSE.md
-rw-rw-r-- 1 abc abc   11 Aug 31 21:10 README.md
abc@ubuntu:~/src/git_basics$ git status
On branch master

No commits yet

Untracked files:
  (use "git add <file>..." to include in what will be committed)
.gitignore
LICENSE.md
README.md

nothing added to commit but untracked files present (use "git add" to track)
abc@ubuntu:~/src/git_basics$ git add .gitignore
abc@ubuntu:~/src/git_basics$ ll
total 24
drwxrwxr-x 3 abc abc 4096 Aug 31 21:11 ./
drwxrwxr-x 9 abc abc 4096 Aug 31 21:10 ../
drwxrwxr-x 7 abc abc 4096 Aug 31 21:12 .git/
-rw-rw-r-- 1 abc abc   43 Aug 31 21:11 .gitignore
-rw-rw-r-- 1 abc abc   12 Aug 31 21:10 LICENSE.md
-rw-rw-r-- 1 abc abc   11 Aug 31 21:10 README.md
abc@ubuntu:~/src/git_basics$ git status
On branch master

No commits yet

Changes to be committed:
  (use "git rm --cached <file>..." to unstage)
new file:   .gitignore

Untracked files:
  (use "git add <file>..." to include in what will be committed)
LICENSE.md
README.md

abc@ubuntu:~/src/git_basics$ git add LICENSE.md
abc@ubuntu:~/src/git_basics$ git status
On branch master

No commits yet

Changes to be committed:
  (use "git rm --cached <file>..." to unstage)
new file:   .gitignore
new file:   LICENSE.md

Untracked files:
  (use "git add <file>..." to include in what will be committed)
README.md

abc@ubuntu:~/src/git_basics$ git add README.md
abc@ubuntu:~/src/git_basics$ git status
On branch master

No commits yet

Changes to be committed:
  (use "git rm --cached <file>..." to unstage)
new file:   .gitignore
new file:   LICENSE.md
new file:   README.md

abc@ubuntu:~/src/git_basics$ git commit -m 'Add first project files'
[master (root-commit) 81bb26c] Add first project files
 3 files changed, 4 insertions(+)
 create mode 100644 .gitignore
 create mode 100644 LICENSE.md
 create mode 100644 README.md
abc@ubuntu:~/src/git_basics$ git status
On branch master
nothing to commit, working tree clean
abc@ubuntu:~/src/git_basics$ git log
commit 81bb26c447474fb8cba25e5fd91b0bb425822a79 (HEAD -> master)
Author: Maya Angelou <MayaAngelou@poets.com>
Date:   Mon Aug 31 21:13:52 2020 +1000

    Add first project files
abc@ubuntu:~/src/git_basics$ 


Git Cheat Sheet (Ruby Garage)









Monday, August 17, 2020

Java Refresher

  • Byte = 8 bits
  • Short - 16 bits
  • Int - 32 bits
  • Long - 64 bits
  • Float - 32 bits (not precise, don't use for financials)
  • Double - 64 bits - not very precise, don't use for financials.
  • Char - 16 bits
  • Boolean - True/ False
  •  Control + L = Clear Screen

JVM VS JRE VS JDK




Rancher

 Rancher is a Kubernetes management platform. 

Wednesday, August 12, 2020

Webservices (Guru99.com)

What is a Webservice?

  • A web service is a software module that is designed to perform a certain set of tasks.
  • It can be searched over the network (on the server where it it hosted) and invoked accordingly. 

  • The requests to the server are made thru REMOTE PROCEDURE CALLS (RPC).
  • The main component of a web service is the data which is transferred between the client and server and is in XML format. 
  • So when applications talk to each other, they do in XML. 
  • Webservice uses a SOAP protocol for sending XML data in between the applications. 
  • Data is sent over in HTTP. 

Why do you need a Webservice?

  • Web services provide a common platform that allows multiple applications built on various programming languages (Java, .NET, Angular JS, Node.js, etc.) to have the ability to communicate with each other. (Don't have to bother in what language the front-end is written.)

Types of web services

  • SOAP web services

  • RESTful web services


 

Thursday, August 06, 2020

Inception meeting checklist

Inception Meeting Pre-Requisites 

  • Completed Design Kit (UI/UX) -fair understanding of the UI / UX
  • Completed Architectural Design - fair understanding of the solution architecture
  • Completed scoping document - scope clarity

Meeting Invite Checklist

  • Ensure all stakeholders have been invited to the INCEPTION - confirm with the Product Owner
  • Ensure all teams that are impacted in any way are iincluded in the inception - to align timelines
  • Include the proposed agenda (topic - duration - speaker)
  • Include any confluence links in the meeting invite to allow for preparation.

Before Meeting

  • Set-up Trello Board for story mapping session
  • Set-up Ideaz Board to capture RAID/Parking Lot 
  • Confirm all presenters  have accepted the invite and are aware they are to present
AGENDA

  • Suggested inception agenda/format.  
  • Each  Presentation should occur on a different day to allow time to absorb inception artefacts,  
  • keep each inception check-in efficient and mindful of everyone's time.
Inception meeting Presentation (All to attend)

  • Introductions
  • Project Overview - Vision/Goals/Deliverables (Product Owner)
  • Architectural Design Walk-thru (Project Architect)
  • Design Kit Walk-thru (UI/UX Designer)
  • RAID checkpoint (Risks, Assumptions, Issues, Decision, Parking Lot)
  • Story Mapping Session

SQL Essential Training - LinkedIn

Datum - piece of information Data is plural of datum. Data are piece of information - text, images or video. Database - collection of data. ...