Devops World

View the certs:

keytool -v -list -keystore /apps/software/jdk1.8.0_92/jre/lib/security/cacerts

Add new cert:

keytool -importcert -alias TESTNAME -keystore /apps/software/jdk1.8.0_92/jre/lib/security/cacerts -file /tmp/test-public-cert.crt

Confirm the addition:

keytool -list -keystore /apps/software/jdk1.8.0_92/jre/lib/security/cacerts -alias TESTNAME

Note: default password for cacerts file in tomcat is “changeit”

SFTP uses SSH protocol, so first we have to install windows version of openssh the server.

Luckily we get the precompiled version of it, so we just have to unzip the contents to a folder. Please note that this installation should be used only in a non-prod environment.

Download link : https://github.com/PowerShell/Win32-OpenSSH/releases/download/3_19_2016/OpenSSH-Win64-1.1.zip (I find that the latest versions give a 1067 error while starting)

Steps:
Inside PowerShell prompt execute below command to bypass execution restrictions:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

cd c:\OpenSSH-Win
.\install-sshlsa.ps1
reboot server

Once server is up, edit c:\OpenSSH-Win\sshd_config
Modify below line in config file:
subsystem sftp c:\OpenSSH-Win\sftp-server.exe -d C:/Users/ftp-testing/Work

-d –> default working directory for ftp logins

Open cmd in elevated rights
cd c:\OpenSSH-Win
sshd.exe install

It will show installation successful.

Open services.msc and go to sshd
Make sure sshd starts “Automatically”

Generate SSH keys for the server (they are necessary to start sshd):
ssh-keygen.exe –A

Start SSHD service

Connect ssh using some client tools, like, winscp.

Common screen commands that we can use are:

Starting Named Session:
screen -S session_name

Detach from screen session without killing that session:
Ctrl+a d

Reattaching a screen session:
screen -r (works if only one session is present)

List all existing screen sessions:
screen -ls

If there are more than one screen session, we should mention the screen session id:
screen -r

To install multiple npm versions and switch between them, you should use Node Version Manager (nvm)

nvm can be installed by the below commands for a particular user where the commands are run:

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.34.0/install.sh | bash

After successful completion, if you want to install a specific Node Js version use the below command:
nvm install 8.9.4

Finally, check npm version using:
npm version

To check node js version:
node -v

Sometimes it is useful to create a working copy that is made out of a number of different checkouts. For example, you may want different files or subdirectories to come from different locations in a repository, or perhaps from different repositories altogether. If you want every user to have the same layout, you can define the svn:externals properties to pull in the specified resource at the locations where they are needed.

Command to get the externals already set for a folder:

svn propget svn:externals <folder_name>

To edit an already assigned external or add a new external to a folder use the command:

1. first set an appropriate editor to edit the externals:

              SVN_EDITOR=/bin/vi
              export SVN_EDITOR

2.  Then use the below command:

svn propedit svn:externals <folder_name> <absolute_path_to_the_folder>

eg: svn propedit svn:externals test /home/kevin/modules/configuration/test

The above command will open the editor “vi” and we can provide the necessary externals url there and save the file.

eg: $ svn propget svn:externals test
/svn/myrepo/application/branches/new1.4.1 suite

Note that “suite” is a subfolder inside “test” directory to which the external svn path has to be fetched.

That means, the svn branch “/svn/myrepo/application/branches/new1.4.1” will get synced to the folder /home/kevin/modules/configuration/test/suite whenever it is referenced.