2.Run the following commands to install SQL Server:
sudo yum install -y mssql-server
3.After the package installation finishes, run mssql-conf setup and follow the prompts to set the SA password and choose your edition.
sudo /opt/mssql/bin/mssql-conf setup
4.Once the configuration is done, verify that the service is running:
systemctl status mssql-server
5.To allow remote connections, open the SQL Server port on the firewall on RHEL. The default SQL Server port is TCP 1433. If you are using FirewallD for your firewall, you can use the following commands:
4.For convenience, add /opt/mssql-tools/bin/ to your PATH environment variable. This enables you to run the tools without specifying the full path. Run the following commands to modify the PATH for both login sessions and interactive/non-login sessions:
You can view all of your settings and where they are coming from using:
git config --list --show-origin
Your default branch name
By default Git will create a branch called master when you create a new repository with git init. From Git version 2.28 onwards, you can set a different name for the initial branch.
git config --global init.defaultBranch main
2. Getting a Git Repository
Initializing a Repository in an Existing Directory
You clone a repository with git clone <url>. For example, if you want to clone the Git linkable library called libgit2, you can do so like this:
git clone https://github.com/libgit2/libgit2
If you want to clone the repository into a directory named something other than libgit2, you can specify the new directory name as an additional argument:
$ echo 'My Project' > README
$ git status
On branch master
Your branch is up-to-date with 'origin/master'.
Untracked files:
(use "git add <file>..." to include in what will be committed)
README
nothing added to commit but untracked files present (use "git add" to track)
Tracking New Files
git add README
$ git status
On branch master
Your branch is up-to-date with 'origin/master'.
Changes to be committed:
(use "git restore --staged <file>..." to unstage)
new file: README
Ignoring Files
$ cat .gitignore
*.[oa]
*~
Viewing Your Staged and Unstaged Changes
To see what you’ve changed but not yet staged, type git diff with no other arguments:
git diff
If you want to see what you’ve staged that will go into your next commit, you can use git diff --staged or git diff --cached.
git diff --staged
หรือ
git status -v
Committing Your Changes
git commit -m "Story 182: fix benchmarks for speed"