learn/learn.softwareshinobi.com
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

automated terminal push
Some checks are pending
learn org at code.softwareshinobi.com/learn.softwareshinobi.com/pipeline/head Build queued...
Details

Browse Source
This commit is contained in:
Software Shinobi
2025-06-05 20:01:56 -04:00
parent f5ee235c3f
commit b1cda1e79f
235 changed files with 957 additions and 13720 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
.dockerignore Normal file
View File

@@ -0,0 +1,11 @@
.git
.pristine
.trash
.recycle
.backup
.template

0
server/.hushlogin → .gitignore vendored Executable file → Normal file
View File

238
.recycle/compose.full.yaml
View File

@@ -1,238 +0,0 @@
version: "3.8"
services:
shinobi-academy-linux-public:
build:
context: servers/public
dockerfile: Dockerfile
container_name: shinobi-academy-linux-public
hostname: miura
image: softwareshinobi/shinobi-academy-linux:miura
domainname: sian.embanet.softwareshinobi.digital
ports:
- "2222:22"
shinobi-academy-linux-private:
build:
context: servers/private
dockerfile: Dockerfile
container_name: shinobi-academy-linux-private
hostname: veneno
image: softwareshinobi/shinobi-academy-linux:veneno
domainname: sian.embanet.softwareshinobi.digital
ports:
- "3333:22"
shinobi-academy-linux-landing:
container_name: shinobi-academy-linux-landing
image: softwareshinobi/shinobi-academy-linux-landing
build:
context: landing
dockerfile: Dockerfile
ports:
- 8888:80
#####
##########################################
##
## software shinobi studio situation
##
##########################################
software-shinobi-desktop1:
build:
context: desktops/studio
dockerfile: Dockerfile
container_name: software-shinobi-desktop1
hostname: hyperion
image: softwareshinobi/software-shinobi-desktop
restart: unless-stopped
## deploy:
##
## resources:
##
## limits:
##
## cpus: 2
##
## memory: 3.5G
##
## reservations:
##
## cpus: 1
##
## memory: 2.0G
volumes:
- .volumes/desktop:/root
domainname: desktop.softwareshinobi.digital
environment:
TZ: America/Bogota
USER_UID: 1000
USER_GID: 1000
USER: root
PASSWORD: passw0rd
HTTP_PASSWORD: passw0rd
VIRTUAL_HOST: desktop.softwareshinobi.digital
LETSENCRYPT_HOST: desktop.softwareshinobi.digital
software-shinobi-desktop2:
build:
context: desktops/coding
dockerfile: Dockerfile
container_name: software-shinobi-desktop2
hostname: hyperion
image: softwareshinobi/software-shinobi-desktop
restart: unless-stopped
## deploy:
##
## resources:
##
## limits:
##
## cpus: 2
##
## memory: 3.5G
##
## reservations:
##
## cpus: 1
##
## memory: 2.0G
volumes:
- .volumes/desktop2:/root
domainname: desktop.softwareshinobi.digital
environment:
TZ: America/Bogota
USER_UID: 1000
USER_GID: 1000
USER: root
PASSWORD: passw0rd
HTTP_PASSWORD: passw0rd
VIRTUAL_HOST: desktop.softwareshinobi.digital
LETSENCRYPT_HOST: desktop.softwareshinobi.digital
software-shinobi-desktop3:
build:
context: desktops/instructor
dockerfile: Dockerfile
container_name: software-shinobi-desktop3
hostname: hyperion
image: softwareshinobi/software-shinobi-desktop:instructor
restart: unless-stopped
## deploy:
##
## resources:
##
## limits:
##
## cpus: 2
##
## memory: 3.5G
##
## reservations:
##
## cpus: 1
##
## memory: 2.0G
volumes:
- .volumes/desktop3:/root
domainname: desktop.softwareshinobi.digital
environment:
TZ: America/Bogota
USER_UID: 1000
USER_GID: 1000
USER: root
PASSWORD: passw0rd
HTTP_PASSWORD: passw0rd
VIRTUAL_HOST: desktop.softwareshinobi.digital
LETSENCRYPT_HOST: desktop.softwareshinobi.digital

11
.recycle/desktops/coding/.dockerignore
View File

@@ -1,11 +0,0 @@
.volumes
.git
.import
.stash
.recycle
.trash

11
.recycle/desktops/coding/.gitignore vendored
View File

@@ -1,11 +0,0 @@
.volumes
.git
.import
.stash
.recycle
.trash

9
.recycle/desktops/coding/Dockerfile
View File

@@ -1,9 +0,0 @@
FROM dorowu/ubuntu-desktop-lxde-vnc as desktopBase
RUN rm /etc/apt/sources.list.d/google-chrome.list
RUN apt update && apt install -y recordmydesktop kdenlive zip docker-compose curl wget net-tools keepassx vlc dos2unix git filezilla openjdk-17-jdk maven
COPY /provision .
RUN bash netbeans.bash

119
.recycle/desktops/coding/compose.yaml
View File

@@ -1,119 +0,0 @@
services:
##########################################
##
## reverse proxy and ssl things
##
##########################################
software-shinobi-proxy:
container_name: software-shinobi-proxy
hostname: hyperion
image: nginxproxy/nginx-proxy
restart: unless-stopped
ports:
- 80:80
- 443:443
volumes:
- /var/run/docker.sock:/tmp/docker.sock:ro
- /var/docker/nginx/html:/usr/share/nginx/html
- /var/docker/nginx/certs:/etc/nginx/certs
- /var/docker/nginx/vhost:/etc/nginx/vhost.d
logging:
options:
max-size: "10m"
max-file: "3"
software-shinobi-letsencrypt:
container_name: software-shinobi-letsencrypt
image: jrcs/letsencrypt-nginx-proxy-companion
restart: unless-stopped
volumes_from:
- software-shinobi-proxy
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /var/docker/nginx/acme:/etc/acme.sh
environment:
DEFAULT_EMAIL: the.software.shinobi@gmail.com
##########################################
##
## software shinobi studio situation
##
##########################################
software-shinobi-desktop:
container_name: software-shinobi-desktop
hostname: hyperion
image: softwareshinobi/software-shinobi-studio
restart: unless-stopped
## deploy:
##
## resources:
##
## limits:
##
## cpus: 2
##
## memory: 3.5G
##
## reservations:
##
## cpus: 1
##
## memory: 2.0G
volumes:
- .volumes/desktop:/root
domainname: desktop.softwareshinobi.digital
environment:
TZ: America/Bogota
USER_UID: 1000
USER_GID: 1000
USER: root
PASSWORD: passw0rd
HTTP_PASSWORD: passw0rd
VIRTUAL_HOST: desktop.softwareshinobi.digital
LETSENCRYPT_HOST: desktop.softwareshinobi.digital

BIN
.recycle/desktops/coding/files/Pictures/desktop.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 20 KiB

37
.recycle/desktops/coding/provision/netbeans.bash
View File

@@ -1,37 +0,0 @@
#!/bin/bash
set -e
set -x
##
## create the apps dir and populate with unzipped netbeans content
##
ls
mkdir /apps
cd /apps
##
ls
wget https://dlcdn.apache.org/netbeans/netbeans/21/netbeans-21-bin.zip
ls
mv netbeans-21-bin.zip netbeans.zip
ls
unzip netbeans.zip
ls
pwd
##
##
##

17
.recycle/desktops/coding/studio.bash
View File

@@ -1,17 +0,0 @@
#!/bin/bash
set -e
set -x
reset
clear
docker-compose build
docker-compose pull
docker-compose down
docker-compose up -d

11
.recycle/desktops/instructor/.dockerignore
View File

@@ -1,11 +0,0 @@
.volumes
.git
.import
.stash
.recycle
.trash

11
.recycle/desktops/instructor/.gitignore vendored
View File

@@ -1,11 +0,0 @@
.volumes
.git
.import
.stash
.recycle
.trash

11
.recycle/desktops/instructor/Dockerfile
View File

@@ -1,11 +0,0 @@
FROM dorowu/ubuntu-desktop-lxde-vnc as desktopBase
RUN rm /etc/apt/sources.list.d/google-chrome.list
RUN apt update && apt install -y recordmydesktop shotcut kdenlive zip curl wget net-tools git
##kdenlive zip docker-compose curl wget net-tools keepassx vlc dos2unix git filezilla openjdk-17-jdk maven
COPY /provision .
RUN bash netbeans.bash

63
.recycle/desktops/instructor/compose.yaml
View File

@@ -1,63 +0,0 @@
services:
##########################################
##
## software shinobi studio situation
##
##########################################
software-shinobi-desktop:
build:
context: .
dockerfile: Dockerfile
container_name: software-shinobi-desktop
hostname: hyperion
image: softwareshinobi/software-shinobi-studio
restart: unless-stopped
## deploy:
##
## resources:
##
## limits:
##
## cpus: 2
##
## memory: 3.5G
##
## reservations:
##
## cpus: 1
##
## memory: 2.0G
volumes:
- .volumes/desktop:/root
domainname: desktop.softwareshinobi.digital
environment:
TZ: America/Bogota
USER_UID: 1000
USER_GID: 1000
USER: root
PASSWORD: passw0rd
HTTP_PASSWORD: passw0rd
VIRTUAL_HOST: desktop.softwareshinobi.digital
LETSENCRYPT_HOST: desktop.softwareshinobi.digital

BIN
.recycle/desktops/instructor/files/Pictures/desktop.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 20 KiB

37
.recycle/desktops/instructor/provision/netbeans.bash
View File

@@ -1,37 +0,0 @@
#!/bin/bash
set -e
set -x
##
## create the apps dir and populate with unzipped netbeans content
##
ls
mkdir /apps
cd /apps
##
ls
wget https://dlcdn.apache.org/netbeans/netbeans/21/netbeans-21-bin.zip
ls
mv netbeans-21-bin.zip netbeans.zip
ls
unzip netbeans.zip
ls
pwd
##
##
##

17
.recycle/desktops/instructor/studio.bash
View File

@@ -1,17 +0,0 @@
#!/bin/bash
set -e
set -x
reset
clear
docker-compose build
docker-compose pull
docker-compose down
docker-compose up -d

11
.recycle/desktops/studio/.dockerignore
View File

@@ -1,11 +0,0 @@
.volumes
.git
.import
.stash
.recycle
.trash

11
.recycle/desktops/studio/.gitignore vendored
View File

@@ -1,11 +0,0 @@
.volumes
.git
.import
.stash
.recycle
.trash

9
.recycle/desktops/studio/Dockerfile
View File

@@ -1,9 +0,0 @@
FROM dorowu/ubuntu-desktop-lxde-vnc as desktopBase
RUN rm /etc/apt/sources.list.d/google-chrome.list
RUN apt update && apt install -y recordmydesktop kdenlive shotcut zip docker-compose curl wget net-tools keepassx vlc dos2unix git filezilla openjdk-17-jdk maven gradle
COPY /provision .
RUN bash netbeans.bash

119
.recycle/desktops/studio/compose.yaml
View File

@@ -1,119 +0,0 @@
services:
##########################################
##
## reverse proxy and ssl things
##
##########################################
software-shinobi-proxy:
container_name: software-shinobi-proxy
hostname: hyperion
image: nginxproxy/nginx-proxy
restart: unless-stopped
ports:
- 80:80
- 443:443
volumes:
- /var/run/docker.sock:/tmp/docker.sock:ro
- /var/docker/nginx/html:/usr/share/nginx/html
- /var/docker/nginx/certs:/etc/nginx/certs
- /var/docker/nginx/vhost:/etc/nginx/vhost.d
logging:
options:
max-size: "10m"
max-file: "3"
software-shinobi-letsencrypt:
container_name: software-shinobi-letsencrypt
image: jrcs/letsencrypt-nginx-proxy-companion
restart: unless-stopped
volumes_from:
- software-shinobi-proxy
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /var/docker/nginx/acme:/etc/acme.sh
environment:
DEFAULT_EMAIL: the.software.shinobi@gmail.com
##########################################
##
## software shinobi studio situation
##
##########################################
software-shinobi-desktop:
container_name: software-shinobi-desktop
hostname: hyperion
image: softwareshinobi/software-shinobi-studio
restart: unless-stopped
## deploy:
##
## resources:
##
## limits:
##
## cpus: 2
##
## memory: 3.5G
##
## reservations:
##
## cpus: 1
##
## memory: 2.0G
volumes:
- .volumes/desktop:/root
domainname: desktop.softwareshinobi.digital
environment:
TZ: America/Bogota
USER_UID: 1000
USER_GID: 1000
USER: root
PASSWORD: passw0rd
HTTP_PASSWORD: passw0rd
VIRTUAL_HOST: desktop.softwareshinobi.digital
LETSENCRYPT_HOST: desktop.softwareshinobi.digital

BIN
.recycle/desktops/studio/files/Pictures/desktop.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 20 KiB

37
.recycle/desktops/studio/provision/netbeans.bash
View File

@@ -1,37 +0,0 @@
#!/bin/bash
set -e
set -x
##
## create the apps dir and populate with unzipped netbeans content
##
ls
mkdir /apps
cd /apps
##
ls
wget https://dlcdn.apache.org/netbeans/netbeans/21/netbeans-21-bin.zip
ls
mv netbeans-21-bin.zip netbeans.zip
ls
unzip netbeans.zip
ls
pwd
##
##
##

17
.recycle/desktops/studio/studio.bash
View File

@@ -1,17 +0,0 @@
#!/bin/bash
set -e
set -x
reset
clear
docker-compose build
docker-compose pull
docker-compose down
docker-compose up -d

14
.recycle/servers/private/Dockerfile
View File

@@ -1,14 +0,0 @@
FROM ubuntu
ARG DEBIAN_FRONTEND=noninteractive
COPY /provision/bashrc /tmp/.bashrc
COPY /provision/provision.bash provision.bash
RUN bash provision.bash
EXPOSE 22
CMD ["/usr/sbin/sshd","-D"]

192
.recycle/servers/private/provision/bashrc
View File

@@ -1,192 +0,0 @@
#!/bin/bash
##
## docker aliases
##
alias prune="docker system prune -a -f;docker volume prune -a -f"
##
## some more ls aliases
##
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'
##
## uncategorized
##
alias r="reset;clear;"
alias push="reset;clear;git add .;git commit -m 'automated terminal push';git push origin;"
alias pushe="reset;clear;git add .;git commit -m 'automated terminal push';git push origin;exit"
## video editing things
alias record="recordmydesktop on-the-fly-encoding --no-sound"
##
alias d="docker"
alias c="docker-compose"
alias compose='docker-compose'
## incoming
alias ll='ls -l'
alias r="reset;clear;"
##
alias cd..='cd ..'
alias ..='cd ..'
alias ...='cd ../../../'
alias ....='cd ../../../../'
alias .....='cd ../../../../'
alias .4='cd ../../../../'
alias .5='cd ../../../../..'
##
alias @memory-info='free -m -l -t'
alias @memory-top='ps auxf | sort -nr -k 4 | head -10'
alias @memory-top-10='ps auxf | sort -nr -k 4 | head -10'
alias @cpu-info='lscpu'
alias @cpu-top='ps auxf | sort -nr -k 3'
alias @cpu-top-10='ps auxf | sort -nr -k 3 | head -10'
alias @net-open-ports="sudo netstat -tlpn"
alias @net-external-ip="dig +short myip.opendns.com @resolver1.opendns.com"
alias @net-internal-interfaces="dig +short myip.opendns.com @resolver1.opendns.com"
## aliases for accessing cloud desktop
alias dustydepot="ssh dustydepot0@linux.softwareshinobi.digital -p 4444"
##
## everything below here is factory bullshit
##
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples
# If not running interactively, don't do anything
case $- in
*i*) ;;
*) return;;
esac
# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth
# append to the history file, don't overwrite it
shopt -s histappend
# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000
# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize
# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar
# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"
# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi
# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color|*-256color) color_prompt=yes;;
esac
# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes
if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi
if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt
# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
;;
*)
;;
esac
# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'
alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
fi
# colored GCC warnings and errors
#export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'
# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'
# Add an "alert" alias for long running commands. Use like so:
# sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'
# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.
if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi
# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
if [ -f /usr/share/bash-completion/bash_completion ]; then
. /usr/share/bash-completion/bash_completion
elif [ -f /etc/bash_completion ]; then
. /etc/bash_completion
fi
fi

144
.recycle/servers/private/provision/provision.bash
View File

@@ -1,144 +0,0 @@
#!/bin/bash
##
## This script installs stuff
## to set up a linux server
## suitable for newbies.
##
## Before you go, check read around my blog!
##
## https://softwareshinobi.digital
##
##
##
set -e;
set -x;
##
ls -l /tmp/.bashrc
cat /tmp/.bashrc;
source /tmp/.bashrc;
##
apt update;
##
apt install -y cmatrix;
apt install -y hollywood;
##
#!/bin/bash
##
## This script installs stuff
## to set up a linux server
## suitable for newbies.
##
## This linux server will be hosted under
## linux.softwareshinobi.digital
##
## Before you go, check read around my blog!
##
## https://www.softwareshinobi.digital
##
##
set -e;
set -x;
##
cat /etc/issue;
echo "Shinobi Academy OS 8" > /etc/issue;
cat /etc/issue;
##
apt-get update;
## install bashrc systemwide
cp /tmp/.bashrc /usr/local/bin/bashrc
##apt-get install docker-compose -y;
##
apt-get install -y vim nano;
apt-get install -y hollywood;
apt-get install -y cmatrix;
##
apt-get install -y openssh-server;
apt-get install -y sudo;
##
service ssh start;
##
## shinobi academy user config
##
useradd -rm -d /home/shinobi -s /bin/bash -u 444 shinobi;
cp /tmp/.bashrc /home/shinobi/.bashrc
## restrict permissions on home
chown -R nobody: /home/shinobi/
chmod -R 555 /home/shinobi/
chmod -R 555 /tmp/
##cat /home/shinobi/.bashrc
##apt install -y dos2unix
##dos2unix /home/shinobi/.bashrc
##usermod -a -G sudo shinobi
##usermod -a -G docker shinobi
echo 'shinobi:shinobi' | chpasswd
##
## wargame / thedustydepotdeputy
##
rm -rf /home/depotdeputy/;
mkdir /home/depotdeputy/;
##
useradd -rm -d /home/depotdeputy/depotdeputy0 -s /bin/bash -u 4010 depotdeputy0;
cp /tmp/.bashrc /home/depotdeputy/depotdeputy0/.bashrc
echo 'depotdeputy0:depotdeputy0' | chpasswd
##
echo "fin."

5
Dockerfile Normal file
View File

@@ -0,0 +1,5 @@
FROM nginx:latest
WORKDIR /usr/share/nginx/html
COPY --chown=www-data:www-data --chmod=755 . .

4
Jenkinsfile vendored
View File

@@ -51,4 +51,6 @@ pipeline {
} }
}} }
}

7
compose.bash
View File

@@ -2,6 +2,12 @@
## ##
reset;
clear;
##
set -e; set -e;
set -x; set -x;
@@ -11,4 +17,3 @@ set -x;
docker compose down --remove-orphans docker compose down --remove-orphans
docker compose up --build -d docker compose up --build -d

33
compose.yaml
View File

@@ -1,38 +1,17 @@
services: services:
linux.softwareshinobi.com-server: links.softwareshinobi.come:
container_name: linux.softwareshinobi.com-server
image: softwareshinobi/linux.softwareshinobi.com:server container_name: links.softwareshinobi.com
build: image: softwareshinobi/links.softwareshinobi.com
context: server build:
dockerfile: Dockerfile context: .
hostname: shinobilinux
domainname: linux.softwareshinobi.com
ports:
- "2222:22"
linux.softwareshinobi.com-landing:
container_name: linux.softwareshinobi.com-landing
image: softwareshinobi/linux.softwareshinobi.com:landing
build:
context: landing
dockerfile: Dockerfile dockerfile: Dockerfile
ports: ports:
- "2280:80" - 8000:80

BIN
cover.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 185 KiB

807
css/starfield.css Executable file
View File

@@ -0,0 +1,807 @@
@import url('https://fonts.googleapis.com/css?family=Karla:400,700&display=swap');
:root {
--bgColor: #223344;
--bgColor2: #090a0f;
--accentColor: #FFF;
--font: 'Karla', sans-serif;
--delay: .3s;
}
body {
margin: 0;
padding: 0;
min-height: 100vh;
font-family: var(--font);
background: radial-gradient(ellipse at bottom, var(--bgColor) 0%, var(--bgColor2) 100%);
/* background-image: url('https://bit.ly/3nFVqJh'); */
opacity: 0;
animation: 1s ease-out var(--delay) 1 transitionAnimation; /* duration/timing-function/delay/iterations/name */
animation-fill-mode: forwards;
background-repeat: no-repeat;
background-size: cover;
position: relative;
}
#profilePicture, #profilePicture img {
position: relative;
width: 96px;
height: 96px;
display: block;
margin: 40px auto 20px;
border-radius: 50%;
-webkit-tap-highlight-color: transparent;
}
#userName {
color: var(--accentColor);
font-size: 1rem;
font-weight: bold;
line-height: 1.25;
display: block;
font-family: var(--font);
text-align: center;
text-decoration: none;
}
.trash {
width: 25%;
}
#links {
max-width: 675px;
width: auto;
display: block;
margin: 27px auto;
}
.link {
position: relative;
background-color: transparent;
color: var(--accentColor);
border: solid var(--accentColor) 2px;
border-radius: 10px;
font-size: 1rem;
text-align: center;
display: block;
margin-left: 10px;
margin-right: 10px;
margin-bottom: 10px;
padding: 10px; /* 17px */
text-decoration: none;
/* transition: all .25s cubic-bezier(.08, .59, .29, .99); */
-webkit-tap-highlight-color: transparent;
}
@media (hover: hover) {
.link:hover {
background-color: var(--accentColor);
color: var(--bgColor);
}
}
.link:active {
background-color: var(--accentColor);
color: var(--bgColor);
}
#hashtag {
position: relative;
padding-bottom: 20px;
color: var(--accentColor);
font-size: 1rem;
display: block;
font-family: var(--font);
width: 100%;
text-align: center;
/* animation */
overflow: hidden;
background: linear-gradient(90deg, var(--bgColor), var(--accentColor), var(--bgColor));
background-repeat: no-repeat;
background-size: 80%;
animation: animate 3s linear var(--delay) infinite;
-webkit-background-clip: text;
background-clip: text;
-webkit-text-fill-color: rgba(255, 255, 255, 0);
}
/*-------------------------animations-----------------------*/
@keyframes transitionAnimation {
0% {
opacity: 0;
transform: translateY(-10px);
}
100% {
opacity: 1;
transform: translateY(0);
}
}
@keyframes animate {
0% {
background-position: -500%;
}
100% {
background-position: 500%;
}
}
@keyframes animStar {
from {
transform: translateY(0px);
}
to {
transform: translateY(-2000px);
}
}
/*-------------------------popup------------------------*/
/* credits: https://www.youtube.com/watch?v=lAS2glU0xlc */
.overlay {
display: flex;
align-items: center;
justify-content: center;
position: fixed;
top: 0;
bottom: 0;
left: 0;
right: 0;
background-color: rgba(0, 0, 0, 0.7);
z-index: 2;
visibility: hidden;
opacity: 0;
overflow: hidden;
transition: .5s ease-in-out;
}
.popup {
position: relative;
top: -43%;
/* right: -100vh; */
display: flex;
flex-direction: column;
align-items: center;
max-width: 400px;
/* max-height: 500px; */
width: auto;
height: auto;
margin: 56px;
background-color: var(--bgColor);
/* transform: rotate(32deg); */
transform: scale(0);
transition: .5s ease-in-out;
}
.popup-quote {
font-family : Baskerville, Georgia, serif;
font-style : italic;
position: flex;
color: var(--accentColor);
padding: 20px;
text-align: center;
font-size: 1rem;
}
.popup-photo {
display: flex;
width: 100%;
height: 100%;
}
.popup-photo img {
width: 100%;
height: 100%;
}
.overlay:target {
visibility: visible;
opacity: 1;
}
.overlay:target .popup {
transform: scale(1);
top: 0;
/* right: 0; */
/* transform: rotate(0); */
}
.popup-close {
position: absolute;
right: -1rem;
top: -1rem;
width: 3rem;
height: 3rem;
font-size: 1.7rem;
font-weight: 400;
border-radius: 100%;
background-color: var(--bgColor);
z-index: 4;
color: var(--accentColor);
line-height: 2.7rem;
text-align: center;
cursor: pointer;
text-decoration: none;
-webkit-tap-highlight-color: transparent;
}
@media (hover: hover) {
.popup-close:hover {
background-color: var(--accentColor);
color: var(--bgColor);
}
}
.popup-close:active {
background-color: var(--accentColor);
color: var(--bgColor);
}
/*-----------------------parallax-----------------------*/
/* credits: https://www.youtube.com/watch?v=aywzn9cf-_U */
#stars1 {
width: 1px;
height: 1px;
background: transparent;
animation: animStar 120s linear infinite;
box-shadow: 779px 1331px #fff, 324px 42px #fff, 303px 586px #fff,
1312px 276px #fff, 451px 625px #fff, 521px 1931px #fff, 1087px 1871px #fff,
36px 1546px #fff, 132px 934px #fff, 1698px 901px #fff, 1418px 664px #fff,
1448px 1157px #fff, 1084px 232px #fff, 347px 1776px #fff, 1722px 243px #fff,
1629px 835px #fff, 479px 969px #fff, 1231px 960px #fff, 586px 384px #fff,
164px 527px #fff, 8px 646px #fff, 1150px 1126px #fff, 665px 1357px #fff,
1556px 1982px #fff, 1260px 1961px #fff, 1675px 1741px #fff,
1843px 1514px #fff, 718px 1628px #fff, 242px 1343px #fff, 1497px 1880px #fff,
1364px 230px #fff, 1739px 1302px #fff, 636px 959px #fff, 304px 686px #fff,
614px 751px #fff, 1935px 816px #fff, 1428px 60px #fff, 355px 335px #fff,
1594px 158px #fff, 90px 60px #fff, 1553px 162px #fff, 1239px 1825px #fff,
1945px 587px #fff, 749px 1785px #fff, 1987px 1172px #fff, 1301px 1237px #fff,
1039px 342px #fff, 1585px 1481px #fff, 995px 1048px #fff, 524px 932px #fff,
214px 413px #fff, 1701px 1300px #fff, 1037px 1613px #fff, 1871px 996px #fff,
1360px 1635px #fff, 1110px 1313px #fff, 412px 1783px #fff, 1949px 177px #fff,
903px 1854px #fff, 700px 1936px #fff, 378px 125px #fff, 308px 834px #fff,
1118px 962px #fff, 1350px 1929px #fff, 781px 1811px #fff, 561px 137px #fff,
757px 1148px #fff, 1670px 1979px #fff, 343px 739px #fff, 945px 795px #fff,
576px 1903px #fff, 1078px 1436px #fff, 1583px 450px #fff, 1366px 474px #fff,
297px 1873px #fff, 192px 162px #fff, 1624px 1633px #fff, 59px 453px #fff,
82px 1872px #fff, 1933px 498px #fff, 1966px 1974px #fff, 1975px 1688px #fff,
779px 314px #fff, 1858px 1543px #fff, 73px 1507px #fff, 1693px 975px #fff,
1683px 108px #fff, 1768px 1654px #fff, 654px 14px #fff, 494px 171px #fff,
1689px 1895px #fff, 1660px 263px #fff, 1031px 903px #fff, 1203px 1393px #fff,
1333px 1421px #fff, 1113px 41px #fff, 1206px 1645px #fff, 1325px 1635px #fff,
142px 388px #fff, 572px 215px #fff, 1535px 296px #fff, 1419px 407px #fff,
1379px 1003px #fff, 329px 469px #fff, 1791px 1652px #fff, 935px 1802px #fff,
1330px 1820px #fff, 421px 1933px #fff, 828px 365px #fff, 275px 316px #fff,
707px 960px #fff, 1605px 1554px #fff, 625px 58px #fff, 717px 1697px #fff,
1669px 246px #fff, 1925px 322px #fff, 1154px 1803px #fff, 1929px 295px #fff,
1248px 240px #fff, 1045px 1755px #fff, 166px 942px #fff, 1888px 1773px #fff,
678px 1963px #fff, 1370px 569px #fff, 1974px 1400px #fff, 1786px 460px #fff,
51px 307px #fff, 784px 1400px #fff, 730px 1258px #fff, 1712px 393px #fff,
416px 170px #fff, 1797px 1932px #fff, 572px 219px #fff, 1557px 1856px #fff,
218px 8px #fff, 348px 1334px #fff, 469px 413px #fff, 385px 1738px #fff,
1357px 1818px #fff, 240px 942px #fff, 248px 1847px #fff, 1535px 806px #fff,
236px 1514px #fff, 1429px 1556px #fff, 73px 1633px #fff, 1398px 1121px #fff,
671px 1301px #fff, 1404px 1663px #fff, 740px 1018px #fff, 1600px 377px #fff,
785px 514px #fff, 112px 1084px #fff, 1915px 1887px #fff, 1463px 1848px #fff,
687px 1115px #fff, 1268px 1768px #fff, 1729px 1425px #fff,
1284px 1022px #fff, 801px 974px #fff, 1975px 1317px #fff, 1354px 834px #fff,
1446px 1484px #fff, 1283px 1786px #fff, 11px 523px #fff, 1842px 236px #fff,
1355px 654px #fff, 429px 7px #fff, 1033px 1128px #fff, 157px 297px #fff,
545px 635px #fff, 52px 1080px #fff, 827px 1520px #fff, 1121px 490px #fff,
9px 309px #fff, 1744px 1586px #fff, 1014px 417px #fff, 1534px 524px #fff,
958px 552px #fff, 1403px 1496px #fff, 387px 703px #fff, 1522px 548px #fff,
1355px 282px #fff, 1532px 601px #fff, 1838px 790px #fff, 290px 259px #fff,
295px 598px #fff, 1601px 539px #fff, 1561px 1272px #fff, 34px 1922px #fff,
1024px 543px #fff, 467px 369px #fff, 722px 333px #fff, 1976px 1255px #fff,
766px 983px #fff, 1582px 1285px #fff, 12px 512px #fff, 617px 1410px #fff,
682px 577px #fff, 1334px 1438px #fff, 439px 327px #fff, 1617px 1661px #fff,
673px 129px #fff, 794px 941px #fff, 1386px 1902px #fff, 37px 1353px #fff,
1467px 1353px #fff, 416px 18px #fff, 187px 344px #fff, 200px 1898px #fff,
1491px 1619px #fff, 811px 347px #fff, 924px 1827px #fff, 945px 217px #fff,
1735px 1228px #fff, 379px 1890px #fff, 79px 761px #fff, 825px 1837px #fff,
1980px 1558px #fff, 1308px 1573px #fff, 1488px 1726px #fff,
382px 1208px #fff, 522px 595px #fff, 1277px 1898px #fff, 354px 552px #fff,
161px 1784px #fff, 614px 251px #fff, 526px 1576px #fff, 17px 212px #fff,
179px 996px #fff, 467px 1208px #fff, 1944px 1838px #fff, 1140px 1093px #fff,
858px 1007px #fff, 200px 1064px #fff, 423px 1964px #fff, 1945px 439px #fff,
1377px 689px #fff, 1120px 1437px #fff, 1876px 668px #fff, 907px 1324px #fff,
343px 1976px #fff, 1816px 1501px #fff, 1849px 177px #fff, 647px 91px #fff,
1984px 1012px #fff, 1336px 1300px #fff, 128px 648px #fff, 305px 1060px #fff,
1324px 826px #fff, 1263px 1314px #fff, 1801px 629px #fff, 1614px 1555px #fff,
1634px 90px #fff, 1603px 452px #fff, 891px 1984px #fff, 1556px 1906px #fff,
121px 68px #fff, 1676px 1714px #fff, 516px 936px #fff, 1947px 1492px #fff,
1455px 1519px #fff, 45px 602px #fff, 205px 1039px #fff, 793px 172px #fff,
1562px 1739px #fff, 1056px 110px #fff, 1512px 379px #fff, 1795px 1621px #fff,
1848px 607px #fff, 262px 1719px #fff, 477px 991px #fff, 483px 883px #fff,
1239px 1197px #fff, 1496px 647px #fff, 1649px 25px #fff, 1491px 1946px #fff,
119px 996px #fff, 179px 1472px #fff, 1341px 808px #fff, 1565px 1700px #fff,
407px 1544px #fff, 1754px 357px #fff, 1288px 981px #fff, 902px 1997px #fff,
1755px 1668px #fff, 186px 877px #fff, 1202px 1882px #fff, 461px 1213px #fff,
1400px 748px #fff, 1969px 1899px #fff, 809px 522px #fff, 514px 1219px #fff,
374px 275px #fff, 938px 1973px #fff, 357px 552px #fff, 144px 1722px #fff,
1572px 912px #fff, 402px 1858px #fff, 1544px 1195px #fff, 667px 1257px #fff,
727px 1496px #fff, 993px 232px #fff, 1772px 313px #fff, 1040px 1590px #fff,
1204px 1973px #fff, 1268px 79px #fff, 1555px 1048px #fff, 986px 1707px #fff,
978px 1710px #fff, 713px 360px #fff, 407px 863px #fff, 461px 736px #fff,
284px 1608px #fff, 103px 430px #fff, 1283px 1319px #fff, 977px 1186px #fff,
1966px 1516px #fff, 1287px 1129px #fff, 70px 1098px #fff, 1189px 889px #fff,
1126px 1734px #fff, 309px 1292px #fff, 879px 764px #fff, 65px 473px #fff,
1003px 1959px #fff, 658px 791px #fff, 402px 1576px #fff, 35px 622px #fff,
529px 1589px #fff, 164px 666px #fff, 1876px 1290px #fff, 1541px 526px #fff,
270px 1297px #fff, 440px 865px #fff, 1500px 802px #fff, 182px 1754px #fff,
1264px 892px #fff, 272px 1249px #fff, 1289px 1535px #fff, 190px 1646px #fff,
955px 242px #fff, 1456px 1597px #fff, 1727px 1983px #fff, 635px 801px #fff,
226px 455px #fff, 1396px 1710px #fff, 849px 1863px #fff, 237px 1264px #fff,
839px 140px #fff, 1122px 735px #fff, 1280px 15px #fff, 1318px 242px #fff,
1819px 1148px #fff, 333px 1392px #fff, 1949px 553px #fff, 1878px 1332px #fff,
467px 548px #fff, 1812px 1082px #fff, 1067px 193px #fff, 243px 156px #fff,
483px 1616px #fff, 1714px 933px #fff, 759px 1800px #fff, 1822px 995px #fff,
1877px 572px #fff, 581px 1084px #fff, 107px 732px #fff, 642px 1837px #fff,
166px 1493px #fff, 1555px 198px #fff, 819px 307px #fff, 947px 345px #fff,
827px 224px #fff, 927px 1394px #fff, 540px 467px #fff, 1093px 405px #fff,
1140px 927px #fff, 130px 529px #fff, 33px 1980px #fff, 1147px 1663px #fff,
1616px 1436px #fff, 528px 710px #fff, 798px 1100px #fff, 505px 1480px #fff,
899px 641px #fff, 1909px 1949px #fff, 1311px 964px #fff, 979px 1301px #fff,
1393px 969px #fff, 1793px 1886px #fff, 292px 357px #fff, 1196px 1718px #fff,
1290px 1994px #fff, 537px 1973px #fff, 1181px 1674px #fff,
1740px 1566px #fff, 1307px 265px #fff, 922px 522px #fff, 1892px 472px #fff,
384px 1746px #fff, 392px 1098px #fff, 647px 548px #fff, 390px 1498px #fff,
1246px 138px #fff, 730px 876px #fff, 192px 1472px #fff, 1790px 1789px #fff,
928px 311px #fff, 1253px 1647px #fff, 747px 1921px #fff, 1561px 1025px #fff,
1533px 1292px #fff, 1985px 195px #fff, 728px 729px #fff, 1712px 1936px #fff,
512px 1717px #fff, 1528px 483px #fff, 313px 1642px #fff, 281px 1849px #fff,
1212px 799px #fff, 435px 1191px #fff, 1422px 611px #fff, 1718px 1964px #fff,
411px 944px #fff, 210px 636px #fff, 1502px 1295px #fff, 1434px 349px #fff,
769px 60px #fff, 747px 1053px #fff, 789px 504px #fff, 1436px 1264px #fff,
1893px 1225px #fff, 1394px 1788px #fff, 1108px 1317px #fff,
1673px 1395px #fff, 854px 1010px #fff, 1705px 80px #fff, 1858px 148px #fff,
1729px 344px #fff, 1388px 664px #fff, 895px 406px #fff, 1479px 157px #fff,
1441px 1157px #fff, 552px 1900px #fff, 516px 364px #fff, 1647px 189px #fff,
1427px 1071px #fff, 785px 729px #fff, 1080px 1710px #fff, 504px 204px #fff,
1177px 1622px #fff, 657px 34px #fff, 1296px 1099px #fff, 248px 180px #fff,
1212px 1568px #fff, 667px 1562px #fff, 695px 841px #fff, 1608px 1247px #fff,
751px 882px #fff, 87px 167px #fff, 607px 1368px #fff, 1363px 1203px #fff,
1836px 317px #fff, 1668px 1703px #fff, 830px 1154px #fff, 1721px 1398px #fff,
1601px 1280px #fff, 976px 874px #fff, 1743px 254px #fff, 1020px 1815px #fff,
1670px 1766px #fff, 1890px 735px #fff, 1379px 136px #fff, 1864px 695px #fff,
206px 965px #fff, 1404px 1932px #fff, 1923px 1360px #fff, 247px 682px #fff,
519px 1708px #fff, 645px 750px #fff, 1164px 1204px #fff, 834px 323px #fff,
172px 1350px #fff, 213px 972px #fff, 1837px 190px #fff, 285px 1806px #fff,
1047px 1299px #fff, 1548px 825px #fff, 1730px 324px #fff, 1346px 1909px #fff,
772px 270px #fff, 345px 1190px #fff, 478px 1433px #fff, 1479px 25px #fff,
1994px 1830px #fff, 1744px 732px #fff, 20px 1635px #fff, 690px 1795px #fff,
1594px 569px #fff, 579px 245px #fff, 1398px 733px #fff, 408px 1352px #fff,
1774px 120px #fff, 1152px 1370px #fff, 1698px 1810px #fff, 710px 1450px #fff,
665px 286px #fff, 493px 1720px #fff, 786px 5px #fff, 637px 1140px #fff,
764px 324px #fff, 927px 310px #fff, 938px 1424px #fff, 1884px 744px #fff,
913px 462px #fff, 1831px 1936px #fff, 1527px 249px #fff, 36px 1381px #fff,
1597px 581px #fff, 1530px 355px #fff, 949px 459px #fff, 799px 828px #fff,
242px 1471px #fff, 654px 797px #fff, 796px 594px #fff, 1365px 678px #fff,
752px 23px #fff, 1630px 541px #fff, 982px 72px #fff, 1733px 1831px #fff,
21px 412px #fff, 775px 998px #fff, 335px 1945px #fff, 264px 583px #fff,
158px 1311px #fff, 528px 164px #fff, 1978px 574px #fff, 717px 1203px #fff,
734px 1591px #fff, 1555px 820px #fff, 16px 1943px #fff, 1625px 1177px #fff,
1236px 690px #fff, 1585px 1590px #fff, 1737px 1728px #fff, 721px 698px #fff,
1804px 1186px #fff, 166px 980px #fff, 1850px 230px #fff, 330px 1712px #fff,
95px 797px #fff, 1948px 1078px #fff, 469px 939px #fff, 1269px 1899px #fff,
955px 1220px #fff, 1137px 1075px #fff, 312px 1293px #fff, 986px 1762px #fff,
1103px 1238px #fff, 428px 1993px #fff, 355px 570px #fff, 977px 1836px #fff,
1395px 1092px #fff, 276px 913px #fff, 1743px 656px #fff, 773px 502px #fff,
1686px 1322px #fff, 1516px 1945px #fff, 1334px 501px #fff, 266px 156px #fff,
455px 655px #fff, 798px 72px #fff, 1059px 1259px #fff, 1402px 1687px #fff,
236px 1329px #fff, 1455px 786px #fff, 146px 1228px #fff, 1851px 823px #fff,
1062px 100px #fff, 1220px 953px #fff, 20px 1826px #fff, 36px 1063px #fff,
1525px 338px #fff, 790px 1521px #fff, 741px 1099px #fff, 288px 1489px #fff,
700px 1060px #fff, 390px 1071px #fff, 411px 1036px #fff, 1853px 1072px #fff,
1446px 1085px #fff, 1164px 874px #fff, 924px 925px #fff, 291px 271px #fff,
1257px 1964px #fff, 1580px 1352px #fff, 1507px 1216px #fff, 211px 956px #fff,
985px 1195px #fff, 975px 1640px #fff, 518px 101px #fff, 663px 1395px #fff,
914px 532px #fff, 145px 1320px #fff, 69px 1397px #fff, 982px 523px #fff,
257px 725px #fff, 1599px 831px #fff, 1636px 1513px #fff, 1250px 1158px #fff,
1132px 604px #fff, 183px 102px #fff, 1057px 318px #fff, 1247px 1835px #fff,
1983px 1110px #fff, 1077px 1455px #fff, 921px 1770px #fff, 806px 1350px #fff,
1938px 1992px #fff, 855px 1260px #fff, 902px 1345px #fff, 658px 1908px #fff,
1845px 679px #fff, 712px 1482px #fff, 595px 950px #fff, 1784px 1992px #fff,
1847px 1785px #fff, 691px 1004px #fff, 175px 1179px #fff, 1666px 1911px #fff,
41px 61px #fff, 971px 1080px #fff, 1830px 1450px #fff, 1351px 1518px #fff,
1257px 99px #fff, 1395px 1498px #fff, 1117px 252px #fff, 1779px 597px #fff,
1346px 729px #fff, 1108px 1144px #fff, 402px 691px #fff, 72px 496px #fff,
1673px 1604px #fff, 1497px 974px #fff, 1865px 1664px #fff, 88px 806px #fff,
918px 77px #fff, 244px 1118px #fff, 256px 1820px #fff, 1851px 1840px #fff,
605px 1851px #fff, 634px 383px #fff, 865px 37px #fff, 943px 1024px #fff,
1951px 177px #fff, 1097px 523px #fff, 985px 1700px #fff, 1243px 122px #fff,
768px 1070px #fff, 468px 194px #fff, 320px 1867px #fff, 1850px 185px #fff,
380px 1616px #fff, 468px 1294px #fff, 1122px 1743px #fff, 884px 299px #fff,
1300px 1917px #fff, 1860px 396px #fff, 1270px 990px #fff, 529px 733px #fff,
1975px 1347px #fff, 1885px 685px #fff, 226px 506px #fff, 651px 878px #fff,
1323px 680px #fff, 1284px 680px #fff, 238px 1967px #fff, 911px 174px #fff,
1111px 521px #fff, 1150px 85px #fff, 794px 502px #fff, 484px 1856px #fff,
1809px 368px #fff, 112px 953px #fff, 590px 1009px #fff, 1655px 311px #fff,
100px 1026px #fff, 1803px 352px #fff, 865px 306px #fff, 1077px 1019px #fff,
1335px 872px #fff, 1647px 1298px #fff, 1233px 1387px #fff, 698px 1036px #fff,
659px 1860px #fff, 388px 1412px #fff, 1212px 458px #fff, 755px 1468px #fff,
696px 1654px #fff, 1144px 60px #fff;
}
#stars1:after {
content: '';
position: absolute;
top: auto;
width: 1px;
height: 1px;
background: transparent;
box-shadow: 779px 1331px #fff, 324px 42px #fff, 303px 586px #fff,
1312px 276px #fff, 451px 625px #fff, 521px 1931px #fff, 1087px 1871px #fff,
36px 1546px #fff, 132px 934px #fff, 1698px 901px #fff, 1418px 664px #fff,
1448px 1157px #fff, 1084px 232px #fff, 347px 1776px #fff, 1722px 243px #fff,
1629px 835px #fff, 479px 969px #fff, 1231px 960px #fff, 586px 384px #fff,
164px 527px #fff, 8px 646px #fff, 1150px 1126px #fff, 665px 1357px #fff,
1556px 1982px #fff, 1260px 1961px #fff, 1675px 1741px #fff,
1843px 1514px #fff, 718px 1628px #fff, 242px 1343px #fff, 1497px 1880px #fff,
1364px 230px #fff, 1739px 1302px #fff, 636px 959px #fff, 304px 686px #fff,
614px 751px #fff, 1935px 816px #fff, 1428px 60px #fff, 355px 335px #fff,
1594px 158px #fff, 90px 60px #fff, 1553px 162px #fff, 1239px 1825px #fff,
1945px 587px #fff, 749px 1785px #fff, 1987px 1172px #fff, 1301px 1237px #fff,
1039px 342px #fff, 1585px 1481px #fff, 995px 1048px #fff, 524px 932px #fff,
214px 413px #fff, 1701px 1300px #fff, 1037px 1613px #fff, 1871px 996px #fff,
1360px 1635px #fff, 1110px 1313px #fff, 412px 1783px #fff, 1949px 177px #fff,
903px 1854px #fff, 700px 1936px #fff, 378px 125px #fff, 308px 834px #fff,
1118px 962px #fff, 1350px 1929px #fff, 781px 1811px #fff, 561px 137px #fff,
757px 1148px #fff, 1670px 1979px #fff, 343px 739px #fff, 945px 795px #fff,
576px 1903px #fff, 1078px 1436px #fff, 1583px 450px #fff, 1366px 474px #fff,
297px 1873px #fff, 192px 162px #fff, 1624px 1633px #fff, 59px 453px #fff,
82px 1872px #fff, 1933px 498px #fff, 1966px 1974px #fff, 1975px 1688px #fff,
779px 314px #fff, 1858px 1543px #fff, 73px 1507px #fff, 1693px 975px #fff,
1683px 108px #fff, 1768px 1654px #fff, 654px 14px #fff, 494px 171px #fff,
1689px 1895px #fff, 1660px 263px #fff, 1031px 903px #fff, 1203px 1393px #fff,
1333px 1421px #fff, 1113px 41px #fff, 1206px 1645px #fff, 1325px 1635px #fff,
142px 388px #fff, 572px 215px #fff, 1535px 296px #fff, 1419px 407px #fff,
1379px 1003px #fff, 329px 469px #fff, 1791px 1652px #fff, 935px 1802px #fff,
1330px 1820px #fff, 421px 1933px #fff, 828px 365px #fff, 275px 316px #fff,
707px 960px #fff, 1605px 1554px #fff, 625px 58px #fff, 717px 1697px #fff,
1669px 246px #fff, 1925px 322px #fff, 1154px 1803px #fff, 1929px 295px #fff,
1248px 240px #fff, 1045px 1755px #fff, 166px 942px #fff, 1888px 1773px #fff,
678px 1963px #fff, 1370px 569px #fff, 1974px 1400px #fff, 1786px 460px #fff,
51px 307px #fff, 784px 1400px #fff, 730px 1258px #fff, 1712px 393px #fff,
416px 170px #fff, 1797px 1932px #fff, 572px 219px #fff, 1557px 1856px #fff,
218px 8px #fff, 348px 1334px #fff, 469px 413px #fff, 385px 1738px #fff,
1357px 1818px #fff, 240px 942px #fff, 248px 1847px #fff, 1535px 806px #fff,
236px 1514px #fff, 1429px 1556px #fff, 73px 1633px #fff, 1398px 1121px #fff,
671px 1301px #fff, 1404px 1663px #fff, 740px 1018px #fff, 1600px 377px #fff,
785px 514px #fff, 112px 1084px #fff, 1915px 1887px #fff, 1463px 1848px #fff,
687px 1115px #fff, 1268px 1768px #fff, 1729px 1425px #fff,
1284px 1022px #fff, 801px 974px #fff, 1975px 1317px #fff, 1354px 834px #fff,
1446px 1484px #fff, 1283px 1786px #fff, 11px 523px #fff, 1842px 236px #fff,
1355px 654px #fff, 429px 7px #fff, 1033px 1128px #fff, 157px 297px #fff,
545px 635px #fff, 52px 1080px #fff, 827px 1520px #fff, 1121px 490px #fff,
9px 309px #fff, 1744px 1586px #fff, 1014px 417px #fff, 1534px 524px #fff,
958px 552px #fff, 1403px 1496px #fff, 387px 703px #fff, 1522px 548px #fff,
1355px 282px #fff, 1532px 601px #fff, 1838px 790px #fff, 290px 259px #fff,
295px 598px #fff, 1601px 539px #fff, 1561px 1272px #fff, 34px 1922px #fff,
1024px 543px #fff, 467px 369px #fff, 722px 333px #fff, 1976px 1255px #fff,
766px 983px #fff, 1582px 1285px #fff, 12px 512px #fff, 617px 1410px #fff,
682px 577px #fff, 1334px 1438px #fff, 439px 327px #fff, 1617px 1661px #fff,
673px 129px #fff, 794px 941px #fff, 1386px 1902px #fff, 37px 1353px #fff,
1467px 1353px #fff, 416px 18px #fff, 187px 344px #fff, 200px 1898px #fff,
1491px 1619px #fff, 811px 347px #fff, 924px 1827px #fff, 945px 217px #fff,
1735px 1228px #fff, 379px 1890px #fff, 79px 761px #fff, 825px 1837px #fff,
1980px 1558px #fff, 1308px 1573px #fff, 1488px 1726px #fff,
382px 1208px #fff, 522px 595px #fff, 1277px 1898px #fff, 354px 552px #fff,
161px 1784px #fff, 614px 251px #fff, 526px 1576px #fff, 17px 212px #fff,
179px 996px #fff, 467px 1208px #fff, 1944px 1838px #fff, 1140px 1093px #fff,
858px 1007px #fff, 200px 1064px #fff, 423px 1964px #fff, 1945px 439px #fff,
1377px 689px #fff, 1120px 1437px #fff, 1876px 668px #fff, 907px 1324px #fff,
343px 1976px #fff, 1816px 1501px #fff, 1849px 177px #fff, 647px 91px #fff,
1984px 1012px #fff, 1336px 1300px #fff, 128px 648px #fff, 305px 1060px #fff,
1324px 826px #fff, 1263px 1314px #fff, 1801px 629px #fff, 1614px 1555px #fff,
1634px 90px #fff, 1603px 452px #fff, 891px 1984px #fff, 1556px 1906px #fff,
121px 68px #fff, 1676px 1714px #fff, 516px 936px #fff, 1947px 1492px #fff,
1455px 1519px #fff, 45px 602px #fff, 205px 1039px #fff, 793px 172px #fff,
1562px 1739px #fff, 1056px 110px #fff, 1512px 379px #fff, 1795px 1621px #fff,
1848px 607px #fff, 262px 1719px #fff, 477px 991px #fff, 483px 883px #fff,
1239px 1197px #fff, 1496px 647px #fff, 1649px 25px #fff, 1491px 1946px #fff,
119px 996px #fff, 179px 1472px #fff, 1341px 808px #fff, 1565px 1700px #fff,
407px 1544px #fff, 1754px 357px #fff, 1288px 981px #fff, 902px 1997px #fff,
1755px 1668px #fff, 186px 877px #fff, 1202px 1882px #fff, 461px 1213px #fff,
1400px 748px #fff, 1969px 1899px #fff, 809px 522px #fff, 514px 1219px #fff,
374px 275px #fff, 938px 1973px #fff, 357px 552px #fff, 144px 1722px #fff,
1572px 912px #fff, 402px 1858px #fff, 1544px 1195px #fff, 667px 1257px #fff,
727px 1496px #fff, 993px 232px #fff, 1772px 313px #fff, 1040px 1590px #fff,
1204px 1973px #fff, 1268px 79px #fff, 1555px 1048px #fff, 986px 1707px #fff,
978px 1710px #fff, 713px 360px #fff, 407px 863px #fff, 461px 736px #fff,
284px 1608px #fff, 103px 430px #fff, 1283px 1319px #fff, 977px 1186px #fff,
1966px 1516px #fff, 1287px 1129px #fff, 70px 1098px #fff, 1189px 889px #fff,
1126px 1734px #fff, 309px 1292px #fff, 879px 764px #fff, 65px 473px #fff,
1003px 1959px #fff, 658px 791px #fff, 402px 1576px #fff, 35px 622px #fff,
529px 1589px #fff, 164px 666px #fff, 1876px 1290px #fff, 1541px 526px #fff,
270px 1297px #fff, 440px 865px #fff, 1500px 802px #fff, 182px 1754px #fff,
1264px 892px #fff, 272px 1249px #fff, 1289px 1535px #fff, 190px 1646px #fff,
955px 242px #fff, 1456px 1597px #fff, 1727px 1983px #fff, 635px 801px #fff,
226px 455px #fff, 1396px 1710px #fff, 849px 1863px #fff, 237px 1264px #fff,
839px 140px #fff, 1122px 735px #fff, 1280px 15px #fff, 1318px 242px #fff,
1819px 1148px #fff, 333px 1392px #fff, 1949px 553px #fff, 1878px 1332px #fff,
467px 548px #fff, 1812px 1082px #fff, 1067px 193px #fff, 243px 156px #fff,
483px 1616px #fff, 1714px 933px #fff, 759px 1800px #fff, 1822px 995px #fff,
1877px 572px #fff, 581px 1084px #fff, 107px 732px #fff, 642px 1837px #fff,
166px 1493px #fff, 1555px 198px #fff, 819px 307px #fff, 947px 345px #fff,
827px 224px #fff, 927px 1394px #fff, 540px 467px #fff, 1093px 405px #fff,
1140px 927px #fff, 130px 529px #fff, 33px 1980px #fff, 1147px 1663px #fff,
1616px 1436px #fff, 528px 710px #fff, 798px 1100px #fff, 505px 1480px #fff,
899px 641px #fff, 1909px 1949px #fff, 1311px 964px #fff, 979px 1301px #fff,
1393px 969px #fff, 1793px 1886px #fff, 292px 357px #fff, 1196px 1718px #fff,
1290px 1994px #fff, 537px 1973px #fff, 1181px 1674px #fff,
1740px 1566px #fff, 1307px 265px #fff, 922px 522px #fff, 1892px 472px #fff,
384px 1746px #fff, 392px 1098px #fff, 647px 548px #fff, 390px 1498px #fff,
1246px 138px #fff, 730px 876px #fff, 192px 1472px #fff, 1790px 1789px #fff,
928px 311px #fff, 1253px 1647px #fff, 747px 1921px #fff, 1561px 1025px #fff,
1533px 1292px #fff, 1985px 195px #fff, 728px 729px #fff, 1712px 1936px #fff,
512px 1717px #fff, 1528px 483px #fff, 313px 1642px #fff, 281px 1849px #fff,
1212px 799px #fff, 435px 1191px #fff, 1422px 611px #fff, 1718px 1964px #fff,
411px 944px #fff, 210px 636px #fff, 1502px 1295px #fff, 1434px 349px #fff,
769px 60px #fff, 747px 1053px #fff, 789px 504px #fff, 1436px 1264px #fff,
1893px 1225px #fff, 1394px 1788px #fff, 1108px 1317px #fff,
1673px 1395px #fff, 854px 1010px #fff, 1705px 80px #fff, 1858px 148px #fff,
1729px 344px #fff, 1388px 664px #fff, 895px 406px #fff, 1479px 157px #fff,
1441px 1157px #fff, 552px 1900px #fff, 516px 364px #fff, 1647px 189px #fff,
1427px 1071px #fff, 785px 729px #fff, 1080px 1710px #fff, 504px 204px #fff,
1177px 1622px #fff, 657px 34px #fff, 1296px 1099px #fff, 248px 180px #fff,
1212px 1568px #fff, 667px 1562px #fff, 695px 841px #fff, 1608px 1247px #fff,
751px 882px #fff, 87px 167px #fff, 607px 1368px #fff, 1363px 1203px #fff,
1836px 317px #fff, 1668px 1703px #fff, 830px 1154px #fff, 1721px 1398px #fff,
1601px 1280px #fff, 976px 874px #fff, 1743px 254px #fff, 1020px 1815px #fff,
1670px 1766px #fff, 1890px 735px #fff, 1379px 136px #fff, 1864px 695px #fff,
206px 965px #fff, 1404px 1932px #fff, 1923px 1360px #fff, 247px 682px #fff,
519px 1708px #fff, 645px 750px #fff, 1164px 1204px #fff, 834px 323px #fff,
172px 1350px #fff, 213px 972px #fff, 1837px 190px #fff, 285px 1806px #fff,
1047px 1299px #fff, 1548px 825px #fff, 1730px 324px #fff, 1346px 1909px #fff,
772px 270px #fff, 345px 1190px #fff, 478px 1433px #fff, 1479px 25px #fff,
1994px 1830px #fff, 1744px 732px #fff, 20px 1635px #fff, 690px 1795px #fff,
1594px 569px #fff, 579px 245px #fff, 1398px 733px #fff, 408px 1352px #fff,
1774px 120px #fff, 1152px 1370px #fff, 1698px 1810px #fff, 710px 1450px #fff,
665px 286px #fff, 493px 1720px #fff, 786px 5px #fff, 637px 1140px #fff,
764px 324px #fff, 927px 310px #fff, 938px 1424px #fff, 1884px 744px #fff,
913px 462px #fff, 1831px 1936px #fff, 1527px 249px #fff, 36px 1381px #fff,
1597px 581px #fff, 1530px 355px #fff, 949px 459px #fff, 799px 828px #fff,
242px 1471px #fff, 654px 797px #fff, 796px 594px #fff, 1365px 678px #fff,
752px 23px #fff, 1630px 541px #fff, 982px 72px #fff, 1733px 1831px #fff,
21px 412px #fff, 775px 998px #fff, 335px 1945px #fff, 264px 583px #fff,
158px 1311px #fff, 528px 164px #fff, 1978px 574px #fff, 717px 1203px #fff,
734px 1591px #fff, 1555px 820px #fff, 16px 1943px #fff, 1625px 1177px #fff,
1236px 690px #fff, 1585px 1590px #fff, 1737px 1728px #fff, 721px 698px #fff,
1804px 1186px #fff, 166px 980px #fff, 1850px 230px #fff, 330px 1712px #fff,
95px 797px #fff, 1948px 1078px #fff, 469px 939px #fff, 1269px 1899px #fff,
955px 1220px #fff, 1137px 1075px #fff, 312px 1293px #fff, 986px 1762px #fff,
1103px 1238px #fff, 428px 1993px #fff, 355px 570px #fff, 977px 1836px #fff,
1395px 1092px #fff, 276px 913px #fff, 1743px 656px #fff, 773px 502px #fff,
1686px 1322px #fff, 1516px 1945px #fff, 1334px 501px #fff, 266px 156px #fff,
455px 655px #fff, 798px 72px #fff, 1059px 1259px #fff, 1402px 1687px #fff,
236px 1329px #fff, 1455px 786px #fff, 146px 1228px #fff, 1851px 823px #fff,
1062px 100px #fff, 1220px 953px #fff, 20px 1826px #fff, 36px 1063px #fff,
1525px 338px #fff, 790px 1521px #fff, 741px 1099px #fff, 288px 1489px #fff,
700px 1060px #fff, 390px 1071px #fff, 411px 1036px #fff, 1853px 1072px #fff,
1446px 1085px #fff, 1164px 874px #fff, 924px 925px #fff, 291px 271px #fff,
1257px 1964px #fff, 1580px 1352px #fff, 1507px 1216px #fff, 211px 956px #fff,
985px 1195px #fff, 975px 1640px #fff, 518px 101px #fff, 663px 1395px #fff,
914px 532px #fff, 145px 1320px #fff, 69px 1397px #fff, 982px 523px #fff,
257px 725px #fff, 1599px 831px #fff, 1636px 1513px #fff, 1250px 1158px #fff,
1132px 604px #fff, 183px 102px #fff, 1057px 318px #fff, 1247px 1835px #fff,
1983px 1110px #fff, 1077px 1455px #fff, 921px 1770px #fff, 806px 1350px #fff,
1938px 1992px #fff, 855px 1260px #fff, 902px 1345px #fff, 658px 1908px #fff,
1845px 679px #fff, 712px 1482px #fff, 595px 950px #fff, 1784px 1992px #fff,
1847px 1785px #fff, 691px 1004px #fff, 175px 1179px #fff, 1666px 1911px #fff,
41px 61px #fff, 971px 1080px #fff, 1830px 1450px #fff, 1351px 1518px #fff,
1257px 99px #fff, 1395px 1498px #fff, 1117px 252px #fff, 1779px 597px #fff,
1346px 729px #fff, 1108px 1144px #fff, 402px 691px #fff, 72px 496px #fff,
1673px 1604px #fff, 1497px 974px #fff, 1865px 1664px #fff, 88px 806px #fff,
918px 77px #fff, 244px 1118px #fff, 256px 1820px #fff, 1851px 1840px #fff,
605px 1851px #fff, 634px 383px #fff, 865px 37px #fff, 943px 1024px #fff,
1951px 177px #fff, 1097px 523px #fff, 985px 1700px #fff, 1243px 122px #fff,
768px 1070px #fff, 468px 194px #fff, 320px 1867px #fff, 1850px 185px #fff,
380px 1616px #fff, 468px 1294px #fff, 1122px 1743px #fff, 884px 299px #fff,
1300px 1917px #fff, 1860px 396px #fff, 1270px 990px #fff, 529px 733px #fff,
1975px 1347px #fff, 1885px 685px #fff, 226px 506px #fff, 651px 878px #fff,
1323px 680px #fff, 1284px 680px #fff, 238px 1967px #fff, 911px 174px #fff,
1111px 521px #fff, 1150px 85px #fff, 794px 502px #fff, 484px 1856px #fff,
1809px 368px #fff, 112px 953px #fff, 590px 1009px #fff, 1655px 311px #fff,
100px 1026px #fff, 1803px 352px #fff, 865px 306px #fff, 1077px 1019px #fff,
1335px 872px #fff, 1647px 1298px #fff, 1233px 1387px #fff, 698px 1036px #fff,
659px 1860px #fff, 388px 1412px #fff, 1212px 458px #fff, 755px 1468px #fff,
696px 1654px #fff, 1144px 60px #fff;
}
#stars2 {
width: 2px;
height: 2px;
background: transparent;
animation: animStar 180s linear infinite;
box-shadow: 1448px 320px #fff, 1775px 1663px #fff, 332px 1364px #fff,
878px 340px #fff, 569px 1832px #fff, 1422px 1684px #fff, 1946px 1907px #fff,
121px 979px #fff, 1044px 1069px #fff, 463px 381px #fff, 423px 112px #fff,
523px 1179px #fff, 779px 654px #fff, 1398px 694px #fff, 1085px 1464px #fff,
1599px 1869px #fff, 801px 1882px #fff, 779px 1231px #fff, 552px 932px #fff,
1057px 1196px #fff, 282px 1280px #fff, 496px 1986px #fff, 1833px 1120px #fff,
1802px 1293px #fff, 6px 1696px #fff, 412px 1902px #fff, 605px 438px #fff,
24px 1212px #fff, 234px 1320px #fff, 544px 344px #fff, 1107px 170px #fff,
1603px 196px #fff, 905px 648px #fff, 68px 1458px #fff, 649px 1969px #fff,
744px 675px #fff, 1127px 478px #fff, 714px 1814px #fff, 1486px 526px #fff,
270px 1636px #fff, 1931px 149px #fff, 1807px 378px #fff, 8px 390px #fff,
1415px 699px #fff, 1473px 1211px #fff, 1590px 141px #fff, 270px 1705px #fff,
69px 1423px #fff, 1108px 1053px #fff, 1946px 128px #fff, 371px 371px #fff,
1490px 220px #fff, 357px 1885px #fff, 363px 363px #fff, 1896px 1256px #fff,
1979px 1050px #fff, 947px 1342px #fff, 1754px 242px #fff, 514px 974px #fff,
65px 1477px #fff, 1840px 547px #fff, 950px 695px #fff, 459px 1150px #fff,
1124px 1502px #fff, 481px 940px #fff, 680px 839px #fff, 797px 1169px #fff,
1977px 1491px #fff, 734px 1724px #fff, 210px 298px #fff, 816px 628px #fff,
686px 770px #fff, 1721px 267px #fff, 1663px 511px #fff, 1481px 1141px #fff,
582px 248px #fff, 1308px 953px #fff, 628px 657px #fff, 897px 1535px #fff,
270px 931px #fff, 791px 467px #fff, 1336px 1732px #fff, 1013px 1653px #fff,
1911px 956px #fff, 587px 816px #fff, 83px 456px #fff, 930px 1478px #fff,
1587px 1694px #fff, 614px 1200px #fff, 302px 1782px #fff, 1711px 1432px #fff,
443px 904px #fff, 1666px 714px #fff, 1588px 1167px #fff, 273px 1075px #fff,
1679px 461px #fff, 721px 664px #fff, 1202px 10px #fff, 166px 1126px #fff,
331px 1628px #fff, 430px 1565px #fff, 1585px 509px #fff, 640px 38px #fff,
822px 837px #fff, 1760px 1664px #fff, 1122px 1458px #fff, 398px 131px #fff,
689px 285px #fff, 460px 652px #fff, 1627px 365px #fff, 348px 1648px #fff,
819px 1946px #fff, 981px 1917px #fff, 323px 76px #fff, 979px 684px #fff,
887px 536px #fff, 1348px 1596px #fff, 1055px 666px #fff, 1402px 1797px #fff,
1300px 1055px #fff, 937px 238px #fff, 1474px 1815px #fff, 1144px 1710px #fff,
1629px 1087px #fff, 911px 919px #fff, 771px 819px #fff, 403px 720px #fff,
163px 736px #fff, 1062px 238px #fff, 1774px 818px #fff, 1874px 1178px #fff,
1177px 699px #fff, 1244px 1244px #fff, 1371px 58px #fff, 564px 1515px #fff,
1824px 487px #fff, 929px 702px #fff, 394px 1348px #fff, 1161px 641px #fff,
219px 1841px #fff, 358px 941px #fff, 140px 1759px #fff, 1019px 1345px #fff,
274px 436px #fff, 1433px 1605px #fff, 1798px 1426px #fff, 294px 1848px #fff,
1681px 1877px #fff, 1344px 1824px #fff, 1439px 1632px #fff,
161px 1012px #fff, 1308px 588px #fff, 1789px 582px #fff, 721px 1910px #fff,
318px 218px #fff, 607px 319px #fff, 495px 535px #fff, 1552px 1575px #fff,
1562px 67px #fff, 403px 926px #fff, 1096px 1800px #fff, 1814px 1709px #fff,
1882px 1831px #fff, 533px 46px #fff, 823px 969px #fff, 530px 165px #fff,
1030px 352px #fff, 1681px 313px #fff, 338px 115px #fff, 1607px 211px #fff,
1718px 1184px #fff, 1589px 659px #fff, 278px 355px #fff, 464px 1464px #fff,
1165px 277px #fff, 950px 694px #fff, 1746px 293px #fff, 793px 911px #fff,
528px 773px #fff, 1883px 1694px #fff, 748px 182px #fff, 1924px 1531px #fff,
100px 636px #fff, 1473px 1445px #fff, 1264px 1244px #fff, 850px 1377px #fff,
987px 1976px #fff, 933px 1761px #fff, 922px 1270px #fff, 500px 396px #fff,
1324px 8px #fff, 1967px 1814px #fff, 1072px 1401px #fff, 961px 37px #fff,
156px 81px #fff, 1915px 502px #fff, 1076px 1846px #fff, 152px 1669px #fff,
986px 1529px #fff, 1667px 1137px #fff;
}
#stars2:after {
content: '';
position: absolute;
top: auto;
width: 2px;
height: 2px;
background: transparent;
box-shadow: 1448px 320px #fff, 1775px 1663px #fff, 332px 1364px #fff,
878px 340px #fff, 569px 1832px #fff, 1422px 1684px #fff, 1946px 1907px #fff,
121px 979px #fff, 1044px 1069px #fff, 463px 381px #fff, 423px 112px #fff,
523px 1179px #fff, 779px 654px #fff, 1398px 694px #fff, 1085px 1464px #fff,
1599px 1869px #fff, 801px 1882px #fff, 779px 1231px #fff, 552px 932px #fff,
1057px 1196px #fff, 282px 1280px #fff, 496px 1986px #fff, 1833px 1120px #fff,
1802px 1293px #fff, 6px 1696px #fff, 412px 1902px #fff, 605px 438px #fff,
24px 1212px #fff, 234px 1320px #fff, 544px 344px #fff, 1107px 170px #fff,
1603px 196px #fff, 905px 648px #fff, 68px 1458px #fff, 649px 1969px #fff,
744px 675px #fff, 1127px 478px #fff, 714px 1814px #fff, 1486px 526px #fff,
270px 1636px #fff, 1931px 149px #fff, 1807px 378px #fff, 8px 390px #fff,
1415px 699px #fff, 1473px 1211px #fff, 1590px 141px #fff, 270px 1705px #fff,
69px 1423px #fff, 1108px 1053px #fff, 1946px 128px #fff, 371px 371px #fff,
1490px 220px #fff, 357px 1885px #fff, 363px 363px #fff, 1896px 1256px #fff,
1979px 1050px #fff, 947px 1342px #fff, 1754px 242px #fff, 514px 974px #fff,
65px 1477px #fff, 1840px 547px #fff, 950px 695px #fff, 459px 1150px #fff,
1124px 1502px #fff, 481px 940px #fff, 680px 839px #fff, 797px 1169px #fff,
1977px 1491px #fff, 734px 1724px #fff, 210px 298px #fff, 816px 628px #fff,
686px 770px #fff, 1721px 267px #fff, 1663px 511px #fff, 1481px 1141px #fff,
582px 248px #fff, 1308px 953px #fff, 628px 657px #fff, 897px 1535px #fff,
270px 931px #fff, 791px 467px #fff, 1336px 1732px #fff, 1013px 1653px #fff,
1911px 956px #fff, 587px 816px #fff, 83px 456px #fff, 930px 1478px #fff,
1587px 1694px #fff, 614px 1200px #fff, 302px 1782px #fff, 1711px 1432px #fff,
443px 904px #fff, 1666px 714px #fff, 1588px 1167px #fff, 273px 1075px #fff,
1679px 461px #fff, 721px 664px #fff, 1202px 10px #fff, 166px 1126px #fff,
331px 1628px #fff, 430px 1565px #fff, 1585px 509px #fff, 640px 38px #fff,
822px 837px #fff, 1760px 1664px #fff, 1122px 1458px #fff, 398px 131px #fff,
689px 285px #fff, 460px 652px #fff, 1627px 365px #fff, 348px 1648px #fff,
819px 1946px #fff, 981px 1917px #fff, 323px 76px #fff, 979px 684px #fff,
887px 536px #fff, 1348px 1596px #fff, 1055px 666px #fff, 1402px 1797px #fff,
1300px 1055px #fff, 937px 238px #fff, 1474px 1815px #fff, 1144px 1710px #fff,
1629px 1087px #fff, 911px 919px #fff, 771px 819px #fff, 403px 720px #fff,
163px 736px #fff, 1062px 238px #fff, 1774px 818px #fff, 1874px 1178px #fff,
1177px 699px #fff, 1244px 1244px #fff, 1371px 58px #fff, 564px 1515px #fff,
1824px 487px #fff, 929px 702px #fff, 394px 1348px #fff, 1161px 641px #fff,
219px 1841px #fff, 358px 941px #fff, 140px 1759px #fff, 1019px 1345px #fff,
274px 436px #fff, 1433px 1605px #fff, 1798px 1426px #fff, 294px 1848px #fff,
1681px 1877px #fff, 1344px 1824px #fff, 1439px 1632px #fff,
161px 1012px #fff, 1308px 588px #fff, 1789px 582px #fff, 721px 1910px #fff,
318px 218px #fff, 607px 319px #fff, 495px 535px #fff, 1552px 1575px #fff,
1562px 67px #fff, 403px 926px #fff, 1096px 1800px #fff, 1814px 1709px #fff,
1882px 1831px #fff, 533px 46px #fff, 823px 969px #fff, 530px 165px #fff,
1030px 352px #fff, 1681px 313px #fff, 338px 115px #fff, 1607px 211px #fff,
1718px 1184px #fff, 1589px 659px #fff, 278px 355px #fff, 464px 1464px #fff,
1165px 277px #fff, 950px 694px #fff, 1746px 293px #fff, 793px 911px #fff,
528px 773px #fff, 1883px 1694px #fff, 748px 182px #fff, 1924px 1531px #fff,
100px 636px #fff, 1473px 1445px #fff, 1264px 1244px #fff, 850px 1377px #fff,
987px 1976px #fff, 933px 1761px #fff, 922px 1270px #fff, 500px 396px #fff,
1324px 8px #fff, 1967px 1814px #fff, 1072px 1401px #fff, 961px 37px #fff,
156px 81px #fff, 1915px 502px #fff, 1076px 1846px #fff, 152px 1669px #fff,
986px 1529px #fff, 1667px 1137px #fff;
}
#stars3 {
width: 3px;
height: 3px;
background: transparent;
animation: animStar 240s linear infinite;
box-shadow: 387px 1878px #fff, 760px 1564px #fff, 1487px 999px #fff,
948px 1828px #fff, 1977px 1001px #fff, 1284px 1963px #fff, 656px 284px #fff,
1268px 1635px #fff, 1820px 598px #fff, 642px 1900px #fff, 296px 57px #fff,
921px 1620px #fff, 476px 1858px #fff, 658px 613px #fff, 1171px 1363px #fff,
1419px 283px #fff, 1037px 731px #fff, 503px 663px #fff, 1562px 463px #fff,
383px 1197px #fff, 1171px 1233px #fff, 876px 1768px #fff, 856px 1615px #fff,
1375px 1924px #fff, 1725px 918px #fff, 952px 119px #fff, 768px 1212px #fff,
992px 1462px #fff, 1929px 717px #fff, 1947px 755px #fff, 1818px 1123px #fff,
1896px 1672px #fff, 460px 198px #fff, 256px 271px #fff, 752px 544px #fff,
1222px 1859px #fff, 1851px 443px #fff, 313px 1858px #fff, 709px 446px #fff,
1546px 697px #fff, 674px 1155px #fff, 1112px 130px #fff, 355px 1790px #fff,
1496px 974px #fff, 1696px 480px #fff, 1316px 1265px #fff, 1645px 1063px #fff,
1182px 237px #fff, 427px 1582px #fff, 859px 253px #fff, 458px 939px #fff,
1517px 1644px #fff, 1943px 60px #fff, 212px 1650px #fff, 966px 1786px #fff,
473px 712px #fff, 130px 76px #fff, 1417px 1186px #fff, 909px 1580px #fff,
1913px 762px #fff, 204px 1143px #fff, 1998px 1057px #fff, 1468px 1301px #fff,
144px 1676px #fff, 21px 1601px #fff, 382px 1362px #fff, 912px 753px #fff,
1488px 1405px #fff, 802px 156px #fff, 174px 550px #fff, 338px 1366px #fff,
1197px 774px #fff, 602px 486px #fff, 682px 1877px #fff, 348px 1503px #fff,
407px 1139px #fff, 950px 1400px #fff, 922px 1139px #fff, 1697px 293px #fff,
1238px 1281px #fff, 1038px 1197px #fff, 376px 1889px #fff,
1255px 1680px #fff, 1008px 1316px #fff, 1538px 1447px #fff,
1186px 874px #fff, 1967px 640px #fff, 1341px 19px #fff, 29px 1732px #fff,
16px 1650px #fff, 1021px 1075px #fff, 723px 424px #fff, 1175px 41px #fff,
494px 1957px #fff, 1296px 431px #fff, 175px 1507px #fff, 831px 121px #fff,
498px 1947px #fff, 617px 880px #fff, 240px 403px #fff;
}
#stars3:after {
content: '';
position: absolute;
top: auto;
width: 3px;
height: 3px;
background: transparent;
box-shadow: 387px 1878px #fff, 760px 1564px #fff, 1487px 999px #fff,
948px 1828px #fff, 1977px 1001px #fff, 1284px 1963px #fff, 656px 284px #fff,
1268px 1635px #fff, 1820px 598px #fff, 642px 1900px #fff, 296px 57px #fff,
921px 1620px #fff, 476px 1858px #fff, 658px 613px #fff, 1171px 1363px #fff,
1419px 283px #fff, 1037px 731px #fff, 503px 663px #fff, 1562px 463px #fff,
383px 1197px #fff, 1171px 1233px #fff, 876px 1768px #fff, 856px 1615px #fff,
1375px 1924px #fff, 1725px 918px #fff, 952px 119px #fff, 768px 1212px #fff,
992px 1462px #fff, 1929px 717px #fff, 1947px 755px #fff, 1818px 1123px #fff,
1896px 1672px #fff, 460px 198px #fff, 256px 271px #fff, 752px 544px #fff,
1222px 1859px #fff, 1851px 443px #fff, 313px 1858px #fff, 709px 446px #fff,
1546px 697px #fff, 674px 1155px #fff, 1112px 130px #fff, 355px 1790px #fff,
1496px 974px #fff, 1696px 480px #fff, 1316px 1265px #fff, 1645px 1063px #fff,
1182px 237px #fff, 427px 1582px #fff, 859px 253px #fff, 458px 939px #fff,
1517px 1644px #fff, 1943px 60px #fff, 212px 1650px #fff, 966px 1786px #fff,
473px 712px #fff, 130px 76px #fff, 1417px 1186px #fff, 909px 1580px #fff,
1913px 762px #fff, 204px 1143px #fff, 1998px 1057px #fff, 1468px 1301px #fff,
144px 1676px #fff, 21px 1601px #fff, 382px 1362px #fff, 912px 753px #fff,
1488px 1405px #fff, 802px 156px #fff, 174px 550px #fff, 338px 1366px #fff,
1197px 774px #fff, 602px 486px #fff, 682px 1877px #fff, 348px 1503px #fff,
407px 1139px #fff, 950px 1400px #fff, 922px 1139px #fff, 1697px 293px #fff,
1238px 1281px #fff, 1038px 1197px #fff, 376px 1889px #fff,
1255px 1680px #fff, 1008px 1316px #fff, 1538px 1447px #fff,
1186px 874px #fff, 1967px 640px #fff, 1341px 19px #fff, 29px 1732px #fff,
16px 1650px #fff, 1021px 1075px #fff, 723px 424px #fff, 1175px 41px #fff,
494px 1957px #fff, 1296px 431px #fff, 175px 1507px #fff, 831px 121px #fff,
498px 1947px #fff, 617px 880px #fff, 240px 403px #fff;
}

93
index.html Normal file
View File

@@ -0,0 +1,93 @@
<!DOCTYPE html>
<html lang="en">
<head>
<title>Java Team Six: Learn</title>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="stylesheet" href="https://use.fontawesome.com/releases/v5.8.1/css/all.css">
<link rel="stylesheet" href="css/starfield.css">
<link rel="icon" type="image/png" sizes="32x32" href="https://cdn.allmylinks.com/prod/User/photo/l/U/t/sCUgUDbSvbSWlRpakzRe3K8ridPWbym-.jpg">
</head>
<body>
<section class="animated-background">
<div id="stars1"></div>
<div id="stars2"></div>
<div id="stars3"></div>
</section>
<br />
<div style="display:hidden"> <a target="hq" id="profilePicture" href="https://softwareshinobi.com">
<img src="https://cdn.allmylinks.com/prod/User/photo/l/U/t/sCUgUDbSvbSWlRpakzRe3K8ridPWbym-.jpg" alt="Software Shinobi">
</a>
<div class="overlay" id="popup">
<div class="popup">
<div class="popup-photo">
<img src="https://cdn.allmylinks.com/prod/User/photo/l/U/t/sCUgUDbSvbSWlRpakzRe3K8ridPWbym-.jpg" alt="software shinobi">
</div>
</div>
</div>
<br />
<center> <div id="userName">
I help experienced Java developers upskill in Git, Docker, Linux, CI/CD, and AWS for smooth, automated builds and deployments.
</div>
</center>
<br />
</div>
<div id="links">
<a class="link" target="_blank" rel="noopener noreferrer" href="https://linux.softwareshinobi.com">
<i class="fab fa-linux"> </i>
Free Linux Training
</a>
</div>
<div id="links">
<a class="link" target="_blank" rel="noopener noreferrer" href="https://bash.softwareshinobi.com">
<i class="fas fa-terminal"> </i>
Free Bash Training
</a>
</div>
<div id="links">
<a class="link" target="_blank" rel="noopener noreferrer" href="https://git.softwareshinobi.com">
<i class="fab fa-github"> </i>
Free Git Training
</a>
</div>
<div id="links">
<a class="link" target="_blank" rel="noopener noreferrer" href="https://docker.softwareshinobi.com">
<i class="fab fa-docker"> </i>
Free Docker Training
</a>
</div>
<div id="links">
<a class="link" target="_blank" rel="noopener noreferrer" href="https://databases.softwareshinobi.com">
<i class="fas fa-database"> </i>
Free Databases Training
</a>
</div>
<div id="hashtag">
I help experienced Java developers upskill in Git, Docker, Linux, CI/CD, and AWS for smooth, automated builds and deployments.
</div>
</body>
</html>

15
landing/Dockerfile
View File

@@ -1,15 +0,0 @@
FROM titom73/mkdocs AS MKDOCS_BUILD
RUN pip install markupsafe==2.0.1
RUN pip install mkdocs-blog-plugin
WORKDIR /docs
COPY . .
RUN mkdocs build
FROM mengzyou/bbhttpd:1.35
COPY --from=MKDOCS_BUILD --chown=www:www /docs/site /home/www/html

19
landing/compose.bash
View File

@@ -1,19 +0,0 @@
#!/bin/bash
##
reset
clear
##
set -e
set -x
##
docker compose down --remove-orphans
docker compose up --build -d

24
landing/compose.yaml
View File

@@ -1,24 +0,0 @@
services:
shinobi-academy-linux-docs:
container_name: shinobi-academy-linux-docs
image: softwareshinobi/shinobi-academy-linux-docs
build:
context: .
dockerfile: Dockerfile
restart: unless-stopped
ports:
- 8000:8000
# volumes:
# - ./docs:/docs/docs
# - ./mkdocs.yml:/docs/mkdocs.yml
#

91
landing/docs/.Bash-Scripting/000-about-the-author.md
View File

@@ -1,91 +0,0 @@
# About the book
* **This version was published on Oct 30 2023**
This is an open-source introduction to Bash scripting guide that will help you learn the basics of Bash scripting and start writing awesome Bash scripts that will help you automate your daily SysOps, DevOps, and Dev tasks. No matter if you are a DevOps/SysOps engineer, developer, or just a Linux enthusiast, you can use Bash scripts to combine different Linux commands and automate tedious and repetitive daily tasks so that you can focus on more productive and fun things.
The guide is suitable for anyone working as a developer, system administrator, or a DevOps engineer and wants to learn the basics of Bash scripting.
The first 13 chapters would be purely focused on getting some solid Bash scripting foundations, then the rest of the chapters would give you some real-life examples and scripts.
## About the author
My name is Bobby Iliev, and I have been working as a Linux DevOps Engineer since 2014. I am an avid Linux lover and supporter of the open-source movement philosophy. I am always doing that which I cannot do in order that I may learn how to do it, and I believe in sharing knowledge.
I think it's essential always to keep professional and surround yourself with good people, work hard, and be nice to everyone. You have to perform at a consistently higher level than others. That's the mark of a true professional.
For more information, please visit my blog at [https://bobbyiliev.com](https://bobbyiliev.com), follow me on Twitter [@bobbyiliev_](https://twitter.com/bobbyiliev_) and [YouTube](https://www.youtube.com/channel/UCQWmdHTeAO0UvaNqve9udRw).
## Sponsors
This book is made possible thanks to these fantastic companies!
### Materialize
The Streaming Database for Real-time Analytics.
[Materialize](https://materialize.com/) is a reactive database that delivers incremental view updates. Materialize helps developers easily build with streaming data using standard SQL.
### DigitalOcean
DigitalOcean is a cloud services platform delivering the simplicity developers love and businesses trust to run production applications at scale.
It provides highly available, secure, and scalable compute, storage, and networking solutions that help developers build great software faster.
Founded in 2012 with offices in New York and Cambridge, MA, DigitalOcean offers transparent and affordable pricing, an elegant user interface, and one of the largest libraries of open source resources available.
For more information, please visit [https://www.digitalocean.com](https://www.digitalocean.com) or follow [@digitalocean](https://twitter.com/digitalocean) on Twitter.
If you are new to DigitalOcean, you can get a free $200 credit and spin up your own servers via this referral link here:
[Free $200 Credit For DigitalOcean](https://m.do.co/c/2a9bba940f39)
### DevDojo
The DevDojo is a resource to learn all things web development and web design. Learn on your lunch break or wake up and enjoy a cup of coffee with us to learn something new.
Join this developer community, and we can all learn together, build together, and grow together.
[Join DevDojo](https://devdojo.com?ref=bobbyiliev)
For more information, please visit [https://www.devdojo.com](https://www.devdojo.com?ref=bobbyiliev) or follow [@thedevdojo](https://twitter.com/thedevdojo) on Twitter.
## Ebook PDF Generation Tool
This ebook was generated by [Ibis](https://github.com/themsaid/ibis/) developed by [Mohamed Said](https://github.com/themsaid).
Ibis is a PHP tool that helps you write eBooks in markdown.
## Ebook ePub Generation Tool
The ePub version was generated by [Pandoc](https://pandoc.org/).
## Book Cover
The cover for this ebook was created with [Canva.com](https://www.canva.com/join/determined-cork-learn).
If you ever need to create a graphic, poster, invitation, logo, presentation – or anything that looks good — give Canva a go.
## License
MIT License
Copyright (c) 2020 Bobby Iliev
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

11
landing/docs/.Bash-Scripting/001-introduction-to-bash.md
View File

@@ -1,11 +0,0 @@
# Introduction to Bash scripting
Welcome to this Bash basics training guide! In this **bash crash course**, you will learn the **Bash basics** so you could start writing your own Bash scripts and automate your daily tasks.
Bash is a Unix shell and command language. It is widely available on various operating systems, and it is also the default command interpreter on most Linux systems.
Bash stands for Bourne-Again SHell. As with other shells, you can use Bash interactively directly in your terminal, and also, you can use Bash like any other programming language to write scripts. This book will help you learn the basics of Bash scripting including Bash Variables, User Input, Comments, Arguments, Arrays, Conditional Expressions, Conditionals, Loops, Functions, Debugging, and testing.
Bash scripts are great for automating repetitive workloads and can help you save time considerably. For example, imagine working with a group of five developers on a project that requires a tedious environment setup. In order for the program to work correctly, each developer has to manually set up the environment. That's the same and very long task (setting up the environment) repeated five times at least. This is where you and Bash scripts come to the rescue! So instead, you create a simple text file containing all the necessary instructions and share it with your teammates. And now, all they have to do is execute the Bash script and everything will be created for them.
In order to write Bash scripts, you just need a UNIX terminal and a text editor like Sublime Text, VS Code, or a terminal-based editor like vim or nano.

32
landing/docs/.Bash-Scripting/002-bash-structure.md
View File

@@ -1,32 +0,0 @@
# Bash Structure
Let's start by creating a new file with a `.sh` extension. As an example, we could create a file called `devdojo.sh`.
To create that file, you can use the `touch` command:
```bash
touch devdojo.sh
```
Or you can use your text editor instead:
```bash
nano devdojo.sh
```
In order to execute/run a bash script file with the bash shell interpreter, the first line of a script file must indicate the absolute path to the bash executable:
```bash
#!/bin/bash
```
This is also called a [Shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)).
All that the shebang does is to instruct the operating system to run the script with the `/bin/bash` executable.
However, bash is not always in `/bin/bash` directory, particularly on non-Linux systems or due to installation as an optional package. Thus, you may want to use:
```bash
#!/usr/bin/env bash
```
It searches for bash executable in directories, listed in PATH environmental variable.

41
landing/docs/.Bash-Scripting/003-bash-hello-world.md
View File

@@ -1,41 +0,0 @@
# Bash Hello World
Once we have our `devdojo.sh` file created and we've specified the bash shebang on the very first line, we are ready to create our first `Hello World` bash script.
To do that, open the `devdojo.sh` file again and add the following after the `#!/bin/bash` line:
```bash
#!/bin/bash
echo "Hello World!"
```
Save the file and exit.
After that make the script executable by running:
```bash
chmod +x devdojo.sh
```
After that execute the file:
```bash
./devdojo.sh
```
You will see a "Hello World" message on the screen.
Another way to run the script would be:
```bash
bash devdojo.sh
```
As bash can be used interactively, you could run the following command directly in your terminal and you would get the same result:
```bash
echo "Hello DevDojo!"
```
Putting a script together is useful once you have to combine multiple commands together.

131
landing/docs/.Bash-Scripting/004-bash-variables.md
View File

@@ -1,131 +0,0 @@
# Bash Variables
As in any other programming language, you can use variables in Bash Scripting as well. However, there are no data types, and a variable in Bash can contain numbers as well as characters.
To assign a value to a variable, all you need to do is use the `=` sign:
```bash
name="DevDojo"
```
>{notice} as an important note, you can not have spaces before and after the `=` sign.
After that, to access the variable, you have to use the `$` and reference it as shown below:
```bash
echo $name
```
Wrapping the variable name between curly brackets is not required, but is considered a good practice, and I would advise you to use them whenever you can:
```bash
echo ${name}
```
The above code would output: `DevDojo` as this is the value of our `name` variable.
Next, let's update our `devdojo.sh` script and include a variable in it.
Again, you can open the file `devdojo.sh` with your favorite text editor, I'm using nano here to open the file:
```bash
nano devdojo.sh
```
Adding our `name` variable here in the file, with a welcome message. Our file now looks like this:
```bash
#!/bin/bash
name="DevDojo"
echo "Hi there $name"
```
Save it and run the file using the command below:
```bash
./devdojo.sh
```
You would see the following output on your screen:
```bash
Hi there DevDojo
```
Here is a rundown of the script written in the file:
* `#!/bin/bash` - At first, we specified our shebang.
* `name=DevDojo` - Then, we defined a variable called `name` and assigned a value to it.
* `echo "Hi there $name"` - Finally, we output the content of the variable on the screen as a welcome message by using `echo`
You can also add multiple variables in the file as shown below:
```bash
#!/bin/bash
name="DevDojo"
greeting="Hello"
echo "$greeting $name"
```
Save the file and run it again:
```bash
./devdojo.sh
```
You would see the following output on your screen:
```bash
Hello DevDojo
```
Note that you don't necessarily need to add semicolon `;` at the end of each line. It works both ways, a bit like other programming language such as JavaScript!
You can also add variables in the Command Line outside the Bash script and they can be read as parameters:
```bash
./devdojo.sh Bobby buddy!
```
This script takes in two parameters `Bobby`and `buddy!` separated by space. In the `devdojo.sh` file we have the following:
```bash
#!/bin/bash
echo "Hello there" $1
```
`$1` is the first input (`Bobby`) in the Command Line. Similarly, there could be more inputs and they are all referenced to by the `$` sign and their respective order of input. This means that `buddy!` is referenced to using `$2`. Another useful method for reading variables is the `$@` which reads all inputs.
So now let's change the `devdojo.sh` file to better understand:
```bash
#!/bin/bash
echo "Hello there" $1
# $1 : first parameter
echo "Hello there" $2
# $2 : second parameter
echo "Hello there" $@
# $@ : all
```
The output for:
```bash
./devdojo.sh Bobby buddy!
```
Would be the following:
```bash
Hello there Bobby
Hello there buddy!
Hello there Bobby buddy!
```

54
landing/docs/.Bash-Scripting/005-bash-user-input.md
View File

@@ -1,54 +0,0 @@
# Bash User Input
With the previous script, we defined a variable, and we output the value of the variable on the screen with the `echo $name`.
Now let's go ahead and ask the user for input instead. To do that again, open the file with your favorite text editor and update the script as follows:
```bash
#!/bin/bash
echo "What is your name?"
read name
echo "Hi there $name"
echo "Welcome to DevDojo!"
```
The above will prompt the user for input and then store that input as a string/text in a variable.
We can then use the variable and print a message back to them.
The output of the above script would be:
* First run the script:
```bash
./devdojo.sh
```
* Then, you would be prompted to enter your name:
```
What is your name?
Bobby
```
* Once you've typed your name, just hit enter, and you will get the following output:
```
Hi there Bobby
Welcome to DevDojo!
```
To reduce the code, we could change the first `echo` statement with the `read -p`, the `read` command used with `-p` flag will print a message before prompting the user for their input:
```bash
#!/bin/bash
read -p "What is your name? " name
echo "Hi there $name"
echo "Welcome to DevDojo!"
```
Make sure to test this out yourself as well!

27
landing/docs/.Bash-Scripting/006-bash-comments.md
View File

@@ -1,27 +0,0 @@
# Bash Comments
As with any other programming language, you can add comments to your script. Comments are used to leave yourself notes through your code.
To do that in Bash, you need to add the `#` symbol at the beginning of the line. Comments will never be rendered on the screen.
Here is an example of a comment:
```bash
# This is a comment and will not be rendered on the screen
```
Let's go ahead and add some comments to our script:
```bash
#!/bin/bash
# Ask the user for their name
read -p "What is your name? " name
# Greet the user
echo "Hi there $name"
echo "Welcome to DevDojo!"
```
Comments are a great way to describe some of the more complex functionality directly in your scripts so that other people could find their way around your code with ease.

81
landing/docs/.Bash-Scripting/007-bash-arguments.md
View File

@@ -1,81 +0,0 @@
# Bash Arguments
You can pass arguments to your shell script when you execute it. To pass an argument, you just need to write it right after the name of your script. For example:
```bash
./devdojo.com your_argument
```
In the script, we can then use `$1` in order to reference the first argument that we specified.
If we pass a second argument, it would be available as `$2` and so on.
Let's create a short script called `arguments.sh` as an example:
```bash
#!/bin/bash
echo "Argument one is $1"
echo "Argument two is $2"
echo "Argument three is $3"
```
Save the file and make it executable:
```bash
chmod +x arguments.sh
```
Then run the file and pass **3** arguments:
```bash
./arguments.sh dog cat bird
```
The output that you would get would be:
```bash
Argument one is dog
Argument two is cat
Argument three is bird
```
To reference all arguments, you can use `$@`:
```bash
#!/bin/bash
echo "All arguments: $@"
```
If you run the script again:
```bash
./arguments.sh dog cat bird
```
You will get the following output:
```
All arguments: dog cat bird
```
Another thing that you need to keep in mind is that `$0` is used to reference the script itself.
This is an excellent way to create self destruct the file if you need to or just get the name of the script.
For example, let's create a script that prints out the name of the file and deletes the file after that:
```bash
#!/bin/bash
echo "The name of the file is: $0 and it is going to be self-deleted."
rm -f $0
```
You need to be careful with the self deletion and ensure that you have your script backed up before you self-delete it.

112
landing/docs/.Bash-Scripting/008-bash-arrays.md
View File

@@ -1,112 +0,0 @@
# Bash Arrays
If you have ever done any programming, you are probably already familiar with arrays.
But just in case you are not a developer, the main thing that you need to know is that unlike variables, arrays can hold several values under one name.
You can initialize an array by assigning values divided by space and enclosed in `()`. Example:
```bash
my_array=("value 1" "value 2" "value 3" "value 4")
```
To access the elements in the array, you need to reference them by their numeric index.
>{notice} keep in mind that you need to use curly brackets.
* Access a single element, this would output: `value 2`
```bash
echo ${my_array[1]}
```
* This would return the last element: `value 4`
```bash
echo ${my_array[-1]}
```
* As with command line arguments using `@` will return all arguments in the array, as follows: `value 1 value 2 value 3 value 4`
```bash
echo ${my_array[@]}
```
* Prepending the array with a hash sign (`#`) would output the total number of elements in the array, in our case it is `4`:
```bash
echo ${#my_array[@]}
```
Make sure to test this and practice it at your end with different values.
## Substring in Bash :: Slicing
Let's review the following example of slicing in a string in Bash:
```bash
#!/bin/bash
letters=( "A""B""C""D""E" )
echo ${letters[@]}
```
This command will print all the elements of an array.
Output:
```bash
$ ABCDE
```
Let's see a few more examples:
- Example 1
```bash
#!/bin/bash
letters=( "A""B""C""D""E" )
b=${letters:0:2}
echo "${b}"
```
This command will print array from starting index 0 to 2 where 2 is exclusive.
```bash
$ AB
```
- Example 2
```bash
#!/bin/bash
letters=( "A""B""C""D""E" )
b=${letters::5}
echo "${b}"
```
This command will print from base index 0 to 5, where 5 is exclusive and starting index is default set to 0 .
```bash
$ ABCDE
```
- Example 3
```bash
#!/bin/bash
letters=( "A""B""C""D""E" )
b=${letters:3}
echo "${b}"
```
This command will print from starting index
3 to end of array inclusive .
```bash
$ DE
```

186
landing/docs/.Bash-Scripting/009-bash-conditional-expressions.md
View File

@@ -1,186 +0,0 @@
# Bash Conditional Expressions
In computer science, conditional statements, conditional expressions, and conditional constructs are features of a programming language, which perform different computations or actions depending on whether a programmer-specified boolean condition evaluates to true or false.
In Bash, conditional expressions are used by the `[[` compound command and the `[`built-in commands to test file attributes and perform string and arithmetic comparisons.
Here is a list of the most popular Bash conditional expressions. You do not have to memorize them by heart. You can simply refer back to this list whenever you need it!
## File expressions
* True if file exists.
```bash
[[ -a ${file} ]]
```
* True if file exists and is a block special file.
```bash
[[ -b ${file} ]]
```
* True if file exists and is a character special file.
```bash
[[ -c ${file} ]]
```
* True if file exists and is a directory.
```bash
[[ -d ${file} ]]
```
* True if file exists.
```bash
[[ -e ${file} ]]
```
* True if file exists and is a regular file.
```bash
[[ -f ${file} ]]
```
* True if file exists and is a symbolic link.
```bash
[[ -h ${file} ]]
```
* True if file exists and is readable.
```bash
[[ -r ${file} ]]
```
* True if file exists and has a size greater than zero.
```bash
[[ -s ${file} ]]
```
* True if file exists and is writable.
```bash
[[ -w ${file} ]]
```
* True if file exists and is executable.
```bash
[[ -x ${file} ]]
```
* True if file exists and is a symbolic link.
```bash
[[ -L ${file} ]]
```
## String expressions
* True if the shell variable varname is set (has been assigned a value).
```bash
[[ -v ${varname} ]]
```
True if the length of the string is zero.
```bash
[[ -z ${string} ]]
```
True if the length of the string is non-zero.
```bash
[[ -n ${string} ]]
```
* True if the strings are equal. `=` should be used with the test command for POSIX conformance. When used with the `[[` command, this performs pattern matching as described above (Compound Commands).
```bash
[[ ${string1} == ${string2} ]]
```
* True if the strings are not equal.
```bash
[[ ${string1} != ${string2} ]]
```
* True if string1 sorts before string2 lexicographically.
```bash
[[ ${string1} < ${string2} ]]
```
* True if string1 sorts after string2 lexicographically.
```bash
[[ ${string1} > ${string2} ]]
```
## Arithmetic operators
* Returns true if the numbers are **equal**
```bash
[[ ${arg1} -eq ${arg2} ]]
```
* Returns true if the numbers are **not equal**
```bash
[[ ${arg1} -ne ${arg2} ]]
```
* Returns true if arg1 is **less than** arg2
```bash
[[ ${arg1} -lt ${arg2} ]]
```
* Returns true if arg1 is **less than or equal** arg2
```bash
[[ ${arg1} -le ${arg2} ]]
```
* Returns true if arg1 is **greater than** arg2
```bash
[[ ${arg1} -gt ${arg2} ]]
```
* Returns true if arg1 is **greater than or equal** arg2
```bash
[[ ${arg1} -ge ${arg2} ]]
```
As a side note, arg1 and arg2 may be positive or negative integers.
As with other programming languages you can use `AND` & `OR` conditions:
```bash
[[ test_case_1 ]] && [[ test_case_2 ]] # And
[[ test_case_1 ]] || [[ test_case_2 ]] # Or
```
## Exit status operators
* returns true if the command was successful without any errors
```bash
[[ $? -eq 0 ]]
```
* returns true if the command was not successful or had errors
```bash
[[ $? -gt 0 ]]
```

187
landing/docs/.Bash-Scripting/010-bash-conditionals.md
View File

@@ -1,187 +0,0 @@
# Bash Conditionals
In the last section, we covered some of the most popular conditional expressions. We can now use them with standard conditional statements like `if`, `if-else` and `switch case` statements.
## If statement
The format of an `if` statement in Bash is as follows:
```bash
if [[ some_test ]]
then
<commands>
fi
```
Here is a quick example which would ask you to enter your name in case that you've left it empty:
```bash
#!/bin/bash
# Bash if statement example
read -p "What is your name? " name
if [[ -z ${name} ]]
then
echo "Please enter your name!"
fi
```
## If Else statement
With an `if-else` statement, you can specify an action in case that the condition in the `if` statement does not match. We can combine this with the conditional expressions from the previous section as follows:
```bash
#!/bin/bash
# Bash if statement example
read -p "What is your name? " name
if [[ -z ${name} ]]
then
echo "Please enter your name!"
else
echo "Hi there ${name}"
fi
```
You can use the above if statement with all of the conditional expressions from the previous chapters:
```bash
#!/bin/bash
admin="devdojo"
read -p "Enter your username? " username
# Check if the username provided is the admin
if [[ "${username}" == "${admin}" ]] ; then
echo "You are the admin user!"
else
echo "You are NOT the admin user!"
fi
```
Here is another example of an `if` statement which would check your current `User ID` and would not allow you to run the script as the `root` user:
```bash
#!/bin/bash
if (( $EUID == 0 )); then
echo "Please do not run as root"
exit
fi
```
If you put this on top of your script it would exit in case that the EUID is 0 and would not execute the rest of the script. This was discussed on [the DigitalOcean community forum](https://www.digitalocean.com/community/questions/how-to-check-if-running-as-root-in-a-bash-script).
You can also test multiple conditions with an `if` statement. In this example we want to make sure that the user is neither the admin user nor the root user to ensure the script is incapable of causing too much damage. We'll use the `or` operator in this example, noted by `||`. This means that either of the conditions needs to be true. If we used the `and` operator of `&&` then both conditions would need to be true.
```bash
#!/bin/bash
admin="devdojo"
read -p "Enter your username? " username
# Check if the username provided is the admin
if [[ "${username}" != "${admin}" ]] || [[ $EUID != 0 ]] ; then
echo "You are not the admin or root user, but please be safe!"
else
echo "You are the admin user! This could be very destructive!"
fi
```
If you have multiple conditions and scenarios, then can use `elif` statement with `if` and `else` statements.
```bash
#!/bin/bash
read -p "Enter a number: " num
if [[ $num -gt 0 ]] ; then
echo "The number is positive"
elif [[ $num -lt 0 ]] ; then
echo "The number is negative"
else
echo "The number is 0"
fi
```
## Switch case statements
As in other programming languages, you can use a `case` statement to simplify complex conditionals when there are multiple different choices. So rather than using a few `if`, and `if-else` statements, you could use a single `case` statement.
The Bash `case` statement syntax looks like this:
```bash
case $some_variable in
pattern_1)
commands
;;
pattern_2| pattern_3)
commands
;;
*)
default commands
;;
esac
```
A quick rundown of the structure:
* All `case` statements start with the `case` keyword.
* On the same line as the `case` keyword, you need to specify a variable or an expression followed by the `in` keyword.
* After that, you have your `case` patterns, where you need to use `)` to identify the end of the pattern.
* You can specify multiple patterns divided by a pipe: `|`.
* After the pattern, you specify the commands that you would like to be executed in case that the pattern matches the variable or the expression that you've specified.
* All clauses have to be terminated by adding `;;` at the end.
* You can have a default statement by adding a `*` as the pattern.
* To close the `case` statement, use the `esac` (case typed backwards) keyword.
Here is an example of a Bash `case` statement:
```bash
#!/bin/bash
read -p "Enter the name of your car brand: " car
case $car in
Tesla)
echo -n "${car}'s car factory is in the USA."
;;
BMW | Mercedes | Audi | Porsche)
echo -n "${car}'s car factory is in Germany."
;;
Toyota | Mazda | Mitsubishi | Subaru)
echo -n "${car}'s car factory is in Japan."
;;
*)
echo -n "${car} is an unknown car brand"
;;
esac
```
With this script, we are asking the user to input a name of a car brand like Telsa, BMW, Mercedes and etc.
Then with a `case` statement, we check the brand name and if it matches any of our patterns, and if so, we print out the factory's location.
If the brand name does not match any of our `case` statements, we print out a default message: `an unknown car brand`.
## Conclusion
I would advise you to try and modify the script and play with it a bit so that you could practice what you've just learned in the last two chapters!
For more examples of Bash `case` statements, make sure to check chapter 16, where we would create an interactive menu in Bash using a `cases` statement to process the user input.

197
landing/docs/.Bash-Scripting/011-bash-loops.md
View File

@@ -1,197 +0,0 @@
# Bash Loops
As with any other language, loops are very convenient. With Bash you can use `for` loops, `while` loops, and `until` loops.
## For loops
Here is the structure of a for loop:
```bash
for var in ${list}
do
your_commands
done
```
Example:
```bash
#!/bin/bash
users="devdojo bobby tony"
for user in ${users}
do
echo "${user}"
done
```
A quick rundown of the example:
* First, we specify a list of users and store the value in a variable called `$users`.
* After that, we start our `for` loop with the `for` keyword.
* Then we define a new variable which would represent each item from the list that we give. In our case, we define a variable called `user`, which would represent each user from the `$users` variable.
* Then we specify the `in` keyword followed by our list that we will loop through.
* On the next line, we use the `do` keyword, which indicates what we will do for each iteration of the loop.
* Then we specify the commands that we want to run.
* Finally, we close the loop with the `done` keyword.
You can also use `for` to process a series of numbers. For example here is one way to loop through from 1 to 10:
```bash
#!/bin/bash
for num in {1..10}
do
echo ${num}
done
```
## While loops
The structure of a while loop is quite similar to the `for` loop:
```bash
while [ your_condition ]
do
your_commands
done
```
Here is an example of a `while` loop:
```bash
#!/bin/bash
counter=1
while [[ $counter -le 10 ]]
do
echo $counter
((counter++))
done
```
First, we specified a counter variable and set it to `1`, then inside the loop, we added counter by using this statement here: `((counter++))`. That way, we make sure that the loop will run 10 times only and would not run forever. The loop will complete as soon as the counter becomes 10, as this is what we've set as the condition: `while [[ $counter -le 10 ]]`.
Let's create a script that asks the user for their name and not allow an empty input:
```bash
#!/bin/bash
read -p "What is your name? " name
while [[ -z ${name} ]]
do
echo "Your name can not be blank. Please enter a valid name!"
read -p "Enter your name again? " name
done
echo "Hi there ${name}"
```
Now, if you run the above and just press enter without providing input, the loop would run again and ask you for your name again and again until you actually provide some input.
## Until Loops
The difference between `until` and `while` loops is that the `until` loop will run the commands within the loop until the condition becomes true.
Structure:
```bash
until [[ your_condition ]]
do
your_commands
done
```
Example:
```bash
#!/bin/bash
count=1
until [[ $count -gt 10 ]]
do
echo $count
((count++))
done
```
## Continue and Break
As with other languages, you can use `continue` and `break` with your bash scripts as well:
* `continue` tells your bash script to stop the current iteration of the loop and start the next iteration.
The syntax of the continue statement is as follows:
```bash
continue [n]
```
The [n] argument is optional and can be greater than or equal to 1. When [n] is given, the n-th enclosing loop is resumed. continue 1 is equivalent to continue.
```bash
#!/bin/bash
for i in 1 2 3 4 5
do
if [[ $i –eq 2 ]]
then
echo "skipping number 2"
continue
fi
echo "i is equal to $i"
done
```
We can also use continue command in similar way to break command for controlling multiple loops.
* `break` tells your bash script to end the loop straight away.
The syntax of the break statement takes the following form:
```bash
break [n]
```
[n] is an optional argument and must be greater than or equal to 1. When [n] is provided, the n-th enclosing loop is exited. break 1 is equivalent to break.
Example:
```bash
#!/bin/bash
num=1
while [[ $num –lt 10 ]]
do
if [[ $num –eq 5 ]]
then
break
fi
((num++))
done
echo "Loop completed"
```
We can also use break command with multiple loops. If we want to exit out of current working loop whether inner or outer loop, we simply use break but if we are in inner loop & want to exit out of outer loop, we use break 2.
Example:
```bash
#!/bin/bash
for (( a = 1; a < 10; a++ ))
do
echo "outer loop: $a"
for (( b = 1; b < 100; b++ ))
do
if [[ $b –gt 5 ]]
then
break 2
fi
echo "Inner loop: $b "
done
done
```
The bash script will begin with a=1 & will move to inner loop and when it reaches b=5, it will break the outer loop.
We can use break only instead of break 2, to break inner loop & see how it affects the output.

66
landing/docs/.Bash-Scripting/012-bash-functions.md
View File

@@ -1,66 +0,0 @@
# Bash Functions
Functions are a great way to reuse code. The structure of a function in bash is quite similar to most languages:
```bash
function function_name() {
your_commands
}
```
You can also omit the `function` keyword at the beginning, which would also work:
```bash
function_name() {
your_commands
}
```
I prefer putting it there for better readability. But it is a matter of personal preference.
Example of a "Hello World!" function:
```bash
#!/bin/bash
function hello() {
echo "Hello World Function!"
}
hello
```
>{notice} One thing to keep in mind is that you should not add the parenthesis when you call the function.
Passing arguments to a function work in the same way as passing arguments to a script:
```bash
#!/bin/bash
function hello() {
echo "Hello $1!"
}
hello DevDojo
```
Functions should have comments mentioning description, global variables, arguments, outputs, and returned values, if applicable
```bash
#######################################
# Description: Hello function
# Globals:
# None
# Arguments:
# Single input argument
# Outputs:
# Value of input argument
# Returns:
# 0 if successful, non-zero on error.
#######################################
function hello() {
echo "Hello $1!"
}
```
In the next few chapters we will be using functions a lot!

83
landing/docs/.Bash-Scripting/013-debugging-and-testing.md
View File

@@ -1,83 +0,0 @@
# Debugging, testing and shortcuts
In order to debug your bash scripts, you can use `-x` when executing your scripts:
```bash
bash -x ./your_script.sh
```
Or you can add `set -x` before the specific line that you want to debug, `set -x` enables a mode of the shell where all executed commands are printed to the terminal.
Another way to test your scripts is to use this fantastic tool here:
[https://www.shellcheck.net/](https://www.shellcheck.net/)
Just copy and paste your code into the textbox, and the tool will give you some suggestions on how you can improve your script.
You can also run the tool directly in your terminal:
[https://github.com/koalaman/shellcheck](https://github.com/koalaman/shellcheck)
If you like the tool, make sure to star it on GitHub and contribute!
As a SysAdmin/DevOps, I spend a lot of my day in the terminal. Here are my favorite shortcuts that help me do tasks quicker while writing Bash scripts or just while working in the terminal.
The below two are particularly useful if you have a very long command.
* Delete everything from the cursor to the end of the line:
```
Ctrl + k
```
* Delete everything from the cursor to the start of the line:
```
Ctrl + u
```
* Delete one word backward from cursor:
```
Ctrl + w
```
* Search your history backward. This is probably the one that I use the most. It is really handy and speeds up my work-flow a lot:
```
Ctrl + r
```
* Clear the screen, I use this instead of typing the `clear` command:
```
Ctrl + l
```
* Stops the output to the screen:
```
Ctrl + s
```
* Enable the output to the screen in case that previously stopped by `Ctrl + s`:
```
Ctrl + q
```
* Terminate the current command
```
Ctrl + c
```
* Throw the current command to background:
```
Ctrl + z
```
I use those regularly every day, and it saves me a lot of time.
If you think that I've missed any feel free to join the discussion on [the DigitalOcean community forum](https://www.digitalocean.com/community/questions/what-are-your-favorite-bash-shortcuts)!

83
landing/docs/.Bash-Scripting/014-creating-custom-bash-commands.md
View File

@@ -1,83 +0,0 @@
# Creating custom bash commands
As a developer or system administrator, you might have to spend a lot of time in your terminal. I always try to look for ways to optimize any repetitive tasks.
One way to do that is to either write short bash scripts or create custom commands also known as aliases. For example, rather than typing a really long command every time you could just create a shortcut for it.
## Example
Let's start with the following scenario, as a system admin, you might have to check the connections to your web server quite often, so I will use the `netstat` command as an example.
What I would usually do when I access a server that is having issues with the connections to port 80 or 443 is to check if there are any services listening on those ports and the number of connections to the ports.
The following `netstat` command would show us how many TCP connections on port 80 and 443 we currently have:
```bash
netstat -plant | grep '80\|443' | grep -v LISTEN | wc -l
```
This is quite a lengthy command so typing it every time might be time-consuming in the long run especially when you want to get that information quickly.
To avoid that, we can create an alias, so rather than typing the whole command, we could just type a short command instead. For example, lets say that we wanted to be able to type `conn` (short for connections) and get the same information. All we need to do in this case is to run the following command:
```bash
alias conn="netstat -plant | grep '80\|443' | grep -v LISTEN | wc -l"
```
That way we are creating an alias called `conn` which would essentially be a 'shortcut' for our long `netstat` command. Now if you run just `conn`:
```bash
conn
```
You would get the same output as the long `netstat` command.
You can get even more creative and add some info messages like this one here:
```bash
alias conn="echo 'Total connections on port 80 and 443:' ; netstat -plant | grep '80\|443' | grep -v LISTEN | wc -l"
```
Now if you run `conn` you would get the following output:
```bash
Total connections on port 80 and 443:
12
```
Now if you log out and log back in, your alias would be lost. In the next step you will see how to make this persistent.
## Making the change persistent
In order to make the change persistent, we need to add the `alias` command in our shell profile file.
By default on Ubuntu this would be the `~/.bashrc` file, for other operating systems this might be the `~/.bash_profle`. With your favorite text editor open the file:
```bash
nano ~/.bashrc
```
Go to the bottom and add the following:
```bash
alias conn="echo 'Total connections on port 80 and 443:' ; netstat -plant | grep '80\|443' | grep -v LISTEN | wc -l"
```
Save and then exit.
That way now even if you log out and log back in again your change would be persisted and you would be able to run your custom bash command.
## Listing all of the available aliases
To list all of the available aliases for your current shell, you have to just run the following command:
```bash
alias
```
This would be handy in case that you are seeing some weird behavior with some commands.
## Conclusion
This is one way of creating custom bash commands or bash aliases.
Of course, you could actually write a bash script and add the script inside your `/usr/bin` folder, but this would not work if you don't have root or sudo access, whereas with aliases you can do it without the need of root access.
>{notice} This was initially posted on [DevDojo.com](https://devdojo.com/bobbyiliev/how-to-create-custom-bash-commands)

180
landing/docs/.Bash-Scripting/015-writing-your-first-bash-script.md
View File

@@ -1,180 +0,0 @@
# Write your first Bash script
Let's try to put together what we've learned so far and create our first Bash script!
## Planning the script
As an example, we will write a script that would gather some useful information about our server like:
* Current Disk usage
* Current CPU usage
* Current RAM usage
* Check the exact Kernel version
Feel free to adjust the script by adding or removing functionality so that it matches your needs.
## Writing the script
The first thing that you need to do is to create a new file with a `.sh` extension. I will create a file called `status.sh` as the script that we will create would give us the status of our server.
Once you've created the file, open it with your favorite text editor.
As we've learned in chapter 1, on the very first line of our Bash script we need to specify the so-called [Shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)):
```bash
#!/bin/bash
```
All that the shebang does is to instruct the operating system to run the script with the /bin/bash executable.
## Adding comments
Next, as discussed in chapter 6, let's start by adding some comments so that people could easily figure out what the script is used for. To do that right after the shebang you can just add the following:
```bash
#!/bin/bash
# Script that returns the current server status
```
## Adding your first variable
Then let's go ahead and apply what we've learned in chapter 4 and add some variables which we might want to use throughout the script.
To assign a value to a variable in bash, you just have to use the `=` sign. For example, let's store the hostname of our server in a variable so that we could use it later:
```bash
server_name=$(hostname)
```
By using `$()` we tell bash to actually interpret the command and then assign the value to our variable.
Now if we were to echo out the variable we would see the current hostname:
```bash
echo $server_name
```
## Adding your first function
As you already know after reading chapter 12, in order to create a function in bash you need to use the following structure:
```bash
function function_name() {
your_commands
}
```
Let's create a function that returns the current memory usage on our server:
```bash
function memory_check() {
echo ""
echo "The current memory usage on ${server_name} is: "
free -h
echo ""
}
```
Quick run down of the function:
* `function memory_check() {` - this is how we define the function
* `echo ""` - here we just print a new line
* `echo "The current memory usage on ${server_name} is: "` - here we print a small message and the `$server_name` variable
* `}` - finally this is how we close the function
Then once the function has been defined, in order to call it, just use the name of the function:
```bash
# Define the function
function memory_check() {
echo ""
echo "The current memory usage on ${server_name} is: "
free -h
echo ""
}
# Call the function
memory_check
```
## Adding more functions challenge
Before checking out the solution, I would challenge you to use the function from above and write a few functions by yourself.
The functions should do the following:
* Current Disk usage
* Current CPU usage
* Current RAM usage
* Check the exact Kernel version
Feel free to use google if you are not sure what commands you need to use in order to get that information.
Once you are ready, feel free to scroll down and check how we've done it and compare the results!
Note that there are multiple correct ways of doing it!
## The sample script
Here's what the end result would look like:
```bash
#!/bin/bash
##
# BASH script that checks:
# - Memory usage
# - CPU load
# - Number of TCP connections
# - Kernel version
##
server_name=$(hostname)
function memory_check() {
echo ""
echo "Memory usage on ${server_name} is: "
free -h
echo ""
}
function cpu_check() {
echo ""
echo "CPU load on ${server_name} is: "
echo ""
uptime
echo ""
}
function tcp_check() {
echo ""
echo "TCP connections on ${server_name}: "
echo ""
cat /proc/net/tcp | wc -l
echo ""
}
function kernel_check() {
echo ""
echo "Kernel version on ${server_name} is: "
echo ""
uname -r
echo ""
}
function all_checks() {
memory_check
cpu_check
tcp_check
kernel_check
}
all_checks
```
## Conclusion
Bash scripting is awesome! No matter if you are a DevOps/SysOps engineer, developer, or just a Linux enthusiast, you can use Bash scripts to combine different Linux commands and automate boring and repetitive daily tasks, so that you can focus on more productive and fun things!
>{notice} This was initially posted on [DevDojo.com](https://devdojo.com/bobbyiliev/introduction-to-bash-scripting)

305
landing/docs/.Bash-Scripting/016-creating-an-interactive-menu-in-bash.md
View File

@@ -1,305 +0,0 @@
# Creating an interactive menu in Bash
In this tutorial, I will show you how to create a multiple-choice menu in Bash so that your users could choose between what action should be executed!
We would reuse some of the code from the previous chapter, so if you have not read it yet make sure to do so.
## Planning the functionality
Let's start again by going over the main functionality of the script:
* Checks the current Disk usage
* Checks the current CPU usage
* Checks the current RAM usage
* Checks the check the exact Kernel version
In case that you don't have it on hand, here is the script itself:
```bash
#!/bin/bash
##
# BASH menu script that checks:
# - Memory usage
# - CPU load
# - Number of TCP connections
# - Kernel version
##
server_name=$(hostname)
function memory_check() {
echo ""
echo "Memory usage on ${server_name} is: "
free -h
echo ""
}
function cpu_check() {
echo ""
echo "CPU load on ${server_name} is: "
echo ""
uptime
echo ""
}
function tcp_check() {
echo ""
echo "TCP connections on ${server_name}: "
echo ""
cat /proc/net/tcp | wc -l
echo ""
}
function kernel_check() {
echo ""
echo "Kernel version on ${server_name} is: "
echo ""
uname -r
echo ""
}
function all_checks() {
memory_check
cpu_check
tcp_check
kernel_check
}
```
We will then build a menu that allows the user to choose which function to be executed.
Of course, you can adjust the function or add new ones depending on your needs.
## Adding some colors
In order to make the menu a bit more 'readable' and easy to grasp at first glance, we will add some color functions.
At the beginning of your script add the following color functions:
```bash
##
# Color Variables
##
green='\e[32m'
blue='\e[34m'
clear='\e[0m'
##
# Color Functions
##
ColorGreen(){
echo -ne $green$1$clear
}
ColorBlue(){
echo -ne $blue$1$clear
}
```
You can use the color functions as follows:
```bash
echo -ne $(ColorBlue 'Some text here')
```
The above would output the `Some text here` string and it would be blue!
# Adding the menu
Finally, to add our menu, we will create a separate function with a case switch for our menu options:
```bash
menu(){
echo -ne "
My First Menu
$(ColorGreen '1)') Memory usage
$(ColorGreen '2)') CPU load
$(ColorGreen '3)') Number of TCP connections
$(ColorGreen '4)') Kernel version
$(ColorGreen '5)') Check All
$(ColorGreen '0)') Exit
$(ColorBlue 'Choose an option:') "
read a
case $a in
1) memory_check ; menu ;;
2) cpu_check ; menu ;;
3) tcp_check ; menu ;;
4) kernel_check ; menu ;;
5) all_checks ; menu ;;
0) exit 0 ;;
*) echo -e $red"Wrong option."$clear; WrongCommand;;
esac
}
```
### A quick rundown of the code
First we just echo out the menu options with some color:
```
echo -ne "
My First Menu
$(ColorGreen '1)') Memory usage
$(ColorGreen '2)') CPU load
$(ColorGreen '3)') Number of TCP connections
$(ColorGreen '4)') Kernel version
$(ColorGreen '5)') Check All
$(ColorGreen '0)') Exit
$(ColorBlue 'Choose an option:') "
```
Then we read the answer of the user and store it in a variable called `$a`:
```bash
read a
```
Finally, we have a switch case which triggers a different function depending on the value of `$a`:
```bash
case $a in
1) memory_check ; menu ;;
2) cpu_check ; menu ;;
3) tcp_check ; menu ;;
4) kernel_check ; menu ;;
5) all_checks ; menu ;;
0) exit 0 ;;
*) echo -e $red"Wrong option."$clear; WrongCommand;;
esac
```
At the end we need to call the menu function to actually print out the menu:
```bash
# Call the menu function
menu
```
## Testing the script
In the end, your script will look like this:
```bash
#!/bin/bash
##
# BASH menu script that checks:
# - Memory usage
# - CPU load
# - Number of TCP connections
# - Kernel version
##
server_name=$(hostname)
function memory_check() {
echo ""
echo "Memory usage on ${server_name} is: "
free -h
echo ""
}
function cpu_check() {
echo ""
echo "CPU load on ${server_name} is: "
echo ""
uptime
echo ""
}
function tcp_check() {
echo ""
echo "TCP connections on ${server_name}: "
echo ""
cat /proc/net/tcp | wc -l
echo ""
}
function kernel_check() {
echo ""
echo "Kernel version on ${server_name} is: "
echo ""
uname -r
echo ""
}
function all_checks() {
memory_check
cpu_check
tcp_check
kernel_check
}
##
# Color Variables
##
green='\e[32m'
blue='\e[34m'
clear='\e[0m'
##
# Color Functions
##
ColorGreen(){
echo -ne $green$1$clear
}
ColorBlue(){
echo -ne $blue$1$clear
}
menu(){
echo -ne "
My First Menu
$(ColorGreen '1)') Memory usage
$(ColorGreen '2)') CPU load
$(ColorGreen '3)') Number of TCP connections
$(ColorGreen '4)') Kernel version
$(ColorGreen '5)') Check All
$(ColorGreen '0)') Exit
$(ColorBlue 'Choose an option:') "
read a
case $a in
1) memory_check ; menu ;;
2) cpu_check ; menu ;;
3) tcp_check ; menu ;;
4) kernel_check ; menu ;;
5) all_checks ; menu ;;
0) exit 0 ;;
*) echo -e $red"Wrong option."$clear; WrongCommand;;
esac
}
# Call the menu function
menu
```
To test the script, create a new filed with a `.sh` extension, for example: `menu.sh` and then run it:
```bash
bash menu.sh
```
The output that you would get will look like this:
```bash
My First Menu
1) Memory usage
2) CPU load
3) Number of TCP connections
4) Kernel version
5) Check All
0) Exit
Choose an option:
```
You will be able to choose a different option from the list and each number will call a different function from the script:
![Nice Bash interactive menu](https://imgur.com/8EgxX4m.png)
## Conclusion
You now know how to create a Bash menu and implement it in your scripts so that users could select different values!
>{notice} This content was initially posted on [DevDojo.com](https://devdojo.com/bobbyiliev/how-to-work-with-json-in-bash-using-jq)

129
landing/docs/.Bash-Scripting/017-executing-bash-script-on-multiple-remote-server.md
View File

@@ -1,129 +0,0 @@
# Executing BASH scripts on Multiple Remote Servers
Any command that you can run from the command line can be used in a bash script. Scripts are used to run a series of commands. Bash is available by default on Linux and macOS operating systems.
Let's have a hypothetical scenario where you need to execute a BASH script on multiple remote servers, but you don't want to manually copy the script to each server, then again login to each server individually and only then execute the script.
Of course you could use a tool like Ansible but let's learn how to do that with Bash!
## Prerequisites
For this example I will use 3 remote Ubuntu servers deployed on DigitalOcean. If you don't have a Digital Ocean account yet, you can sign up for DigitalOcean and get $100 free credit via this referral link here:
[https://m.do.co/c/2a9bba940f39](https://m.do.co/c/2a9bba940f39)
Once you have your Digital Ocean account ready go ahead and deploy 3 droplets.
I've gone ahead and created 3 Ubuntu servers:
![DigitalOcean Ubuntu servers](https://imgur.com/09xmq41.png)
I'll put a those servers IP's in a `servers.txt` file which I would use to loop though with our Bash script.
If you are new to DigitalOcean you can follow the steps on how to create a Droplet here:
* [How to Create a Droplet from the DigitalOcean Control Panel](https://www.digitalocean.com/docs/droplets/how-to/create/)
You can also follow the steps from this video here on how to do your initial server setup:
* [How to do your Initial Server Setup with Ubuntu](https://youtu.be/7NL2_4HIgKU)
Or even better, you can follow this article here on how to automate your initial server setup with Bash:
[Automating Initial Server Setup with Ubuntu 18.04 with Bash](https://www.digitalocean.com/community/tutorials/automating-initial-server-setup-with-ubuntu-18-04)
With the 3 new servers in place, we can go ahead and focus on running our Bash script on all of them with a single command!
## The BASH Script
I will reuse the demo script from the previous chapter with some slight changes. It simply executes a few checks like the current memory usage, the current CPU usage, the number of TCP connections and the version of the kernel.
```bash
#!/bin/bash
##
# BASH script that checks the following:
# - Memory usage
# - CPU load
# - Number of TCP connections
# - Kernel version
##
##
# Memory check
##
server_name=$(hostname)
function memory_check() {
echo "#######"
echo "The current memory usage on ${server_name} is: "
free -h
echo "#######"
}
function cpu_check() {
echo "#######"
echo "The current CPU load on ${server_name} is: "
echo ""
uptime
echo "#######"
}
function tcp_check() {
echo "#######"
echo "Total TCP connections on ${server_name}: "
echo ""
cat /proc/net/tcp | wc -l
echo "#######"
}
function kernel_check() {
echo "#######"
echo "The exact Kernel version on ${server_name} is: "
echo ""
uname -r
echo "#######"
}
function all_checks() {
memory_check
cpu_check
tcp_check
kernel_check
}
all_checks
```
Copy the code bellow and add this in a file called `remote_check.sh`. You can also get the script from [here](https://devdojo.com/bobbyiliev/executing-bash-script-on-multiple-remote-server).
## Running the Script on all Servers
Now that we have the script and the servers ready and that we've added those servers in our servers.txt file we can run the following command to loop though all servers and execute the script remotely without having to copy the script to each server and individually connect to each server.
```bash
for server in $(cat servers.txt) ; do ssh your_user@${server} 'bash -s' < ./remote_check.sh ; done
```
What this for loop does is, it goes through each server in the servers.txt file and then it runs the following command for each item in the list:
```bash
ssh your_user@the_server_ip 'bash -s' < ./remote_check.sh
```
You would get the following output:
![Running bash script on multiple remote servers](https://imgur.com/B1AmhUP.png)
## Conclusion
This is just a really simple example on how to execute a simple script on multiple servers without having to copy the script to each server and without having to access the servers individually.
Of course you could run a much more complex script and on many more servers.
If you are interested in automation, I would recommend checking out the Ansible resources page on the DigitalOcean website:
[Ansible Resources](https://www.digitalocean.com/community/tags/ansible)
>{notice} This content was initially posted on [DevDojo](https://devdojo.com/bobbyiliev/bash-script-to-summarize-your-nginx-and-apache-access-logs)

225
landing/docs/.Bash-Scripting/018-working-with-json-in-bash-using-jq.md
View File

@@ -1,225 +0,0 @@
# Work with JSON in BASH using jq
The `jq` command-line tool is a lightweight and flexible command-line **JSON** processor. It is great for parsing JSON output in BASH.
One of the great things about `jq` is that it is written in portable C, and it has zero runtime dependencies. All you need to do is to download a single binary or use a package manager like apt and install it with a single command.
## Planning the script
For the demo in this tutorial, I would use an external REST API that returns a simple JSON output called the [QuizAPI](https://quizapi.io/):
> [https://quizapi.io/](https://quizapi.io/)
If you want to follow along make sure to get a free API key here:
> [https://quizapi.io/clientarea/settings/token](https://quizapi.io/clientarea/settings/token)
The QuizAPI is free for developers.
## Installing jq
There are many ways to install `jq` on your system. One of the most straight forward ways to do so is to use the package manager depending on your OS.
Here is a list of the commands that you would need to use depending on your OS:
* Install jq on Ubuntu/Debian:
```bash
sudo apt-get install jq
```
* Install jq on Fedora:
```bash
sudo dnf install jq
```
* Install jq on openSUSE:
```bash
sudo zypper install jq
```
- Install jq on Arch:
```bash
sudo pacman -S jq
```
* Installing on Mac with Homebrew:
```bash
brew install jq
```
* Install on Mac with MacPort:
```bash
port install jq
```
If you are using other OS, I would recommend taking a look at the official documentation here for more information:
> [https://stedolan.github.io/jq/download/](https://stedolan.github.io/jq/download/)
Once you have jq installed you can check your current version by running this command:
```bash
jq --version
```
## Parsing JSON with jq
Once you have `jq` installed and your QuizAPI API Key, you can parse the JSON output of the QuizAPI directly in your terminal.
First, create a variable that stores your API Key:
```bash
API_KEY=YOUR_API_KEY_HERE
```
In order to get some output from one of the endpoints of the QuizAPI you can use the curl command:
```bash
curl "https://quizapi.io/api/v1/questions?apiKey=${API_KEY}&limit=10"
```
For a more specific output, you can use the QuizAPI URL Generator here:
> [https://quizapi.io/api-config](https://quizapi.io/api-config)
After running the curl command, the output which you would get would look like this:
![Raw Json output](https://imgur.com/KghOfzj.png)
This could be quite hard to read, but thanks to the jq command-line tool, all we need to do is pipe the curl command to jq and we would see a nice formatted JSON output:
```bash
curl "https://quizapi.io/api/v1/questions?apiKey=${API_KEY}&limit=10" | jq
```
> Note the `| jq` at the end.
In this case the output that you would get would look something like this:
![bash jq formatting](https://imgur.com/ebdTtVf.png)
Now, this looks much nicer! The jq command-line tool formatted the output for us and added some nice coloring!
## Getting the first element with jq
Let's say that we only wanted to get the first element from the JSON output, in order to do that we have to just specify the index that we want to see with the following syntax:
```bash
jq .[0]
```
Now, if we run the curl command again and pipe the output to jq .[0] like this:
```bash
curl "https://quizapi.io/api/v1/questions?apiKey=${API_KEY}&limit=10" | jq.[0]
```
You will only get the first element and the output will look like this:
![jq get first element only](https://imgur.com/h9bFMAL.png)
## Getting a value only for specific key
Sometimes you might want to get only the value of a specific key only, let's say in our example the QuizAPI returns a list of questions along with the answers, description and etc. but what if you wanted to get the Questions only without the additional information?
This is going to be quite straight forward with `jq`, all you need to do is add the key after jq command, so it would look something like this:
```bash
jq .[].question
```
We have to add the `.[]` as the QuizAPI returns an array and by specifying `.[]` we tell jq that we want to get the .question value for all of the elements in the array.
The output that you would get would look like this:
![jq get a value only for specific key](https://imgur.com/0701wHD.png)
As you can see we now only get the questions without the rest of the values.
## Using jq in a BASH script
Let's go ahead and create a small bash script which should output the following information for us:
* Get only the first question from the output
* Get all of the answers for that question
* Assign the answers to variables
* Print the question and the answers
* To do that I've put together the following script:
>{notice} make sure to change the API_KEY part with your actual QuizAPI key:
```bash
#!/bin/bash
##
# Make an API call to QuizAPI and store the output in a variable
##
output=$(curl 'https://quizapi.io/api/v1/questions?apiKey=API_KEY&limit=10' 2>/dev/null)
##
# Get only the first question
##
output=$(echo $output | jq .[0])
##
# Get the question
##
question=$(echo $output | jq .question)
##
# Get the answers
##
answer_a=$(echo $output | jq .answers.answer_a)
answer_b=$(echo $output | jq .answers.answer_b)
answer_c=$(echo $output | jq .answers.answer_c)
answer_d=$(echo $output | jq .answers.answer_d)
##
# Output the question
##
echo "
Question: ${question}
A) ${answer_a}
B) ${answer_b}
C) ${answer_c}
D) ${answer_d}
"
```
If you run the script you would get the following output:
![Using jq in a bash script](https://imgur.com/LKEsrbq.png)
We can even go further by making this interactive so that we could actually choose the answer directly in our terminal.
There is already a bash script that does this by using the QuizAPI and `jq`:
You can take a look at that script here:
* [https://github.com/QuizApi/QuizAPI-BASH/blob/master/quiz.sh](https://github.com/QuizApi/QuizAPI-BASH/blob/master/quiz.sh)
## Conclusion
The `jq` command-line tool is an amazing tool that gives you the power to work with JSON directly in your BASH terminal.
That way you can easily interact with all kinds of different REST APIs with BASH.
For more information, you could take a look at the official documentation here:
* [https://stedolan.github.io/jq/manual/](https://stedolan.github.io/jq/manual/)
And for more information on the **QuizAPI**, you could take a look at the official documentation here:
* [https://quizapi.io/docs/1.0/overview](https://quizapi.io/docs/1.0/overview)
>{notice} This content was initially posted on [DevDojo.com](https://devdojo.com/bobbyiliev/how-to-work-with-json-in-bash-using-jq)

104
landing/docs/.Bash-Scripting/019-working-with-cloudflare-api-with-bash.md
View File

@@ -1,104 +0,0 @@
# Working with Cloudflare API with Bash
I host all of my websites on **DigitalOcean** Droplets and I also use Cloudflare as my CDN provider. One of the benefits of using Cloudflare is that it reduces the overall traffic to your user and also hides your actual server IP address behind their CDN.
My personal favorite Cloudflare feature is their free DDoS protection. It has saved my servers multiple times from different DDoS attacks. They have a cool API that you could use to enable and disable their DDoS protection easily.
This chapter is going to be an exercise! I challenge you to go ahead and write a short bash script that would enable and disable the Cloudflare DDoS protection for your server automatically if needed!
## Prerequisites
Before following this guide here, please set up your Cloudflare account and get your website ready. If you are not sure how to do that you can follow these steps here: [Create a Cloudflare account and add a website](https://support.cloudflare.com/hc/en-us/articles/201720164-Step-2-Create-a-Cloudflare-account-and-add-a-website).
Once you have your Cloudflare account, make sure to obtain the following information:
* A Cloudflare account
* Cloudflare API key
* Cloudflare Zone ID
Also, Make sure curl is installed on your server:
```bash
curl --version
```
If curl is not installed you need to run the following:
* For RedHat/CentOs:
```bash
yum install curl
```
* For Debian/Ubuntu
```bash
apt-get install curl
```
## Challenge - Script requirements
The script needs to monitor the CPU usage on your server and if the CPU usage gets high based on the number vCPU it would enable the Cloudflare DDoS protection automatically via the Cloudflare API.
The main features of the script should be:
* Checks the script CPU load on the server
* In case of a CPU spike the script triggers an API call to Cloudflare and enables the DDoS protection feature for the specified zone
* After the CPU load is back to normal the script would disable the "I'm under attack" option and set it back to normal
## Example script
I already have prepared a demo script which you could use as a reference. But I encourage you to try and write the script yourself first and only then take a look at my script!
To download the script just run the following command:
```bash
wget https://raw.githubusercontent.com/bobbyiliev/cloudflare-ddos-protection/main/protection.sh
```
Open the script with your favorite text editor:
```bash
nano protection.sh
```
And update the following details with your Cloudflare details:
```bash
CF_CONE_ID=YOUR_CF_ZONE_ID
CF_EMAIL_ADDRESS=YOUR_CF_EMAIL_ADDRESS
CF_API_KEY=YOUR_CF_API_KEY
```
After that make the script executable:
```bash
chmod +x ~/protection.sh
```
Finally, set up 2 Cron jobs to run every 30 seconds. To edit your crontab run:
```bash
crontab -e
```
And add the following content:
```bash
* * * * * /path-to-the-script/cloudflare/protection.sh
* * * * * ( sleep 30 ; /path-to-the-script/cloudflare/protection.sh )
```
Note that you need to change the path to the script with the actual path where you've stored the script at.
## Conclusion
This is quite straight forward and budget solution, one of the downsides of the script is that if your server gets unresponsive due to an attack, the script might not be triggered at all.
Of course, a better approach would be to use a monitoring system like Nagios and based on the statistics from the monitoring system then you can trigger the script, but this script challenge could be a good learning experience!
Here is another great resource on how to use the Discord API and send notifications to your Discord Channel with a Bash script:
[How To Use Discord Webhooks to Get Notifications for Your Website Status on Ubuntu 18.04](https://www.digitalocean.com/community/tutorials/how-to-use-discord-webhooks-to-get-notifications-for-your-website-status-on-ubuntu-18-04)
>{notice} This content was initially posted on [DevDojo](https://devdojo.com/bobbyiliev/bash-script-to-automatically-enable-cloudflare-ddos-protection)

83
landing/docs/.Bash-Scripting/020-nginx-and-apache-log-parser.md
View File

@@ -1,83 +0,0 @@
# BASH Script parser to Summarize Your NGINX and Apache Access Logs
One of the first things that I would usually do in case I notice a high CPU usage on some of my Linux servers would be to check the process list with either top or htop and in case that I notice a lot of Apache or Nginx process I would quickly check my access logs to determine what has caused or is causing the CPU spike on my server or to figure out if anything malicious is going on.
Sometimes reading the logs could be quite intimidating as the log might be huge and going though it manually could take a lot of time. Also, the raw log format could be confusing for people with less experience.
Just like the previous chapter, this chapter is going to be a challenge! You need to write a short bash script that would summarize the whole access log for you without the need of installing any additional software.
# Script requirements
This BASH script needs to parse and summarize your access logs and provide you with very useful information like:
* The 20 top pages with the most POST requests
* The 20 top pages with the most GET requests
* Top 20 IP addresses and their geo-location
## Example script
I already have prepared a demo script which you could use as a reference. But I encourage you to try and write the script yourself first and only then take a look at my script!
In order to download the script, you can either clone the repository with the following command:
```bash
git clone https://github.com/bobbyiliev/quick_access_logs_summary.git
```
Or run the following command which would download the script in your current directory:
```bash
wget https://raw.githubusercontent.com/bobbyiliev/quick_access_logs_summary/master/spike_check
```
The script does not make any changes to your system, it only reads the content of your access log and summarizes it for you, however, once you've downloaded the file, make sure to review the content yourself.
## Running the script
All that you have to do once the script has been downloaded is to make it executable and run it.
To do that run the following command to make the script executable:
```bash
chmod +x spike_check
```
Then run the script:
```bash
./spike_check /path/to/your/access_log
```
Make sure to change the path to the file with the actual path to your access log. For example if you are using Apache on an Ubuntu server, the exact command would look like this:
```bash
./spike_check /var/log/apache2/access.log
```
If you are using Nginx the exact command would be almost the same, but with the path to the Nginx access log:
```bash
./spike_check /var/log/nginx/access.log
```
## Understanding the output
Once you run the script, it might take a while depending on the size of the log.
The output that you would see should look like this:
![Summarized access log](https://imgur.com/WWHVMrj.png)
Essentially what we can tell in this case is that we've received 16 POST requests to our xmlrpc.php file which is often used by attackers to try and exploit WordPress websites by using various username and password combinations.
In this specific case, this was not a huge brute force attack, but it gives us an early indication and we can take action to prevent a larger attack in the future.
We can also see that there were a couple of Russian IP addresses accessing our site, so in case that you do not expect any traffic from Russia, you might want to block those IP addresses as well.
## Conclusion
This is an example of a simple BASH script that allows you to quickly summarize your access logs and determine if anything malicious is going on.
Of course, you might want to also manually go through the logs as well but it is a good challenge to try and automate this with Bash!
>{notice} This content was initially posted on [DevDojo](https://devdojo.com/bobbyiliev/bash-script-to-summarize-your-nginx-and-apache-access-logs)

95
landing/docs/.Bash-Scripting/021-how-to-send-emails-with-bash.md
View File

@@ -1,95 +0,0 @@
# Sending emails with Bash and SSMTP
SSMTP is a tool that delivers emails from a computer or a server to a configured mail host.
SSMTP is not an email server itself and does not receive emails or manage a queue.
One of its primary uses is for forwarding automated email (like system alerts) off your machine and to an external email address.
## Prerequisites
You would need the following things in order to be able to complete this tutorial successfully:
* Access to an Ubuntu 18.04 server as a non-root user with sudo privileges and an active firewall installed on your server. To set these up, please refer to our [Initial Server Setup Guide for Ubuntu 18.04](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-18-04)
* An SMTP server along with SMTP username and password, this would also work with Gmail's SMTP server, or you could set up your own SMTP server by following the steps from this tutorial on [How to Install and Configure Postfix as a Send-Only SMTP Server on Ubuntu 16.04](https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-postfix-as-a-send-only-smtp-server-on-ubuntu-16-04)
## Installing SSMTP
In order to install SSMTP, you’ll need to first update your apt cache with:
```bash
sudo apt update
```
Then run the following command to install SSMTP:
```bash
sudo apt install ssmtp
```
Another thing that you would need to install is `mailutils`, to do that run the following command:
```bash
sudo apt install mailutils
```
## Configuring SSMTP
Now that you have `ssmtp` installed, in order to configure it to use your SMTP server when sending emails, you need to edit the SSMTP configuration file.
Using your favourite text editor to open the `/etc/ssmtp/ssmtp.conf` file:
```bash
sudo nano /etc/ssmtp/ssmtp.conf
```
You need to include your SMTP configuration:
```
root=postmaster
mailhub=<^>your_smtp_host.com<^>:587
hostname=<^>your_hostname<^>
AuthUser=<^>your_gmail_username@your_smtp_host.com<^>
AuthPass=<^>your_gmail_password<^>
FromLineOverride=YES
UseSTARTTLS=YES
```
Save the file and exit.
## Sending emails with SSMTP
Once your configuration is done, in order to send an email just run the following command:
```bash
echo "<^>Here add your email body<^>" | mail -s "<^>Here specify your email subject<^>" <^>your_recepient_email@yourdomain.com<^>
```
You can run this directly in your terminal or include it in your bash scripts.
## Sending A File with SSMTP (optional)
If you need to send files as attachments, you can use `mpack`.
To install `mpack` run the following command:
```bash
sudo apt install mpack
```
Next, in order to send an email with a file attached, run the following command.
```bash
mpack -s "<^>Your Subject here<^>" your_file.zip <^>your_recepient_email@yourdomain.com<^>
```
The above command would send an email to `<^>your_recepient_email@yourdomain.com<^>` with the `<^>your_file.zip<^>` attached.
## Conclusion
SSMTP is a great and reliable way to implement SMTP email functionality directly in bash scripts.
For more information about SSMTP I would recommend checking the official documentation [here](https://wiki.archlinux.org/index.php/SSMTP).
>{notice} This content was initially posted on the [DigitalOcean community forum](https://www.digitalocean.com/community/questions/how-to-send-emails-from-a-bash-script-using-ssmtp).

126
landing/docs/.Bash-Scripting/022-bash-password-generator.md
View File

@@ -1,126 +0,0 @@
# Password Generator Bash Script
It's not uncommon situation where you will need to generate a random password that you can use for any software installation or when you sign-up to any website.
There are a lot of options in order to achieve this. You can use a password manager/vault where you often have the option to randomly generate a password or to use a website that can generate the password on your behalf.
You can also use Bash in your terminal (command-line) to generate a password that you can quickly use. There are a lot of ways to achieve that and I will make sure to cover few of them and will leave up to you to choose which option is most suitable with your needs.
## :warning: Security
**This script is intended to practice your bash scripting skills. You can have fun while doing simple projects with BASH, but security is not a joke, so please make sure you do not save your passwords in plain text in a local file or write them down by hand on a piece of paper.**
**I will highly recommend everyone to use secure and trusted providers to generate and save the passwords.**
## Script summary
Let me first do a quick summary of what our script is going to do.:
1. We will have to option to choose the password characters length when the script is executed.
2. The script will then generate 5 random passwords with the length that was specified in step 1
## Prerequisites
You would need a bash terminal and a text editor. You can use any text editor like vi, vim, nano or Visual Studio Code.
I'm running the script locally on my Linux laptop but if you're using Windows PC you can ssh to any server of your choice and execute the script there.
Although the script is pretty simple, having some basic BASH scripting knowledge will help you to better understand the script and how it's working.
## Generate a random password
One of the great benefits of Linux is that you can do a lot of things using different methods. When it comes to generating a random string of characters it's not different as well.
You can use several commands in order to generate a random string of characters. I will cover few of them and will provide some examples.
- Using the ```date``` command.
The date command will output the current date and time. However we also further manipulate the output in order to use it as randomly generated password. We can hash the date using md5, sha or just run it through base64. These are few examples:
```
date | md5sum
94cb1cdecfed0699e2d98acd9a7b8f6d -
```
using sha256sum:
```
date | sha256sum
30a0c6091e194c8c7785f0d7bb6e1eac9b76c0528f02213d1b6a5fbcc76ceff4 -
```
using base64:
```
date | base64
0YHQsSDRj9C90YMgMzAgMTk6NTE6NDggRUVUIDIwMjEK
```
- We can also use openssl in order to generate pseudo-random bytes and run the output through base64. An example output will be:
```
openssl rand -base64 10
9+soM9bt8mhdcw==
```
Keep in mind that openssl might not be installed on your system so it's likely that you will need to install it first in order to use it.
- The most preferred way is to use the pseudorandom number generator - /dev/urandom
since it is intended for most cryptographic purposes. We would also need to manipulate the output using ```tr``` in order to translate it. An example command is:
```
tr -cd '[:alnum:]' < /dev/urandom | fold -w10 | head -n 1
```
With this command we take the output from /dev/urandom and translate it with ```tr``` while using all letters and digits and print the desired number of characters.
## The script
First we begin the script with the shebang. We use it to tell the operating system which interpreter to use to parse the rest of the file.
```
#!/bin/bash
```
We can then continue and ask the user for some input. In this case we would like to know how many characters the password needs to be:
```
# Ask user for password length
clear
printf "\n"
read -p "How many characters you would like the password to have? " pass_length
printf "\n"
```
Generate the passwords and then print it so the user can use it.
```
# This is where the magic happens!
# Generate a list of 10 strings and cut it to the desired value provided from the user
for i in {1..10}; do (tr -cd '[:alnum:]' < /dev/urandom | fold -w${pass_length} | head -n 1); done
# Print the strings
printf "$pass_output\n"
printf "Goodbye, ${USER}\n"
```
## The full script:
```
#!/bin/bash
#=======================================
# Password generator with login option
#=======================================
# Ask user for the string length
clear
printf "\n"
read -p "How many characters you would like the password to have? " pass_length
printf "\n"
# This is where the magic happens!
# Generate a list of 10 strings and cut it to the desired value provided from the user
for i in {1..10}; do (tr -cd '[:alnum:]' < /dev/urandom | fold -w${pass_length} | head -n 1); done
# Print the strings
printf "$pass_output\n"
printf "Goodbye, ${USER}\n"
```
## Conclusion
This is pretty much how you can use simple bash script to generate random passwords.
:warning: **As already mentioned, please make sure to use strong passwords in order to make sure your account is protected. Also whenever is possible use 2 factor authentication as this will provide additional layer of security for your account.**
While the script is working fine, it expects that the user will provide the requested input. In order to prevent any issues you would need to do some more advance checks on the user input in order to make sure the script will continue to work fine even if the provided input does not match our needs.
## Contributed by
[Alex Georgiev](https://twitter.com/alexgeorgiev17)

228
landing/docs/.Bash-Scripting/023-bash-redirection.md
View File

@@ -1,228 +0,0 @@
# Redirection in Bash
A Linux superuser must have a good knowledge of pipes and redirection in Bash. It is an essential component of the system and is often helpful in the field of Linux System Administration.
When you run a command like ``ls``, ``cat``, etc, you get some output on the terminal. If you write a wrong command, pass a wrong flag or a wrong command-line argument, you get error output on the terminal.
In both the cases, you are given some text. It may seem like "just text" to you, but the system treats this text differently. This identifier is known as a File Descriptor (fd).
In Linux, there are 3 File Descriptors, **STDIN** (0); **STDOUT** (1) and **STDERR** (2).
* **STDIN** (fd: 0): Manages the input in the terminal.
* **STDOUT** (fd: 1): Manages the output text in the terminal.
* **STDERR** (fd: 2): Manages the error text in the terminal.
# Difference between Pipes and Redirections
Both *pipes* and *redidertions* redirect streams `(file descriptor)` of process being executed. The main difference is that *redirections* deal with `files stream`, sending the output stream to a file or sending the content of a given file to the input stream of the process.
On the other hand a pipe connects two commands by sending the output stream of the first one to the input stream of the second one. without any redidertions specified.
# Redirection in Bash
## STDIN (Standard Input)
When you enter some input text for a command that asks for it, you are actually entering the text to the **STDIN** file descriptor. Run the ``cat`` command without any command-line arguments.
It may seem that the process has paused but in fact it's ``cat`` asking for **STDIN**. ``cat`` is a simple program and will print the text passed to **STDIN**. However, you can extend the use case by redirecting the input to the commands that take **STDIN**.
Example with ``cat``:
```
cat << EOF
Hello World!
How are you?
EOF
```
This will simply print the provided text on the terminal screen:
```
Hello World!
How are you?
```
The same can be done with other commands that take input via STDIN. Like, ``wc``:
```
wc -l << EOF
Hello World!
How are you?
EOF
```
The ``-l`` flag with ``wc`` counts the number of lines.
This block of bash code will print the number of lines to the terminal screen:
```
2
```
## STDOUT (Standard Output)
The normal non-error text on your terminal screen is printed via the **STDOUT** file descriptor. The **STDOUT** of a command can be redirected into a file, in such a way that the output of the command is written to a file instead of being printed on the terminal screen.
This is done simply with the help of ``>`` and ``>>`` operators.
Example:
```
echo "Hello World!" > file.txt
```
The above command will not print "Hello World" on the terminal screen, it will instead create a file called ``file.txt`` and will write the "Hello World" string to it.
This can be verified by running the ``cat`` command on the ``file.txt`` file.
```
cat file.txt
```
However, everytime you redirect the **STDOUT** of any command multiple times to the same file, it will remove the existing contents of the file to write the new ones.
Example:
```
echo "Hello World!" > file.txt
echo "How are you?" > file.txt
```
On running ``cat`` on ``file.txt`` file:
```
cat file.txt
```
You will only get the "How are you?" string printed.
```
How are you?
```
This is because the "Hello World" string has been overwritten.
This behaviour can be avoided using the ``>>`` operator.
The above example can be written as:
```
echo "Hello World!" > file.txt
echo "How are you?" >> file.txt
```
On running ``cat`` on the ``file.txt`` file, you will get the desired result.
```
Hello World!
How are you?
```
Alternatively, the redirection operator for **STDOUT** can also be written as ``1>``. Like,
```
echo "Hello World!" 1> file.txt
```
## STDERR (Standard Error)
The error text on the terminal screen is printed via the **STDERR** of the command. For example:
```
ls --hello
```
would give an error messages. This error message is the **STDERR** of the command.
**STDERR** can be redirected using the ``2>`` operator.
```
ls --hello 2> error.txt
```
This command will redirect the error message to the ``error.txt`` file and write it to it. This can be verified by running the ``cat`` command on the ``error.txt`` file.
You can also use the ``2>>`` operator for **STDERR** just like you used ``>>`` for **STDOUT**.
Error messages in Bash Scripts can be undesirable sometimes. You can choose to ignore them by redirecting the error message to the ``/dev/null`` file.
``/dev/null`` is pseudo-device that takes in text and then immediately discards it.
The above example can be written follows to ignore the error text completely:
```
ls --hello 2> /dev/null
```
Of course, you can redirect both **STDOUT** and **STDERR** for the same command or script.
```
./install_package.sh > output.txt 2> error.txt
```
Both of them can be redirected to the same file as well.
```
./install_package.sh > file.txt 2> file.txt
```
There is also a shorter way to do this.
```
./install_package.sh > file.txt 2>&1
```
# Piping
So far we have seen how to redirect the **STDOUT**, **STDIN** and **STDOUT** to and from a file.
To concatenate the output of program *(command)* as the input of another program *(command)* you can use a vertical bar `|`.
Example:
```
ls | grep ".txt"
```
This command will list the files in the current directory and pass output to *`grep`* command which then filter the output to only show the files that contain the string ".txt".
Syntax:
```
[time [-p]] [!] command1 [ | or |& command2 ] …
```
You can also build arbitrary chains of commands by piping them together to achieve a powerful result.
This example creates a listing of every user which owns a file in a given directory as well as how many files and directories they own:
```
ls -l /projects/bash_scripts | tail -n +2 | sed 's/\s\s*/ /g' | cut -d ' ' -f 3 | sort | uniq -c
```
Output:
```
8 anne
34 harry
37 tina
18 ryan
```
# HereDocument
The symbol `<<` can be used to create a temporary file [heredoc] and redirect from it at the command line.
```
COMMAND << EOF
ContentOfDocument
...
...
EOF
```
Note here that `EOF` represents the delimiter (end of file) of the heredoc. In fact, we can use any alphanumeric word in its place to signify the start and the end of the file. For instance, this is a valid heredoc:
```
cat << randomword1
This script will print these lines on the terminal.
Note that cat can read from standard input. Using this heredoc, we can
create a temporary file with these lines as it's content and pipe that
into cat.
randomword1
```
Effectively it will appear as if the contents of the heredoc are piped into the command. This can make the script very clean if multiple lines need to be piped into a program.
Further, we can attach more pipes as shown:
```
cat << randomword1 | wc
This script will print these lines on the terminal.
Note that cat can read from standard input. Using this heredoc, we can
create a temporary file with these lines as it's content and pipe that
into cat.
randomword1
```
Also, pre-defined variables can be used inside the heredocs.
# HereString
Herestrings are quite similar to heredocs but use `<<<`. These are used for single line strings that have to be piped into some program. This looks cleaner that heredocs as we don't have to specify the delimiter.
```
wc <<<"this is an easy way of passing strings to the stdin of a program (here wc)"
```
Just like heredocs, herestrings can contain variables.
## Summary
|**Operator** |**Description** |
|:---|:---|
|`>`|`Save output to a file`|
|`>>`|`Append output to a file`|
|`<`|`Read input from a file`|
|`2>`|`Redirect error messages`|
|`\|`|`Send the output from one program as input to another program`|
|`<<`|`Pipe multiple lines into a program cleanly`|
|`<<<`|`Pipe a single line into a program cleanly`|

336
landing/docs/.Bash-Scripting/024-automating-wordpress-lamp-with-bash.md
View File

@@ -1,336 +0,0 @@
# Automatic WordPress on LAMP installation with BASH
Here is an example of a full LAMP and WordPress installation that works on any Debian-based machine.
# Prerequisites
- A Debian-based machine (Ubuntu, Debian, Linux Mint, etc.)
# Planning the functionality
Let's start again by going over the main functionality of the script:
**Lamp Installation**
* Update the package manager
* Install a firewall (ufw)
* Allow SSH, HTTP and HTTPS traffic
* Install Apache2
* Install & Configure MariaDB
* Install PHP and required plugins
* Enable all required Apache2 mods
**Apache Virtual Host Setup**
* Create a directory in `/var/www`
* Configure permissions to the directory
* Create the `$domain` file under `/etc/apache2/sites-available` and append the required Virtualhost content
* Enable the site
* Restart Apache2
**SSL Config**
* Generate the OpenSSL certificate
* Append the SSL certificate to the `ssl-params.conf` file
* Append the SSL config to the Virtualhost file
* Enable SSL
* Reload Apache2
**Database Config**
* Create a database
* Create a user
* Flush Privileges
**WordPress Config**
* Install required WordPress PHP plugins
* Install WordPress
* Append the required information to `wp-config.php` file
Without further ado, let's start writing the script.
# The script
We start by setting our variables and asking the user to input their domain:
```bash
echo 'Please enter your domain of preference without www:'
read DOMAIN
echo "Please enter your Database username:"
read DBUSERNAME
echo "Please enter your Database password:"
read DBPASSWORD
echo "Please enter your Database name:"
read DBNAME
ip=`hostname -I | cut -f1 -d' '`
```
We are now ready to start writing our functions. Start by creating the `lamp_install()` function. Inside of it, we are going to update the system, install ufw, allow SSH, HTTP and HTTPS traffic, install Apache2, install MariaDB and PHP. We are also going to enable all required Apache2 mods.
```bash
lamp_install () {
apt update -y
apt install ufw
ufw enable
ufw allow OpenSSH
ufw allow in "WWW Full"
apt install apache2 -y
apt install mariadb-server
mysql_secure_installation -y
apt install php libapache2-mod-php php-mysql -y
sed -i "2d" /etc/apache2/mods-enabled/dir.conf
sed -i "2i\\\tDirectoryIndex index.php index.html index.cgi index.pl index.xhtml index.htm" /etc/apache2/mods-enabled/dir.conf
systemctl reload apache2
}
```
Next, we are going to create the `apache_virtualhost_setup()` function. Inside of it, we are going to create a directory in `/var/www`, configure permissions to the directory, create the `$domain` file under `/etc/apache2/sites-available` and append the required Virtualhost content, enable the site and restart Apache2.
```bash
apache_virtual_host_setup () {
mkdir /var/www/$DOMAIN
chown -R $USER:$USER /var/www/$DOMAIN
echo "<VirtualHost *:80>" >> /etc/apache2/sites-available/$DOMAIN.conf
echo -e "\tServerName $DOMAIN" >> /etc/apache2/sites-available/$DOMAIN.conf
echo -e "\tServerAlias www.$DOMAIN" >> /etc/apache2/sites-available/$DOMAIN.conf
echo -e "\tServerAdmin webmaster@localhost" >> /etc/apache2/sites-available/$DOMAIN.conf
echo -e "\tDocumentRoot /var/www/$DOMAIN" >> /etc/apache2/sites-available/$DOMAIN.conf
echo -e '\tErrorLog ${APACHE_LOG_DIR}/error.log' >> /etc/apache2/sites-available/$DOMAIN.conf
echo -e '\tCustomLog ${APACHE_LOG_DIR}/access.log combined' >> /etc/apache2/sites-available/$DOMAIN.conf
echo "</VirtualHost>" >> /etc/apache2/sites-available/$DOMAIN.conf
a2ensite $DOMAIN
a2dissite 000-default
systemctl reload apache2
}
```
Next, we are going to create the `ssl_config()` function. Inside of it, we are going to generate the OpenSSL certificate, append the SSL certificate to the `ssl-params.conf` file, append the SSL config to the Virtualhost file, enable SSL and reload Apache2.
```bash
ssl_config () {
openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout /etc/ssl/private/apache-selfsigned.key -out /etc/ssl/certs/apache-selfsigned.crt
echo "SSLCipherSuite EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH" >> /etc/apache2/conf-available/ssl-params.conf
echo "SSLProtocol All -SSLv2 -SSLv3 -TLSv1 -TLSv1.1" >> /etc/apache2/conf-available/ssl-params.conf
echo "SSLHonorCipherOrder On" >> /etc/apache2/conf-available/ssl-params.conf
echo "Header always set X-Frame-Options DENY" >> /etc/apache2/conf-available/ssl-params.conf
echo "Header always set X-Content-Type-Options nosniff" >> /etc/apache2/conf-available/ssl-params.conf
echo "SSLCompression off" >> /etc/apache2/conf-available/ssl-params.conf
echo "SSLUseStapling on" >> /etc/apache2/conf-available/ssl-params.conf
echo "SSLStaplingCache \"shmcb:logs/stapling-cache(150000)\"" >> /etc/apache2/conf-available/ssl-params.conf
echo "SSLSessionTickets Off" >> /etc/apache2/conf-available/ssl-params.conf
cp /etc/apache2/sites-available/default-ssl.conf /etc/apache2/sites-available/default-ssl.conf.bak
sed -i "s/var\/www\/html/var\/www\/$DOMAIN/1" /etc/apache2/sites-available/default-ssl.conf
sed -i "s/etc\/ssl\/certs\/ssl-cert-snakeoil.pem/etc\/ssl\/certs\/apache-selfsigned.crt/1" /etc/apache2/sites-available/default-ssl.conf
sed -i "s/etc\/ssl\/private\/ssl-cert-snakeoil.key/etc\/ssl\/private\/apache-selfsigned.key/1" /etc/apache2/sites-available/default-ssl.conf
sed -i "4i\\\t\tServerName $ip" /etc/apache2/sites-available/default-ssl.conf
sed -i "22i\\\tRedirect permanent \"/\" \"https://$ip/\"" /etc/apache2/sites-available/000-default.conf
a2enmod ssl
a2enmod headers
a2ensite default-ssl
a2enconf ssl-params
systemctl reload apache2
}
```
Next, we are going to create the `db_setup()` function. Inside of it, we are going to create the database, create the user and grant all privileges to the user.
```bash
db_config () {
mysql -e "CREATE DATABASE $DBNAME;"
mysql -e "GRANT ALL ON $DBNAME.* TO '$DBUSERNAME'@'localhost' IDENTIFIED BY '$DBPASSWORD' WITH GRANT OPTION;"
mysql -e "FLUSH PRIVILEGES;"
}
```
Next, we are going to create the `wordpress_config()` function. Inside of it, we are going to download the latest version of WordPress, extract it to the `/var/www/$DOMAIN` directory, create the `wp-config.php` file and append the required content to it.
```bash
wordpress_config () {
db_config
apt install php-curl php-gd php-mbstring php-xml php-xmlrpc php-soap php-intl php-zip -y
systemctl restart apache2
sed -i "8i\\\t<Directory /var/www/$DOMAIN/>" /etc/apache2/sites-available/$DOMAIN.conf
sed -i "9i\\\t\tAllowOverride All" /etc/apache2/sites-available/$DOMAIN.conf
sed -i "10i\\\t</Directory>" /etc/apache2/sites-available/$DOMAIN.conf
a2enmod rewrite
systemctl restart apache2
apt install curl
cd /tmp
curl -O https://wordpress.org/latest.tar.gz
tar xzvf latest.tar.gz
touch /tmp/wordpress/.htaccess
cp /tmp/wordpress/wp-config-sample.php /tmp/wordpress/wp-config.php
mkdir /tmp/wordpress/wp-content/upgrade
cp -a /tmp/wordpress/. /var/www/$DOMAIN
chown -R www-data:www-data /var/www/$DOMAIN
find /var/www/$DOMAIN/ -type d -exec chmod 750 {} \;
find /var/www/$DOMAIN/ -type f -exec chmod 640 {} \;
curl -s https://api.wordpress.org/secret-key/1.1/salt/ >> /var/www/$DOMAIN/wp-config.php
echo "define('FS_METHOD', 'direct');" >> /var/www/$DOMAIN/wp-config.php
sed -i "51,58d" /var/www/$DOMAIN/wp-config.php
sed -i "s/database_name_here/$DBNAME/1" /var/www/$DOMAIN/wp-config.php
sed -i "s/username_here/$DBUSERNAME/1" /var/www/$DOMAIN/wp-config.php
sed -i "s/password_here/$DBPASSWORD/1" /var/www/$DOMAIN/wp-config.php
}
```
And finally, we are going to create the `execute()` function. Inside of it, we are going to call all the functions we created above.
```bash
execute () {
lamp_install
apache_virtual_host_setup
ssl_config
wordpress_config
}
```
With this, you have the script ready and you are ready to run it. And if you need the full script, you can find it in the next section.
# The full script
```bash
#!/bin/bash
echo 'Please enter your domain of preference without www:'
read DOMAIN
echo "Please enter your Database username:"
read DBUSERNAME
echo "Please enter your Database password:"
read DBPASSWORD
echo "Please enter your Database name:"
read DBNAME
ip=`hostname -I | cut -f1 -d' '`
lamp_install () {
apt update -y
apt install ufw
ufw enable
ufw allow OpenSSH
ufw allow in "WWW Full"
apt install apache2 -y
apt install mariadb-server
mysql_secure_installation -y
apt install php libapache2-mod-php php-mysql -y
sed -i "2d" /etc/apache2/mods-enabled/dir.conf
sed -i "2i\\\tDirectoryIndex index.php index.html index.cgi index.pl index.xhtml index.htm" /etc/apache2/mods-enabled/dir.conf
systemctl reload apache2
}
apache_virtual_host_setup () {
mkdir /var/www/$DOMAIN
chown -R $USER:$USER /var/www/$DOMAIN
echo "<VirtualHost *:80>" >> /etc/apache2/sites-available/$DOMAIN.conf
echo -e "\tServerName $DOMAIN" >> /etc/apache2/sites-available/$DOMAIN.conf
echo -e "\tServerAlias www.$DOMAIN" >> /etc/apache2/sites-available/$DOMAIN.conf
echo -e "\tServerAdmin webmaster@localhost" >> /etc/apache2/sites-available/$DOMAIN.conf
echo -e "\tDocumentRoot /var/www/$DOMAIN" >> /etc/apache2/sites-available/$DOMAIN.conf
echo -e '\tErrorLog ${APACHE_LOG_DIR}/error.log' >> /etc/apache2/sites-available/$DOMAIN.conf
echo -e '\tCustomLog ${APACHE_LOG_DIR}/access.log combined' >> /etc/apache2/sites-available/$DOMAIN.conf
echo "</VirtualHost>" >> /etc/apache2/sites-available/$DOMAIN.conf
a2ensite $DOMAIN
a2dissite 000-default
systemctl reload apache2
}
ssl_config () {
openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout /etc/ssl/private/apache-selfsigned.key -out /etc/ssl/certs/apache-selfsigned.crt
echo "SSLCipherSuite EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH" >> /etc/apache2/conf-available/ssl-params.conf
echo "SSLProtocol All -SSLv2 -SSLv3 -TLSv1 -TLSv1.1" >> /etc/apache2/conf-available/ssl-params.conf
echo "SSLHonorCipherOrder On" >> /etc/apache2/conf-available/ssl-params.conf
echo "Header always set X-Frame-Options DENY" >> /etc/apache2/conf-available/ssl-params.conf
echo "Header always set X-Content-Type-Options nosniff" >> /etc/apache2/conf-available/ssl-params.conf
echo "SSLCompression off" >> /etc/apache2/conf-available/ssl-params.conf
echo "SSLUseStapling on" >> /etc/apache2/conf-available/ssl-params.conf
echo "SSLStaplingCache \"shmcb:logs/stapling-cache(150000)\"" >> /etc/apache2/conf-available/ssl-params.conf
echo "SSLSessionTickets Off" >> /etc/apache2/conf-available/ssl-params.conf
cp /etc/apache2/sites-available/default-ssl.conf /etc/apache2/sites-available/default-ssl.conf.bak
sed -i "s/var\/www\/html/var\/www\/$DOMAIN/1" /etc/apache2/sites-available/default-ssl.conf
sed -i "s/etc\/ssl\/certs\/ssl-cert-snakeoil.pem/etc\/ssl\/certs\/apache-selfsigned.crt/1" /etc/apache2/sites-available/default-ssl.conf
sed -i "s/etc\/ssl\/private\/ssl-cert-snakeoil.key/etc\/ssl\/private\/apache-selfsigned.key/1" /etc/apache2/sites-available/default-ssl.conf
sed -i "4i\\\t\tServerName $ip" /etc/apache2/sites-available/default-ssl.conf
sed -i "22i\\\tRedirect permanent \"/\" \"https://$ip/\"" /etc/apache2/sites-available/000-default.conf
a2enmod ssl
a2enmod headers
a2ensite default-ssl
a2enconf ssl-params
systemctl reload apache2
}
db_config () {
mysql -e "CREATE DATABASE $DBNAME;"
mysql -e "GRANT ALL ON $DBNAME.* TO '$DBUSERNAME'@'localhost' IDENTIFIED BY '$DBPASSWORD' WITH GRANT OPTION;"
mysql -e "FLUSH PRIVILEGES;"
}
wordpress_config () {
db_config
apt install php-curl php-gd php-mbstring php-xml php-xmlrpc php-soap php-intl php-zip -y
systemctl restart apache2
sed -i "8i\\\t<Directory /var/www/$DOMAIN/>" /etc/apache2/sites-available/$DOMAIN.conf
sed -i "9i\\\t\tAllowOverride All" /etc/apache2/sites-available/$DOMAIN.conf
sed -i "10i\\\t</Directory>" /etc/apache2/sites-available/$DOMAIN.conf
a2enmod rewrite
systemctl restart apache2
apt install curl
cd /tmp
curl -O https://wordpress.org/latest.tar.gz
tar xzvf latest.tar.gz
touch /tmp/wordpress/.htaccess
cp /tmp/wordpress/wp-config-sample.php /tmp/wordpress/wp-config.php
mkdir /tmp/wordpress/wp-content/upgrade
cp -a /tmp/wordpress/. /var/www/$DOMAIN
chown -R www-data:www-data /var/www/$DOMAIN
find /var/www/$DOMAIN/ -type d -exec chmod 750 {} \;
find /var/www/$DOMAIN/ -type f -exec chmod 640 {} \;
curl -s https://api.wordpress.org/secret-key/1.1/salt/ >> /var/www/$DOMAIN/wp-config.php
echo "define('FS_METHOD', 'direct');" >> /var/www/$DOMAIN/wp-config.php
sed -i "51,58d" /var/www/$DOMAIN/wp-config.php
sed -i "s/database_name_here/$DBNAME/1" /var/www/$DOMAIN/wp-config.php
sed -i "s/username_here/$DBUSERNAME/1" /var/www/$DOMAIN/wp-config.php
sed -i "s/password_here/$DBPASSWORD/1" /var/www/$DOMAIN/wp-config.php
}
execute () {
lamp_install
apache_virtual_host_setup
ssl_config
wordpress_config
}
```
## Summary
The script does the following:
* Install LAMP
* Create a virtual host
* Configure SSL
* Install WordPress
* Configure WordPress
With this being said, I hope you enjoyed this example. If you have any questions, please feel free to ask me directly at [@denctl](https://twitter.com/denctl).

15
landing/docs/.Bash-Scripting/100-bash-wrap-up.md
View File

@@ -1,15 +0,0 @@
# Wrap Up
Congratulations! You have just completed the Bash basics guide!
If you found this useful, be sure to star the project on [GitHub](https://github.com/bobbyiliev/introduction-to-bash-scripting)!
If you have any suggestions for improvements, make sure to contribute pull requests or open issues.
In this introduction to Bash scripting book, we just covered the basics, but you still have enough under your belt to start wringing some awesome scripts and automating daily tasks!
As a next step try writing your own script and share it with the world! This is the best way to learn any new programming or scripting language!
In case that this book inspired you to write some cool Bash scripts, make sure to tweet about it and tag [@bobbyiliev_](https://twitter.com) so that we could check it out!
Congrats again on completing this book!

82
landing/docs/.recycle/extras.md
View File

@@ -1,82 +0,0 @@
# A Linux Learning Playground Situation
!["Shinobi Academy Linux"](/cover.png)
wanna play with the application in this picture? connect to the server using the instructions below and run the command `hollywood`
## Introduction:
Welcome, aspiring Linux ninjas! This tutorial will guide you through accessing Shinobi Academy Linux, a custom-built server designed to provide a safe and engaging environment for you to learn and experiment with Linux. Brought to you by Softwareshinobi ([https://softwareshinobi.digital/](https://softwareshinobi.digital/)), this server is your gateway to the exciting world of open-source exploration.
## What You'll Learn:
* Connecting to a Linux server (using SSH)
* Basic Linux commands (navigation, listing files, etc.)
* Exploring pre-installed tools like cmatrix and hollywood
## What You'll Need:
* A computer with internet access
* An SSH client (built-in on most Linux and macOS systems, downloadable for Windows)
## About Shinobi Academy:
Shinobi Academy, the online learning platform brought to you by Softwareshinobi!
Designed to empower aspiring tech enthusiasts, Shinobi Academy offers a comprehensive range of courses and resources to equip you with the skills you need to excel in the ever-evolving world of technology.
## Connecting to Shinobi Academy Linux:
1. Open your SSH client.
2. Enter the following command (including the port number):
```
ssh -p 2222 shinobi@linux.softwareshinobi.digital
```
3. When prompted, enter the password "shinobi".
```
username / shinobi
```
```
password / shinobi
```
**Congratulations!** You're now connected to Shinobi Academy Linux.
## Exploring the Server:
Once connected, you can use basic Linux commands to navigate the system and explore its features. Here are a few examples:
* **`ls`:** Lists files and directories in the current directory.
* **`cd`:** Changes directory. For example, `cd Desktop` will move you to the Desktop directory (if it exists).
* **`pwd`:** Shows the current working directory.
* **`man` followed by a command name:** Provides detailed information on a specific command (e.g., `man ls`).
## Pre-installed Goodies:
Shinobi Academy Linux comes pre-installed with some interesting tools to enhance your learning experience:
* **`cmatrix`:** Simulates the iconic falling code effect from the movie "The Matrix".
* **`hollywood`:** Creates a variety of dynamic text effects on your terminal.
**Experimenting with these tools is a great way to explore the possibilities of Linux.**
## Conclusion:
By following these steps, you've successfully connected to Shinobi Academy Linux and begun your journey into the world of Linux. Use this platform to explore, experiment, and build your Linux skills!
A big thanks to Gemini for putting together these awesome docs!
## Master Linux Like a Pro: 1-on-1 Tutoring:
**Tired of fumbling in the terminal?** Imagine wielding Linux commands with ease, managing servers like a corporate ninja – just like my government and corporate gigs.
**1-on-1 tutoring unlocks your potential:**
* **Terminal mastery:** Conquer the command line and automate tasks like a pro.
* **Become a command jedi:** Craft commands with lightning speed, streamlining your workflow.
**Ready to transform your skills?** [Learn More!](tutor.softwareshinobi.digital/linux)

BIN
landing/docs/.recycle/introduction-to-bash-scripting-main.zip
View File

Binary file not shown.

BIN
landing/docs/.recycle/videos/commands/the-deluser-command.mp4
View File

Binary file not shown.

BIN
landing/docs/.recycle/videos/commands/the-zip-command.jpg
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 10 KiB

BIN
landing/docs/.recycle/videos/commands/the-zip-command.mp4
View File

Binary file not shown.

59
landing/docs/Linux-Commands/.recycle/008-the-cal-command.md
View File

@@ -1,59 +0,0 @@
# The `cal` Command
The `cal` command displays a formatted calendar in the terminal. If no options are specified, cal displays the current month, with the current day highlighted.
### Syntax:
```
cal [general options] [-jy] [[month] year]
```
### Options:
|**Option**|**Description**|
|:--|:--|
|`-h`|Don't highlight today's date.|
|`-m month`|Specify a month to display. The month specifier is a full month name (e.g., February), a month abbreviation of at least three letters (e.g., Feb), or a number (e.g., 2). If you specify a number, followed by the letter "f" or "p", the month of the following or previous year, respectively, display. For instance, `-m 2f` displays February of next year.|
|`-y year`|Specify a year to display. For example, `-y 1970` displays the entire calendar of the year 1970.|
|`-3`|Display last month, this month, and next month.|
|`-1`|Display only this month. This is the default.|
|`-A num`|Display num months occurring after any months already specified. For example, `-3 -A 3` displays last month, this month, and four months after this one; and `-y 1970 -A 2` displays every month in 1970, and the first two months of 1971.|
|`-B num`|Display num months occurring before any months already specified. For example, `-3 -B 2` displays the previous three months, this month, and next month.|
|`-d YYYY-MM`|Operate as if the current month is number MM of year YYYY.|
### Examples:
1. Display the calendar for this month, with today highlighted.
```
cal
```
2. Same as the previous command, but do not highlight today.
```
cal -h
```
3. Display last month, this month, and next month.
```
cal -3
```
4. Display this entire year's calendar.
```
cal -y
```
5. Display the entire year 2000 calendar.
```
cal -y 2000
```
6. Same as the previous command.
```
cal 2000
```
7. Display the calendar for December of this year.
```
cal -m [December, Dec, or 12]
```
10. Display the calendar for December 2000.
```
cal 12 2000
```

94
landing/docs/Linux-Commands/.recycle/009-the-bc-command.md
View File

@@ -1,94 +0,0 @@
# The `bc` command
The `bc` command provides the functionality of being able to perform mathematical calculations through the command line.
### Examples:
1 . Arithmetic:
```
Input : $ echo "11+5" | bc
Output : 16
```
2 . Increment:
- var –++ : Post increment operator, the result of the variable is used first and then the variable is incremented.
- – ++var : Pre increment operator, the variable is increased first and then the result of the variable is stored.
```
Input: $ echo "var=3;++var" | bc
Output: 4
```
3 . Decrement:
- var – – : Post decrement operator, the result of the variable is used first and then the variable is decremented.
- – – var : Pre decrement operator, the variable is decreased first and then the result of the variable is stored.
```
Input: $ echo "var=3;--var" | bc
Output: 2
```
4 . Assignment:
- var = value : Assign the value to the variable
- var += value : similar to var = var + value
- var -= value : similar to var = var – value
- var *= value : similar to var = var * value
- var /= value : similar to var = var / value
- var ^= value : similar to var = var ^ value
- var %= value : similar to var = var % value
```
Input: $ echo "var=4;var" | bc
Output: 4
```
5 . Comparison or Relational:
- If the comparison is true, then the result is 1. Otherwise,(false), returns 0
- expr1<expr2 : Result is 1, if expr1 is strictly less than expr2.
- expr1<=expr2 : Result is 1, if expr1 is less than or equal to expr2.
- expr1>expr2 : Result is 1, if expr1 is strictly greater than expr2.
- expr1>=expr2 : Result is 1, if expr1 is greater than or equal to expr2.
- expr1==expr2 : Result is 1, if expr1 is equal to expr2.
- expr1!=expr2 : Result is 1, if expr1 is not equal to expr2.
```
Input: $ echo "6<4" | bc
Output: 0
```
```
Input: $ echo "2==2" | bc
Output: 1
```
6 . Logical or Boolean:
- expr1 && expr2 : Result is 1, if both expressions are non-zero.
- expr1 || expr2 : Result is 1, if either expression is non-zero.
- ! expr : Result is 1, if expr is 0.
```
Input: $ echo "! 1" | bc
Output: 0
Input: $ echo "10 && 5" | bc
Output: 1
```
### Syntax:
```
bc [ -hlwsqv ] [long-options] [ file ... ]
```
### Additional Flags and their Functionalities:
*Note: This does not include an exhaustive list of options.*
|**Short Flag** |**Long Flag** |**Description** |
|:---|:---|:---|
|`-i`|`--interactive`|Force interactive mode|
|`-l`|`--mathlib`|Use the predefined math routines|
|`-q`|`--quiet`|Opens the interactive mode for bc without printing the header|
|`-s`|`--standard`|Treat non-standard bc constructs as errors|
|`-w`|`--warn`|Provides a warning if non-standard bc constructs are used|
### Notes:
1. The capabilities of `bc` can be further appreciated if used within a script. Aside from basic arithmetic operations, `bc` supports increments/decrements, complex calculations, logical comparisons, etc.
2. Two of the flags in `bc` refer to non-standard constructs. If you evaluate `100>50 | bc` for example, you will get a strange warning. According to the POSIX page for bc, relational operators are only valid if used within an `if`, `while`, or `for` statement.

31
landing/docs/Linux-Commands/.recycle/011-the-help-command.md
View File

@@ -1,31 +0,0 @@
# The `help` command
The `help` command displays information about builtin commands.
Display information about builtin commands.
If a `PATTERN` is specified, this command gives detailed help on all commands matching the `PATTERN`, otherwise the list of available help topics is printed.
## Syntax
```bash
$ help [-dms] [PATTERN ...]
```
## Options
|**Option**|**Description**|
|:--|:--|
|`-d`|Output short description for each topic.|
|`-m`|Display usage in pseudo-manpage format.|
|`-s`|Output only a short usage synopsis for each topic matching the provided `PATTERN`.|
## Examples of uses:
1. We get the complete information about the `cd` command
```bash
$ help cd
```
2. We get a short description about the `pwd` command
```bash
$ help -d pwd
```
3. We get the syntax of the `cd` command
```bash
$ help -s cd
```

29
landing/docs/Linux-Commands/.recycle/012-the-factor-command.md
View File

@@ -1,29 +0,0 @@
# The `factor` command
The `factor` command prints the prime factors of each specified integer `NUMBER`. If none are specified on the command line, it will read them from the standard input.
## Syntax
```bash
$ factor [NUMBER]...
```
OR:
```bash
$ factor OPTION
```
## Options
|**Option**|**Description**|
|:--|:--|
|`--help`|Display this a help message and exit.|
|`--version`|Output version information and exit.|
## Examples
1. Print prime factors of a prime number.
```bash
$ factor 50
```
2. Print prime factors of a non-prime number.
```bash
$ factor 75
```

32
landing/docs/Linux-Commands/.recycle/016-the-whatis-command.md
View File

@@ -1,32 +0,0 @@
# The `whatis` command
The `whatis` command is used to display one-line manual page descriptions for commands.
It can be used to get a basic understanding of what a (unknown) command is used for.
### Examples of uses:
1. To display what `ls` is used for:
```
whatis ls
```
2. To display the use of all commands which start with `make`, execute the following:
```
whatis -w make*
```
### Syntax:
```
whatis [-OPTION] [KEYWORD]
```
### Additional Flags and their Functionalities:
|**Short Flag** |**Long Flag** |**Description** |
|:---|:---|:---|
|`-d`|`--debug`|Show debugging messages|
|`-r`|`--regex`|Interpret each keyword as a regex|
|`-w`|`--wildcard`|The keyword(s) contain wildcards|

33
landing/docs/Linux-Commands/.recycle/017-the-who-command.md
View File

@@ -1,33 +0,0 @@
# The `who` command
The `who` command lets you print out a list of logged-in users, the current run level of the system and the time of last system boot.
### Examples
1. Print out all details of currently logged-in users
```
who -a
```
2. Print out the list of all dead processes
```
who -d -H
```
### Syntax:
```
who [options] [filename]
```
### Additional Flags and their Functionalities
|**Short Flag** |**Description** |
|---|---|
| `-r` |prints all the current runlevel |
| `-d` |print all the dead processes |
|`-q`|print all the login names and total number of logged on users |
|`-h`|print the heading of the columns displayed |
|`-b`|print the time of last system boot |

33
landing/docs/Linux-Commands/.recycle/018-the-free-command.md
View File

@@ -1,33 +0,0 @@
018-the-free-command.md
# The `free` command
The `free` command in Linux/Unix is used to show memory (RAM/SWAP) information.
# Usage
## Show memory usage
**Action:**
--- Output the memory usage - available and used, as well as swap
**Details:**
--- Outputted values are not human-readable (are in bytes)
**Command:**
```
free
```
## Show memory usage in human-readable form
**Action:**
--- Output the memory usage - available and used, as well as swap
**Details:**
--- Outputted values ARE human-readable (are in GB / MB)
**Command:**
```
free -h
```

19
landing/docs/Linux-Commands/.recycle/020-the-sl-command.md
View File

@@ -1,19 +0,0 @@
# The `sl` command
The `sl` command in Linux is a humorous program that runs a steam locomotive(sl) across your terminal.
![image](https://i.imgur.com/CInBHak.png)
## Installation
Install the package before running.
```
sudo apt install sl
```
## Syntax
```
sl
```

76
landing/docs/Linux-Commands/.recycle/022-the-finger-command.md
View File

@@ -1,76 +0,0 @@
# The `finger` command
The `finger` displays information about the system users.
### Examples:
1. View detail about a particular user.
```
finger abc
```
*Output*
```
Login: abc Name: (null)
Directory: /home/abc Shell: /bin/bash
On since Mon Nov 1 18:45 (IST) on :0 (messages off)
On since Mon Nov 1 18:46 (IST) on pts/0 from :0.0
New mail received Fri May 7 10:33 2013 (IST)
Unread since Sat Jun 7 12:59 2003 (IST)
No Plan.
```
2. View login details and Idle status about an user
```
finger -s root
```
*Output*
```
Login Name Tty Idle Login Time Office Office Phone
root root *1 19d Wed 17:45
root root *2 3d Fri 16:53
root root *3 Mon 20:20
root root *ta 2 Tue 15:43
root root *tb 2 Tue 15:44
```
### Syntax:
```
finger [-l] [-m] [-p] [-s] [username]
```
### Additional Flags and their Functionalities:
|**Flag** |**Description** |
|:---|:---|
|`-l`|Force long output format.|
|`-m`|Match arguments only on user name (not first or last name).|
|`-p`|Suppress printing of the .plan file in a long format printout.|
|`-s`|Force short output format.|
### Additional Information
**Default Format**
The default format includes the following items:
Login name
Full username
Terminal name
Write status (an * (asterisk) before the terminal name indicates that write permission is denied)
For each user on the host, the default information list also includes, if known, the following items:
Idle time (Idle time is minutes if it is a single integer, hours and minutes if a : (colon) is present, or days and hours if a “d” is present.)
Login time
Site-specific information
**Longer Format**
A longer format is used by the finger command whenever a list of user’s names is given. (Account names as well as first and last names of users are accepted.) This format is multiline, and includes all the information described above along with the following:
User’s $HOME directory
User’s login shell
Contents of the .plan file in the user’s $HOME directory
Contents of the .project file in the user’s $HOME directory

56
landing/docs/Linux-Commands/.recycle/026-the-w-command.md
View File

@@ -1,56 +0,0 @@
# The `w` command
The `w` command displays information about the users that are currently active on the machine and their [processes](https://www.computerhope.com/jargon/p/process.htm).
### Examples:
1. Running the `w` command without [arguments](https://www.computerhope.com/jargon/a/argument.htm) shows a list of logged on users and their processes.
```
w
```
2. Show information for the user named *hope*.
```
w hope
```
### Syntax:
```
finger [-l] [-m] [-p] [-s] [username]
```
### Additional Flags and their Functionalities:
|**Short Flag** |**Long Flag** |**Description** |
|:---|:---|:---|
|`-h`|`--no-header`|Don't print the header.|
|`-u`|`--no-current`|Ignores the username while figuring out the current process and cpu times. *(To see an example of this, switch to the root user with `su` and then run both `w` and `w -u`.)*|
|`-s`|`--short`|Display abbreviated output *(don't print the login time, JCPU or PCPU times).*|
|`-f`|`--from`|Toggle printing the from *(remote hostname)* field. The default as released is for the from field to not be printed, although your system administrator or distribution maintainer may have compiled a version where the from field is shown by default.|
|`--help`|<center>-</center>|Display a help message, and exit.|
|`-V`|`--version`|Display version information, and exit.|
|`-o`|`--old-style`|Old style output *(prints blank space for idle times less than one minute)*.|
|*`user`*|<center>-</center>|Show information about the specified the user only.|
### Additional Information
The [header](https://www.computerhope.com/jargon/h/header.htm) of the output shows (in this order): the current time, how long the system has been running, how many users are currently logged on, and the system [load](https://www.computerhope.com/jargon/l/load.htm) averages for the past 1, 5, and 15 minutes.
The following entries are displayed for each user:
- login name the [tty](https://www.computerhope.com/jargon/t/tty.htm)
- name the [remote](https://www.computerhope.com/jargon/r/remote.htm)
- [host](https://www.computerhope.com/jargon/h/hostcomp.htm) they are
- logged in from the amount of time they are logged in their
- [idle](https://www.computerhope.com/jargon/i/idle.htm) time JCPU
- PCPU
- [command line](https://www.computerhope.com/jargon/c/commandi.htm) of their current process
The JCPU time is the time used by all processes attached to the tty. It does not include past background jobs, but does include currently running background jobs.
The PCPU time is the time used by the current process, named in the "what" field.

28
landing/docs/Linux-Commands/.recycle/029-the-login-command.md
View File

@@ -1,28 +0,0 @@
# The `login` Command
The `login` command initiates a user session.
## Syntax
```bash
$ login [-p] [-h host] [-H] [-f username|username]
```
## Flags and their functionalities
|**Short Flag** |**Description** |
|---|---|
| `-f` |Used to skip a login authentication. This option is usually used by the getty(8) autologin feature. |
| `-h` | Used by other servers (such as telnetd(8) to pass the name of the remote host to login so that it can be placed in utmp and wtmp. Only the superuser is allowed use this option. |
|`-p`|Used by getty(8) to tell login to preserve the environment. |
|`-H`|Used by other servers (for example, telnetd(8)) to tell login that printing the hostname should be suppressed in the login: prompt. |
|`--help`|Display help text and exit.|
|`-v`|Display version information and exit.|
## Examples
To log in to the system as user abhishek, enter the following at the login prompt:
```bash
$ login: abhishek
```
If a password is defined, the password prompt appears. Enter your password at this prompt.

52
landing/docs/Linux-Commands/.recycle/030-the-lscpu-command.md
View File

@@ -1,52 +0,0 @@
# `lscpu` command
`lscpu` in Linux/Unix is used to display CPU Architecture info. `lscpu` gathers CPU architecture information from `sysfs` and `/proc/cpuinfo` files.
For example :
```
manish@godsmack:~$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 2
Core(s) per socket: 2
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 142
Model name: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
Stepping: 9
CPU MHz: 700.024
CPU max MHz: 3100.0000
CPU min MHz: 400.0000
BogoMIPS: 5399.81
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 3072K
NUMA node0 CPU(s): 0-3
```
## Options
`-a, --all`
Include lines for online and offline CPUs in the output (default for -e). This option may only specified together with option -e or -p.
For example: `lsof -a`
`-b, --online`
Limit the output to online CPUs (default for -p). This option may only be specified together with option -e or -p.
For example: `lscpu -b`
`-c, --offline`
Limit the output to offline CPUs. This option may only be specified together with option -e or -p.
`-e, --extended [=list]`
Display the CPU information in human readable format.
For example: `lsof -e`
For more info: use `man lscpu` or `lscpu --help`

37
landing/docs/Linux-Commands/.recycle/037-the-printenv-command.md
View File

@@ -1,37 +0,0 @@
# The `printenv` command
The `printenv` prints the values of the specified [environment _VARIABLE(s)_](https://www.computerhope.com/jargon/e/envivari.htm). If no [_VARIABLE_](https://www.computerhope.com/jargon/v/variable.htm) is specified, print name and value pairs for them all.
### Examples:
1. Display the values of all environment variables.
```
printenv
```
2. Display the location of the current user's [home directory](https://www.computerhope.com/jargon/h/homedir.htm).
```
printenv HOME
```
3. To use the `--null` command line option as the terminating character between output entries.
```
printenv --null SHELL HOME
```
*NOTE: By default, the* `printenv` *command uses newline as the terminating character between output entries.*
### Syntax:
```
printenv [OPTION]... PATTERN...
```
### Additional Flags and their Functionalities:
|**Short Flag** |**Long Flag** |**Description** |
|:---|:---|:---|
|`-0`|`--null`|End each output line with **0** byte rather than [newline](https://www.computerhope.com/jargon/n/newline.htm).|
|`--help`|<center>-</center>|Display a help message, and exit.|

39
landing/docs/Linux-Commands/.recycle/042-the-ip-command.md
View File

@@ -1,39 +0,0 @@
# The `ip` command
The `ip` command is present in the net-tools which is used for performing several network administration tasks. IP stands for Internet Protocol. This command is used to show or manipulate routing, devices, and tunnels. It can perform tasks like configuring and modifying the default and static routing, setting up tunnel over IP, listing IP addresses and property information, modifying the status of the interface, assigning, deleting and setting up IP addresses and routes.
### Examples:
1. To assign an IP Address to a specific interface (eth1) :
```
ip addr add 192.168.50.5 dev eth1
```
2. To show detailed information about network interfaces like IP Address, MAC Address information etc. :
```
ip addr show
```
### Syntax:
```
ip [ OPTIONS ] OBJECT { COMMAND | help }
```
### Additional Flags and their Functionalities:
|**Flag** |**Description** |
|:---|:---|
|`-a`| Display and modify IP Addresses |
|`-l`|Display and modify network interfaces |
|`-r`|Display and alter the routing table|
|`-n`|Display and manipulate neighbor objects (ARP table) |
|`-ru`|Rule in routing policy database.|
|`-s`|Output more information. If the option appears twice or more, the amount of information increases |
|`-f`|Specifies the protocol family to use|
|`-r`|Use the system's name resolver to print DNS names instead of host addresses|
|`-c`|To configure color output |

23
landing/docs/Linux-Commands/.recycle/048-the-last-command.md
View File

@@ -1,23 +0,0 @@
# The `last` command
This command shows you a list of all the users that have logged in and out since the creation of the `var/log/wtmp` file. There are also some parameters you can add which will show you for example when a certain user has logged in and how long he was logged in for.
If you want to see the last 5 logs, just add `-5` to the command like this:
```
last -5
```
And if you want to see the last 10, add `-10`.
Another cool thing you can do is if you add `-F` you can see the login and logout time including the dates.
```
last -F
```
There are quite a lot of stuff you can view with this command. If you need to find out more about this command you can run:
```
last --help
```

93
landing/docs/Linux-Commands/.recycle/049-the-locate-command.md
View File

@@ -1,93 +0,0 @@
# The `locate` command
The `locate` command searches the file system for files and directories whose name matches a given pattern through a database file that is generated by the `updatedb` command.
### Examples:
1. Running the `locate` command to search for a file named `.bashrc`.
```
locate .bashrc
```
*Output*
```
/etc/bash.bashrc
/etc/skel/.bashrc
/home/linuxize/.bashrc
/usr/share/base-files/dot.bashrc
/usr/share/doc/adduser/examples/adduser.local.conf.examples/bash.bashrc
/usr/share/doc/adduser/examples/adduser.local.conf.examples/skel/dot.bashrc
```
The `/root/.bashrc` file will not be shown because we ran the command as a normal user that doesn’t have access permissions to the `/root` directory.
If the result list is long, for better readability, you can pipe the output to the [`less`](https://linuxize.com/post/less-command-in-linux/) command:
```
locate .bashrc | less
```
2. To search for all `.md` files on the system
```
locate *.md
```
3. To search all `.py` files and display only 10 results
```
locate -n 10 *.py
```
4. To performs case-insensitive search.
```
locate -i readme.md
```
*Output*
```
/home/linuxize/p1/readme.md
/home/linuxize/p2/README.md
/home/linuxize/p3/ReadMe.md
```
5. To return the number of all files containing `.bashrc` in their name.
```
locate -c .bashrc
```
*Output*
```
6
```
6. The following would return only the existing `.json` files on the file system.
```
locate -e *.json
```
7. To run a more complex search the `-r` (`--regexp`) option is used.
To search for all `.mp4` and `.avi` files on your system and ignore case.
```
locate --regex -i "(\.mp4|\.avi)"
```
### Syntax:
```
1. locate [OPTION]... PATTERN...
```
### Additional Flags and their Functionalities:
|**Short Flag** |**Long Flag** |**Description** |
|:---|:---|:---|
|`-A`|`--all`|It is used to display only entries that match all PATTERNs instead of requiring only one of them to match.|
|`-b`|`--basename`|It is used to match only the base name against the specified patterns.|
|`-c`|`--count`|It is used for writing the number matching entries instead of writing file names on standard output.|
|`-d`|`--database DBPATH`|It is used to replace the default database with DBPATH.|
|`-e`|`--existing`|It is used to display only entries that refer to existing files during the command is executed.|
|`-L`|`--follow`|If the `--existing` option is specified, It is used for checking whether files exist and follow trailing symbolic links. It will omit the broken symbolic links to the output. This is the default behavior. The opposite behavior can be specified using the `--nofollow` option.|
|`-h`|`--help`|It is used to display the help documentation that contains a summary of the available options.|
|`-i`|`--ignore-case`|It is used to ignore case sensitivity of the specified patterns.|
|`-p`|`--ignore-spaces`|It is used to ignore punctuation and spaces when matching patterns.|
|`-t`|`--transliterate`|It is used to ignore accents using iconv transliteration when matching patterns.|
|`-l`|`--limit, -n LIMIT`|If this option is specified, the command exit successfully after finding LIMIT entries.|
|`-m`|`--mmap`|It is used to ignore the compatibility with BSD, and GNU locate.|
|`-0`|`--null`|It is used to separate the entries on output using the ASCII NUL character instead of writing each entry on a separate line.|
|`-S`|`--statistics`|It is used to write statistics about each read database to standard output instead of searching for files.|
|`-r`|`--regexp REGEXP`|It is used for searching a basic regexp REGEXP.|
|`--regex`|<center>-</center>|It is used to describe all PATTERNs as extended regular expressions.|
|`-V`|`--version`|It is used to display the version and license information.|
|`-w`|` --wholename`|It is used for matching only the whole path name in specified patterns.|

47
landing/docs/Linux-Commands/.recycle/050-the-iostat-command.md
View File

@@ -1,47 +0,0 @@
# The `iostat` command
The `iostat` command in Linux is used for monitoring system input/output statistics for devices and partitions. It monitors system input/output by observing the time the devices are active in relation to their average transfer rates. The iostat produce reports may be used to change the system configuration to raised balance the input/output between the physical disks. iostat is being included in sysstat package. If you don’t have it, you need to install first.
### Syntax:
```[linux]
iostat [ -c ] [ -d ] [ -h ] [ -N ] [ -k | -m ] [ -t ] [ -V ] [ -x ]
[ -z ] [ [ [ -T ] -g group_name ] { device [...] | ALL } ]
[ -p [ device [,...] | ALL ] ] [ interval [ count ] ]
```
### Examples:
1. Display a single history-since-boot report for all CPU and Devices:
```[linux]
iostat -d 2
```
2. Display a continuous device report at two-second intervals:
```[linux]
iostat -d 2 6
```
3.Display, for all devices, six reports at two-second intervals:
```[linux]
iostat -x sda sdb 2 6
```
4.Display, for devices sda and sdb, six extended reports at two-second intervals:
```[linux]
iostat -p sda 2 6
```
### Additional Flags and their Functionalities:
| **Short Flag** | **Description** |
| :------------------------------ | :--------------------------------------------------------- |
| `-x` | Show more details statistics information. |
| `-c` | Show only the cpu statistic. |
| `-d` | Display only the device report |
| `-xd | Show extended I/O statistic for device only. |
| `-k` | Capture the statistics in kilobytes or megabytes. |
| `-k23` | Display cpu and device statistics with delay. |
| `-j ID mmcbkl0 sda6 -x -m 2 2` | Display persistent device name statistics. |
| `-p ` | Display statistics for block devices. |
| `-N ` | Display lvm2 statistic information. |

77
landing/docs/Linux-Commands/.recycle/059-the-sort-command.md
View File

@@ -1,77 +0,0 @@
# The `sort` command
the `sort` command is used to sort a file, arranging the records in a particular order. By default, the sort command sorts a file assuming the contents are ASCII. Using options in the sort command can also be used to sort numerically.
### Examples:
Suppose you create a data file with name file.txt:
```
Command :
$ cat > file.txt
abhishek
chitransh
satish
rajan
naveen
divyam
harsh
```
Sorting a file: Now use the sort command
Syntax :
```
sort filename.txt
```
```
Command:
$ sort file.txt
Output :
abhishek
chitransh
divyam
harsh
naveen
rajan
satish
```
Note: This command does not actually change the input file, i.e. file.txt.
### The sort function on a file with mixed case content
i.e. uppercase and lower case: When we have a mix file with both uppercase and lowercase letters then first the upper case letters would be sorted following with the lower case letters.
Example:
Create a file mix.txt
```
Command :
$ cat > mix.txt
abc
apple
BALL
Abc
bat
```
Now use the sort command
```
Command :
$ sort mix.txt
Output :
Abc
BALL
abc
apple
bat
```

33
landing/docs/Linux-Commands/.recycle/060-the-paste-command.md
View File

@@ -1,33 +0,0 @@
# The `paste` command
The `paste` command writes lines of two or more files, sequentially and separated by TABs, to the standard output
### Syntax:
```[linux]
paste [OPTIONS]... [FILE]...
```
### Examples:
1. To paste two files
```[linux]
paste file1 file2
```
2. To paste two files using new line as delimiter
```[linux]
paste -d '\n' file1 file2
```
### Additional Flags and their Functionalities:
| **Short Flag** | **Long Flag** | **Description** |
| :----------------- | :-------------------------- | :-------------------------------------------------------------------------------------------------------------------------------- |
| `-d` | `--delimiter` | use charater of TAB |
| `-s` | `--serial` | paste one file at a time instead of in parallel |
| `-z` | `--zero-terminated` | set line delimiter to NUL, not newline |
| | `--help` | print command help |
| | `--version` | print version information |

24
landing/docs/Linux-Commands/.recycle/066-the-iptable-command.md
View File

@@ -1,24 +0,0 @@
# The `iptables` Command
The `iptables` command is used to set up and maintain tables for the Netfilter firewall for IPv4, included in the Linux kernel. The firewall matches packets with rules defined in these tables and then takes the specified action on a possible match.
### Syntax:
```
iptables --table TABLE -A/-C/-D... CHAIN rule --jump Target
```
### Example and Explanation:
*This command will append to the chain provided in parameters:*
```
iptables [-t table] --append [chain] [parameters]
```
*This command drops all the traffic coming on any port:*
```
iptables -t filter --append INPUT -j DROP
```
### Flags and their Functionalities:
|Flag|Description|
|:---|:---|
|`-C`|Check if a rule is present in the chain or not. It returns 0 if the rule exists and returns 1 if it does not.|
|`-A`|Append to the chain provided in parameters.|

50
landing/docs/Linux-Commands/.recycle/068-the-lsof-command.md
View File

@@ -1,50 +0,0 @@
# The `lsof` command
The `lsof` command shows **file infomation** of all the files opened by a running process. It's name is also derived from the fact that, list open files > `lsof`
An open file may be a regular file, a directory, a block special file, a character special file, an executing text reference, a library , a stream or a network file (Internet socket, NFS file or UNIX domain socket). A specific file or all the files in a file system may be selected by path.
### Syntax:
```
lsof [-OPTION] [USER_NAME]
```
### Examples:
1. To show all the files opened by all active processes:
```
lsof
```
2. To show the files opened by a particular user:
```
lsof -u [USER_NAME]
```
3. To list the processes with opened files under a specified directory:
```
lsof +d [PATH_TO_DIR]
```
### Options and their Functionalities:
|**Option** |**Additional Options** |**Description** |
|:---|:---|:---|
|`-i`|`tcp`/ `udp`/ `:port`|List all network connections running, Additionally, on udp/tcp or on specified port.|
|`-i4`|<center>-</center>|List all processes with ipv4 connections.|
|`-i6`|<center>-</center>|List all processes with ipv6 connections.|
|`-c`|`[PROCESS_NAME]`|List all the files of a particular process with given name.|
|`-p`|`[PROCESS_ID]`|List all the files opened by a specified process id.|
|`-p`|`^[PROCESS_ID]`|List all the files that are not opened by a specified process id.|
|`+d`|`[PATH]`|List the processes with opened files under a specified directory|
|`+R`|<center>-</center>|List the files opened by parent process Id.|
### Help Command
Run below command to view the complete guide to `lsof` command.
```
man lsof
```

57
landing/docs/Linux-Commands/.recycle/069-the-bzip2-command.md
View File

@@ -1,57 +0,0 @@
# The `bzip2` command
The `bzip2` command lets you compress and decompress the files i.e. it helps in binding the files into a single file which takes less storage space as the original file use to take.
### Syntax:
```
bzip2 [OPTIONS] filenames ...
```
#### Note : Each file is replaced by a compressed version of itself, with the name original name of the file followed by extension bz2.
### Options and their Functionalities:
|**Option** |**Alias** |**Description** |
|:---|:---|:---|
|`-d`|`--decompress`|to decompress compressed file|
|`-f`|`--force`|to force overwrite an existing output file|
|`-h`|`--help`|to display the help message and exit|
|`-k`|`--keep`|to enable file compression, doesn't deletes the original input file|
|`-L`|`--license`|to display the license terms and conditions|
|`-q`|`--quiet`|to suppress non-essential warning messages|
|`-t`|`--test`|to check integrity of the specified .bz2 file, but don't want to decompress them|
|`-v`|`--erbose`|to display details for each compression operation|
|`-V`|`--version`|to display the software version|
|`-z`|`--compress`|to enable file compression, but deletes the original input file|
> #### By default, when bzip2 compresses a file, it deletes the original (or input) file. However, if you don't want that to happen, use the -k command line option.
### Examples:
1. To force compression:
```
bzip2 -z input.txt
```
**Note: This option deletes the original file also**
2. To force compression and also retain original input file:
```
bzip2 -k input.txt
```
3. To force decompression:
```
bzip2 -d input.txt.bz2
```
4. To test integrity of compressed file:
```
bzip2 -t input.txt.bz2
```
5. To show the compression ratio for each file processed:
```
bzip2 -v input.txt
```

30
landing/docs/Linux-Commands/.recycle/070-the-service-command.md
View File

@@ -1,30 +0,0 @@
# The `service` command
Service runs a System V init script in as predictable environment as possible, removing most environment variables and with current working directory set to /.
The SCRIPT parameter specifies a System V init script, located in /etc/init.d/SCRIPT. The supported values of COMMAND depend on the invoked script, service passes COMMAND and OPTIONS it to the init script unmodified. All scripts should support at least the start and stop commands. As a special case, if COMMAND is --full-restart, the script is run twice, first with the stop command, then with the start command.
The COMMAND can be at least start, stop, status, and restart.
service --status-all runs all init scripts, in alphabetical order, with the `status` command
Examples :
1. To check the status of all the running services:
```
service --status-all
```
2. To run a script
```
service SCRIPT-Name start
```
3. A more generalized command:
```
service [SCRIPT] [COMMAND] [OPTIONS]
```

25
landing/docs/Linux-Commands/.recycle/071-the-vmstat-command.md
View File

@@ -1,25 +0,0 @@
# The `vmstat` command
The `vmstat` command lets you monitor the performance of your system. It shows you information about your memory, disk, processes, CPU scheduling, paging, and block IO. This command is also referred to as **virtual memory statistic report**.
The very first report that is produced shows you the average details since the last reboot and after that, other reports are made which report over time.
### `vmstat`
![vmstat](https://imgur.com/9HZgBRN.png)
As you can see it is a pretty useful little command. The most important things that we see above are the `free`, which shows us the free space that is not being used, `si` shows us how much memory is swapped in every second in kB, and `so` shows how much memory is swapped out each second in kB as well.
### `vmstat -a`
If we run `vmstat -a`, it will show us the active and inactive memory of the system running.
![vmstat -a](https://imgur.com/LjL4tRh.png)
### `vmstat -d`
The `vmstat -d` command shows us all the disk statistics.
![vmstat -d](https://imgur.com/y3L0pNN.png)
As you can see this is a pretty useful little command that shows you different statistics about your virtual memory

57
landing/docs/Linux-Commands/.recycle/072-the-mpstat-command.md
View File

@@ -1,57 +0,0 @@
# The `mpstat` command
The `mpstat` command is used to report processor related statistics. It accurately displays the statistics of the CPU usage of the system and information about CPU utilization and performance.
### Syntax:
```
mpstat [options] [<interval> [<count>]]
```
#### Note : It initializes the first processor with CPU 0, the second one with CPU 1, and so on.
### Options and their Functionalities:
|**Option** |**Description** |
|-------------|----------------------------------------------------------------------|
|`-A` |to display all the detailed statistics |
|`-h` |to display mpstat help |
|`-I` |to display detailed interrupts statistics |
|`-n` |to report summary CPU statistics based on NUMA node placement |
|`-N` |to indicate the NUMA nodes for which statistics are to be reported |
|`-P` |to indicate the processors for which statistics are to be reported |
|`-o` |to display the statistics in JSON (Javascript Object Notation) format |
|`-T` |to display topology elements in the CPU report |
|`-u` |to report CPU utilization |
|`-v` |to display utilization statistics at the virtual processor level |
|`-V` |to display mpstat version |
|`-ALL` |to display detailed statistics about all CPUs |
### Examples:
1. To display processor and CPU statistics:
```
mpstat
```
2. To display processor number of all CPUs:
```
mpstat -P ALL
```
3. To get all the information which the tool may collect:
```
mpstat -A
```
4. To display CPU utilization by a specific processor:
```
mpstat -P 0
```
5. To display CPU usage with a time interval:
```
mpstat 1 5
```
**Note: This command will print 5 reports with 1 second time interval**

36
landing/docs/Linux-Commands/.recycle/073-the-ncdu-command.md
View File

@@ -1,36 +0,0 @@
# The `ncdu` Command
`ncdu` (NCurses Disk Usage) is a curses-based version of the well-known `du` command. It provides a fast way to see what directories are using your disk space.
## Example
1. Quiet Mode
```
ncdu -q
```
2. Omit mounted directories
```
ncdu -q -x
```
## Syntax
```
ncdu [-hqvx] [--exclude PATTERN] [-X FILE] dir
```
## Additional Flags and their Functionalities:
|Short Flag | Long Flag | Description|
|---|---|---|
| `-h`| - |Print a small help message|
| `-q`| - |Quiet mode. While calculating disk space, ncdu will update the screen 10 times a second by default, this will be decreased to once every 2 seconds in quiet mode. Use this feature to save bandwidth over remote connections.|
| `-v`| - |Print version.|
| `-x`| - |Only count files and directories on the same filesystem as the specified dir.|
| - | `--exclude PATTERN`|Exclude files that match PATTERN. This argument can be added multiple times to add more patterns.|
| `-X FILE`| `--exclude-from FILE`| Exclude files that match any pattern in FILE. Patterns should be separated by a newline.|

69
landing/docs/Linux-Commands/.recycle/074-the-uniq-command.md
View File

@@ -1,69 +0,0 @@
# The `uniq` command
The `uniq` command in Linux is a command line utility that reports or filters out the repeated lines in a file.
In simple words, `uniq` is the tool that helps you to detect the adjacent duplicate lines and also deletes the duplicate lines. It filters out the adjacent matching lines from the input file(that is required as an argument) and writes the filtered data to the output file .
### Examples:
In order to omit the repeated lines from a file, the syntax would be the following:
```
uniq kt.txt
```
In order to tell the number of times a line was repeated, the syntax would be the following:
```
uniq -c kt.txt
```
In order to print repeated lines, the syntax would be the following:
```
uniq -d kt.txt
```
In order to print unique lines, the syntax would be the following:
```
uniq -u kt.txt
```
In order to allows the N fields to be skipped while comparing uniqueness of the lines, the syntax would be the following:
```
uniq -f 2 kt.txt
```
In order to allows the N characters to be skipped while comparing uniqueness of the lines, the syntax would be the following:
```
uniq -s 5 kt.txt
```
In order to to make the comparison case-insensitive, the syntax would be the following:
```
uniq -i kt.txt
```
### Syntax:
```
uniq [OPTION] [INPUT[OUTPUT]]
```
### Possible options:
|**Flag** |**Description** |**Params** |
|:---|:---|:---|
|`-c`|It tells how many times a line was repeated by displaying a number as a prefix with the line.|-|
|`-d`|It only prints the repeated lines and not the lines which aren’t repeated.|-|
|`-i`|By default, comparisons done are case sensitive but with this option case insensitive comparisons can be made.|-|
|`-f`|It allows you to skip N fields(a field is a group of characters, delimited by whitespace) of a line before determining uniqueness of a line.|N|
|`-s`|It doesn’t compares the first N characters of each line while determining uniqueness. This is like the -f option, but it skips individual characters rather than fields.|N|
|`-u`|It allows you to print only unique lines.|-|
|`-z`|It will make a line end with 0 byte(NULL), instead of a newline.|-|
|`-w`|It only compares N characters in a line.|N|
|`--help`|It displays a help message and exit.|-|
|`--version`|It displays version information and exit.|-|

103
landing/docs/Linux-Commands/.recycle/075-the-rpm-command.md
View File

@@ -1,103 +0,0 @@
# The `RPM` command
`rpm` - RPM Package Manager
`rpm` is a powerful __Package Manager__, which can be used to build, install, query, verify, update, and erase individual software packages. A __package__ consists of an archive of files and meta-data used to install and erase the archive files. The meta-data includes helper scripts, file attributes, and descriptive information about the package. Packages come in two varieties: binary packages, used to encapsulate software to be installed, and source packages, containing the source code and recipe necessary to produce binary packages.
One of the following basic modes must be selected: __Query, Verify, Signature Check, Install/Upgrade/Freshen, Uninstall, Initialize Database, Rebuild Database, Resign, Add Signature, Set Owners/Groups, Show Querytags, and Show Configuration.__
**General Options**
These options can be used in all the different modes.
|Short Flag| Long Flag| Description|
|---|---|---|
| -? | --help| Print a longer usage message then normal.|
| - |--version |Print a single line containing the version number of rpm being used.|
| - | --quiet | Print as little as possible - normally only error messages will be displayed.|
| -v | - | Print verbose information - normally routine progress messages will be displayed.|
| -vv | - | Print lots of ugly debugging information.|
| - | --rcfile FILELIST | Each of the files in the colon separated FILELIST is read sequentially by rpm for configuration information. Only the first file in the list must exist, and tildes will be expanded to the value of $HOME. The default FILELIST is /usr/lib/rpm/rpmrc:/usr/lib/rpm/redhat/rpmrc:/etc/rpmrc:~/.rpmrc. |
| - | --pipe CMD | Pipes the output of rpm to the command CMD. |
| - | --dbpath DIRECTORY | Use the database in DIRECTORY rather than the default path /var/lib/rpm |
| - | --root DIRECTORY | Use the file system tree rooted at DIRECTORY for all operations. Note that this means the database within DIRECTORY will be used for dependency checks and any scriptlet(s) (e.g. %post if installing, or %prep if building, a package) will be run after a chroot(2) to DIRECTORY. |
| -D | --define='MACRO EXPR' | Defines MACRO with value EXPR.|
| -E | --eval='EXPR' | Prints macro expansion of EXPR. |
# Synopsis
## Querying and Verifying Packages:
```
rpm {-q|--query} [select-options] [query-options]
rpm {-V|--verify} [select-options] [verify-options]
rpm --import PUBKEY ...
rpm {-K|--checksig} [--nosignature] [--nodigest] PACKAGE_FILE ...
```
## Installing, Upgrading, and Removing Packages:
```
rpm {-i|--install} [install-options] PACKAGE_FILE ...
rpm {-U|--upgrade} [install-options] PACKAGE_FILE ...
rpm {-F|--freshen} [install-options] PACKAGE_FILE ...
rpm {-e|--erase} [--allmatches] [--nodeps] [--noscripts] [--notriggers] [--test] PACKAGE_NAME ...
```
## Miscellaneous:
```
rpm {--initdb|--rebuilddb}
rpm {--addsign|--resign} PACKAGE_FILE...
rpm {--querytags|--showrc}
rpm {--setperms|--setugids} PACKAGE_NAME .
```
### query-options
```
[--changelog] [-c,--configfiles] [-d,--docfiles] [--dump]
[--filesbypkg] [-i,--info] [--last] [-l,--list]
[--provides] [--qf,--queryformat QUERYFMT]
[-R,--requires] [--scripts] [-s,--state]
[--triggers,--triggerscripts]
```
### verify-options
```
[--nodeps] [--nofiles] [--noscripts]
[--nodigest] [--nosignature]
[--nolinkto] [--nofiledigest] [--nosize] [--nouser]
[--nogroup] [--nomtime] [--nomode] [--nordev]
[--nocaps]
```
### install-options
```
[--aid] [--allfiles] [--badreloc] [--excludepath OLDPATH]
[--excludedocs] [--force] [-h,--hash]
[--ignoresize] [--ignorearch] [--ignoreos]
[--includedocs] [--justdb] [--nodeps]
[--nodigest] [--nosignature] [--nosuggest]
[--noorder] [--noscripts] [--notriggers]
[--oldpackage] [--percent] [--prefix NEWPATH]
[--relocate OLDPATH=NEWPATH]
[--replacefiles] [--replacepkgs]
[--test]
```

69
landing/docs/Linux-Commands/.recycle/076-the-scp-command.md
View File

@@ -1,69 +0,0 @@
# The `scp` command
SCP (secure copy) is a command-line utility that allows you to securely copy files and directories between two locations.
Both the files and passwords are encrypted so that anyone snooping on the traffic doesn't get anything sensitive.
### Different ways to copy a file or directory:
- From local system to a remote system.
- From a remote system to a local system.
- Between two remote systems from the local system.
### Examples:
1. To copy the files from a local system to a remote system:
```
scp /home/documents/local-file root@{remote-ip-address}:/home/
```
2. To copy the files from a remote system to the local system:
```
scp root@{remote-ip-address}:/home/remote-file /home/documents/
```
3. To copy the files between two remote systems from the local system.
```
scp root@{remote1-ip-address}:/home/remote-file root@{remote2-ip-address}/home/
```
4. To copy file though a jump host server.
```
scp /home/documents/local-file -oProxyJump=<jump-host-ip> root@{remote-ip-address}/home/
```
On newer version of scp on some machines you can use the above command with a `-J` flag.
```
scp /home/documents/local-file -J <jump-host-ip> root@{remote-ip-address}/home/
```
### Syntax:
```
scp [OPTION] [user@]SRC_HOST:]file1 [user@]DEST_HOST:]file2
```
- `OPTION` - scp options such as cipher, ssh configuration, ssh port, limit, recursive copy …etc.
- `[user@]SRC_HOST:]file1` - Source file
- `[user@]DEST_HOST:]file2` - Destination file
Local files should be specified using an absolute or relative path, while remote file names should include a user and host specification.
scp provides several that control every aspect of its behaviour. The most widely used options are:
|**Short Flag** |**Long Flag** |**Description** |
|:---|:---|:---|
|`-P`|<center>-</center>|Specifies the remote host ssh port.|
|`-p`|<center>-</center>|Preserves files modification and access times.|
|`-q`|<center>-</center>|Use this option if you want to suppress the progress meter and non-error messages.|
|`-C`|<center>-</center>|This option forces scp to compresses the data as it is sent to the destination machine.|
|`-r`|<center>-</center>|This option tells scp to copy directories recursively.|
### Before you begin
The `scp` command relies on `ssh` for data transfer, so it requires an `ssh key` or `password` to authenticate on the remote systems.
The `colon (:)` is how scp distinguish between local and remote locations.
To be able to copy files, you must have at least read permissions on the source file and write permission on the target system.
Be careful when copying files that share the same name and location on both systems, `scp` will overwrite files without warning.
When transferring large files, it is recommended to run the scp command inside a `screen` or `tmux` session.

76
landing/docs/Linux-Commands/.recycle/078-the-split-command.md
View File

@@ -1,76 +0,0 @@
# The `split` command
The `split` command in Linux is used to split a file into smaller files.
### Examples
1. Split a file into a smaller file using file name
```
split filename.txt
```
2. Split a file named filename into segments of 200 lines beginning with prefix file
```
split -l 200 filename file
```
This will create files of the name fileaa, fileab, fileac, filead, etc. of 200 lines.
3. Split a file named filename into segments of 40 bytes with prefix file
```
split -b 40 filename file
```
This will create files of the name fileaa, fileab, fileac, filead, etc. of 40 bytes.
4. Split a file using --verbose to see the files being created.
```
split filename.txt --verbose
```
### Syntax:
```
split [options] filename [prefix]
```
### Additional Flags and their Functionalities
|**Short Flag** |**Long Flag** |**Description** |
|:---|:---|:---|
|`-a`|`--suffix-length=N`|Generate suffixes of length N (default 2)|
||`--additional-suffix=SUFFIX`|Append an additional SUFFIX to file names|
|`-b`|`--bytes=SIZE`|Put SIZE bytes per output file|
|`-C`|`--line-bytes=SIZE`|Put at most SIZE bytes of records per output file|
|`-d`| |Use numeric suffixes starting at 0, not alphabetic|
||`--numeric-suffixes[=FROM]`|Same as -d, but allow setting the start value|
|`-x`||Use hex suffixes starting at 0, not alphabetic|
||`--hex-suffixes[=FROM]`|Same as -x, but allow setting the start value|
|`-e`|`--elide-empty-files`|Do not generate empty output files with '-n'|
||`--filter=COMMAND`|Write to shell COMMAND;<br>file name is $FILE|
|`-l`|`--lines=NUMBER`|Put NUMBER lines/records per output file|
|`-n`|`--number=CHUNKS`|Generate CHUNKS output files;<br>see explanation below|
|`-t`|`--separator=SEP`|Use SEP instead of newline as the record separator;<br>'\0' (zero) specifies the NUL character|
|`-u`|`--unbuffered`|Immediately copy input to output with '-n r/...'|
||`--verbose`|Print a diagnostic just before each<br>output file is opened|
||`--help`|Display this help and exit|
||`--version`|Output version information and exit|
The SIZE argument is an integer and optional unit (example: 10K is 10*1024).
Units are K,M,G,T,P,E,Z,Y (powers of 1024) or KB,MB,... (powers of 1000).
CHUNKS may be:
|**CHUNKS** |**Description** |
|:---|:---|
|`N`|Split into N files based on size of input|
|`K/N`|Output Kth of N to stdout|
|`l/N`|Split into N files without splitting lines/records|
|`l/K/N`|Output Kth of N to stdout without splitting lines/records|
|`r/N`|Like 'l' but use round robin distribution|
|`r/K/N`|Likewise but only output Kth of N to stdout|

61
landing/docs/Linux-Commands/.recycle/079-the-stat-command.md
View File

@@ -1,61 +0,0 @@
# The `stat` command
The `stat` command lets you display file or file system status. It gives you useful information about the file (or directory) on which you use it.
### Examples:
1. Basic command usage
```
stat file.txt
```
2. Use the `-c` (or `--format`) argument to only display information you want to see (here, the total size, in bytes)
```
stat file.txt -c %s
```
### Syntax:
```
stat [OPTION] [FILE]
```
### Additional Flags and their Functionalities:
| Short Flag | Long Flag | Description |
| ---------- | ----------------- | ----------------------------------------------------------------------------- |
| `-L` | `--dereference` | Follow links |
| `-f` | `--file-system` | Display file system status instead of file status |
| `-c` | `--format=FORMAT` | Specify the format (see below) |
| `-t` | `--terse` | Print the information in terse form |
| - | `--cached=MODE` | Specify how to use cached attributes. Can be: `always`, `never`, or `default` |
| - | `--printf=FORMAT` | Like `--format`, but interpret backslash escapes (`\n`, `\t`, ...) |
| - | `--help` | Display the help and exit |
| - | `--version` | Output version information and exit |
### Example of Valid Format Sequences for Files:
| Format | Description |
| ------ | ---------------------------------------------------- |
| `%a` | Permission bits in octal |
| `%A` | Permission bits and file type in human readable form |
| `%d` | Device number in decimal |
| `%D` | Device number in hex |
| `%F` | File type |
| `%g` | Group ID of owner |
| `%G` | Group name of owner |
| `%h` | Number of hard links |
| `%i` | Inode number |
| `%m` | Mount point |
| `%n` | File name |
| `%N` | Quoted file name with dereference if symbolic link |
| `%s` | Total size, in bytes |
| `%u` | User ID of owner |
| `%U` | User name of owner |
| `%w` | Time of file birth, human-readable; - if unknown |
| `%x` | Time of last access, human-readable |
| `%y` | Time of last data modification, human-readable |
| `%z` | Time of last status change, human-readable |

93
landing/docs/Linux-Commands/.recycle/083-the-ionice-command.md
View File

@@ -1,93 +0,0 @@
# The `ionice` command
The `ionice` command is used to set or get process I/O scheduling class and priority.
If no arguments are given , `ionice` will query the current I/O scheduling class and priority for that process.
## Usage
```
ionice [options] -p <pid>
```
```
ionice [options] -P <pgid>
```
```
ionice [options] -u <uid>
```
```
ionice [options] <command>
```
## A process can be of three scheduling classes:
- ### Idle
A program with idle I/O priority will only get disk time when `no other program has asked for disk I/O for a defined grace period`.
The impact of idle processes on normal system actively should be `zero`.
This scheduling class `doesn’t take priority` argument.
Presently this scheduling class is permitted for an `ordinary user (since kernel 2.6.25)`.
- ### Best Effort
This is `effective` scheduling class for any process that has `not asked for a specific I/O priority`.
This class `takes priority argument from 0-7`, with `lower` number being `higher priority`.
Programs running at the same best effort priority are served in `round- robbin fashion`.
Note that before kernel 2.6.26 a process that has not asked for an I/O priority formally uses “None” as scheduling class , but the io schedular will treat such processes as if it were in the best effort class.
The priority within best effort class will be dynamically derived form the CPU nice level of the process : io_priority = ( cpu_nice + 20 ) / 5/
for kernels after 2.6.26 with CFQ I/O schedular a process that has not asked for sn io priority inherits CPU scheduling class.
`The I/O priority is derived from the CPU nice level of the process` ( smr sd before kernel 2.6.26 ).
- ### Real Time
The real time schedular class is `given first access to disk, regardless of what else is going on in the system`.
Thus the real time class needs to be used with some care, as it cans tarve other processes .
As with the best effort class, `8 priority levels are defined denoting how big a time slice a given process will receive on each scheduling window`.
This scheduling class is `not permitted for an ordinary user(non-root)`.
## Options
| Options | Description |
|---|---|
| -c, --class <class> | name or number of scheduling class, 0: none, 1: realtime, 2: best-effort, 3: idle|
| -n, --classdata <num> | priority (0..7) in the specified scheduling class,only for the realtime and best-effort classes|
| -p, --pid <pid>... | act on these already running processes|
| -P, --pgid <pgrp>... | act on already running processes in these groups|
| -t, --ignore | ignore failures|
| -u, --uid <uid>... | act on already running processes owned by these users|
| -h, --help | display this help|
| -V, --version | display version|
For more details see ionice(1).
## Examples
| Command | O/P |Explanation|
|---|---|---|
|`$ ionice` |*none: prio 4*|Running alone `ionice` will give the class and priority of current process |
|`$ ionice -p 101`|*none : prio 4*|Give the details(*class : priority*) of the process specified by given process id|
|`$ ionice -p 2` |*none: prio 4*| Check the class and priority of process with pid 2 it is none and 4 resp.|
|`$ ionice -c2 -n0 -p2`|2 ( best-effort ) priority 0 process 2 | Now lets set process(pid) 2 as a best-effort program with highest priority|
|$ `ionice` -p 2|best-effort : prio 0| Now if I check details of Process 2 you can see the updated one|
|$ `ionice` /bin/ls||get priority and class info of bin/ls |
|$ `ionice` -n4 -p2||set priority 4 of process with pid 2 |
|$ `ionice` -p 2| best-effort: prio 4| Now observe the difference between the command ran above and this one we have changed priority from 0 to 4|
|$ `ionice` -c0 -n4 -p2|ionice: ignoring given class data for none class|(Note that before kernel 2.6.26 a process that has not asked for an I/O priority formally uses “None” as scheduling class , |
|||but the io schedular will treat such processes as if it were in the best effort class. )|
|||-t option : ignore failure|
|$ `ionice` -c0 -n4 -p2 -t| | For ignoring the warning shown above we can use -t option so it will ignore failure |
## Conclusion
Thus we have successfully learnt about `ionice` command.

Some files were not shown because too many files have changed in this diff Show More