John Freier - User contributions [en]

Podman

2026-05-14T20:27:03Z

Jfreier:

== Podman ==

'''Start Podman'''
podman machine start

== Images ==

'''List Images'''
podman images

'''Pull an image'''
podman pull docker.io/library/httpd

'''Run an image'''
podman run -dt -p 8080:80/tcp docker.io/library/httpd

podman run -it --entrypoint="/bin/sh" docker.io/library/httpd

podman run -it -v /home/user/project:/app --entrypoint="/bin/bash" python:3.9.13-buster

* The -d will run the container in detach mode, so you wont see any console.
* The -t command connects the container to your terminal so it will not exit after it runs.

The following command with -rm will clean up the container and remove any persists data.
podman run -rm docker.io/library/httpd

To commit a container to the list of podman images.
podman commit {id}

'''Continue a container'''
This will start back up an exited container, it will continue where you left off.
podman start {id}
To start with shell.
podman start -ai {id}

'''Get in to a running container'''
podman exec -it {id} /bin/sh

'''List running images'''
podman ps -a

'''Remove Image'''
podman rmi {image_sha}

'''Load an Image'''
Worked
cat cs-oci.tar | podman load

Did not work.
podman load oci-archive:cs-oci.tar:latest

'''Update the tag for an image'''
podman tag e7b8dd57dec6 cs:latest

== Containers ==

'''List all containers'''
podman ps -a

'''Remove Container'''
podman rm ff22b3bfecc1

'''Remove all stopped Containers'''
podman container prune

== Pods ==

'''Create a pod'''
podman pod create --name mypod

'''List pods'''
podman pod list

'''Start pod'''
podman pod start {podname}

'''Stop pod'''
podman pod stop {podname}

'''List all processes with pods'''
podman ps -a --pod

== Volume ==

Volume in Podman can be a virtual volume that is mounted through Podman. This virtual volume can be exported or imported as well.

You can also setup to point to a local host directory but because Podman is rootless Podman will need access to the directory, by either permissions on the directory or the user that runs the container from Podman.

'''Create Virtual Volume'''
podman volume create myvolume

'''Export Virtual Volume'''
podman volume export myvolume --output myvolume.tar

== Repositories ==
To login to a repository.
The below example is for harbor but could be used for others.
podman login --username JDOE --password {cli_secret} https://registry.harbor-url.com/

== Build ==

To build and avoid any cached layers use the following.
podman build --no-cache -t $container_name:$container_tag .

== Logs ==

'''View Logs'''
podman logs ff22b3bfecc1

'''Stop the latest container'''

podman stop ff22b3bfecc1

== Kube ==

'''Generate kubernetes yaml'''
podman generate kube -f infra.yaml mypod

'''Load kubernetes yaml'''
podman play kube infra.yaml

'''Kubernetes File'''
# Kubernetes setup for CS.
apiVersion: v1
kind: ConfigMap
metadata:
name: cs-config
data:
CS_DATABASE_MONGODB_EMBEDED_ENABLED: "false"
SPRING_DATA_MONGODB_HOST: "localhost"
---
apiVersion: v1
kind: Pod
metadata:
name: mypod
labels:
app: mypod
spec:
containers:
- name: database
image: docker.io/library/mongo:4.4.13
securityContext:
runAsUser: 0
volumeMounts:
- name: mongodb-data-volume
mountPath: /data/db
- name: application
image: cs:latest
ports:
- containerPort: 8080
hostPort: 8080
envFrom:
- configMapRef:
name: cs-config
volumes:
- name: mongodb-data-volume
persistentVolumeClaim:
claimName: mongodb-data-storage

== Examples ==

'''Example run MongoDB'''
podman run \
--detach \
--publish 27017:27017 \
--userns=keep-id \
--volume ./mongo-data:/data/db \
--name some-mongo \
mongo:4.4.13

# --detach, -d - Detached mode: run the container in the background and print the new container ID. The default is false
# --publish, -p - Publish a container’s port, or range of ports, to the host.
# --userns - Because podman runs rootless we need to assign a user that can access the local volumn. This sets the podman user to the same user who ran the podman command.
# --volume, -v - Create a bind mount.
# --name - Assign a name to the container.

'''Example running with pods'''
This is a test to see how apps can talk between each other in a podman network within a pod.

Create the pod
podman pod create --userns=keep-id --publish 8080:8080 --name mypod

podman run --detach --volume ./mongo-data:/data/db --pod mypod --name some-mongo mongo:4.4.13

podman run --detach --pod mypod --name myapp -e SPRING_DATA_MONGODB_HOST="localhost" -e CS_DATABASE_MONGODB_EMBEDED_ENABLED="false" e7b8dd57dec6

Not used - only for debug
podman run -it --pod mypod --name myapp --volume ./config:/config --entrypoint "/bin/sh" e7b8dd57dec6

Postgresql

2026-05-11T14:28:31Z

Jfreier:

== Test Database Connection ==
This is a way to test the database connection.
./pg_isready -h localhost -p 5432

== Application Structure ==
Log location
./data/log/

== OSX ==
The Postgres app live here on OSX
/Library/PostgreSQL/11

Start
sudo -u postgres ./bin/pg_ctl -D ./data start

Stop
sudo -u postgres ./bin/pg_ctl -D ./data stop

FYI, haven't tried but look like a nicer app to control Postgres is https://postgresapp.com.

If you are not using the system registered database you can all simply use the following commands.

pg_ctl -D ./data start
pg_ctl -D ./data stop

== Initialize a database directory ==
To initialize a database directory use the following command.

initdb -D <data_directory>

== Environment Path ==
To add PostgreSQL in to your environment path.

export POSTGRESQL_HOME=/Library/PostgreSQL/11
PATH=$PATH:$POSTGRESQL_HOME/bin

== Debian ==
You can start Postgres in Debian using
/etc/init.d/postgresql start

Create a database and user
sudo su - postgres
createdb testdb
createuser testdb

To create a password for the user either use
createuser testdb --pwprompt
or
psql
ALTER USER 'testdb' WITH PASSWORD 'testdb';

To have the new user be a superuser add the following.
createuser --superuser testdb --pwprompt

== Run file and commands from CLI ==
PSQL will ask for your password every time unless you set it as an environment variable.
export PGPASSWORD=Password123

To run a command.
psql -U user_name -d database_name -c "SELECT * FROM tblExample"

To run a file.
psql -U user_name -d database_name -f ./file.sql

== Issues ==

Error Connecting to database FATAL : no pg_hba.conf entry for host
I had to add the host ip address into the pg_hba.conf file.

location of file: ./data/pg_hba.conf

Added the following line and then restarted Postgres.
host all all 10.225.41.95/24 md5

== Describe a table ==
You can query the 'information_schema.columns' table to find internal table information.

This is a sample command to find information about a table.
SELECT table_name, column_name, data_type
FROM information_schema.columns
WHERE table_name='TABLE_A';

== Top 10 rows ==
This is to get the top 10 rows.
select *
from table_a
fetch first 10 rows only;

== PSQL VIM ==
Tips for editing script and running them in th PSQL command.

1. Edit a script in vim. Once logged in use the following command.
\e

2. Multiple windows.
In 1 window connect using the psql tool and run scripts using the following command.
\o ./sql.out \i ./test.sql

In 2 window using VIM, edit the test.sql file and open a new tab of sql.out.
Then refresh the buffer using
:e

== PSQL Sequence ==
To update the sequence to a new value.
SELECT setval('sequence_name', 100);

Java maven

2026-05-06T19:18:03Z

Jfreier:

Using Maven to help compile Java projects.

== Run Tests ==
To run a single test.
mvn test -Dtest=ClassName#methodName

== Run Test with full stackTrace messages ==
To show the full error message when something goes wrong in a test.
mvn test -Dtest=ClassName#methodName -DtrimStackTrace=false

== Check dependencies ==
To check dependencies in the pom and versions.

mvn dependency:list | grep log4j

mvn dependency:tree | grep "bcprov-jdk18on" -C 10

Git

2026-04-28T16:34:13Z

Jfreier:

== Rebase ==
When you are on a branch, you get
git rebase master

You will get conflicts with the remote origin if you try and push. Here are some ways to solve this.

This will force the remote origin to stay up to date with your branch. But be aware, if there are more people working on the feature branch then just you, you may overwrite code.
git push --force origin feature_branch

With force with lease, git will warn you if anyone else has committed any code, this helps to prevent overwriting someones code.
git push --force-with-lease

Another good option after rebase with master is to just delete the branch on the remote origin, and then recreate it.
git checkout myFeature
git rebase master
git push origin --delete myFeature
git push origin myFeature

== Squash feature branch ==
This squashes all the commits in to one.
git merge --squash feature

and then you need to commit the new squashed changes.
get commit -m "squashed changes merged in."

== Squash Commits ==
This squashes the last 3 commits.
git reset --soft HEAD~3
git commit -m 'new commit message'

== View the logs ==
A another way to view the logs.
git log --oneline --decorate --graph --all

== Add all untracked changes. ==
Here is a couple of commands to help with backing things up.
This will add all untracked changes for a file type.
git ls-files --other | grep ".md" | xargs git add

This will add all tracked changes for a file type.
git ls-files | grep ".md" | xargs git add

== Sign with GPG ==
List your keys
gpg --list-secret-keys --keyid-format=long

Update git to use a specific key.
git config --global user.signingkey 3AA5C34371567BD2

Sign all commits by default.
git config --global commit.gpgsign true

== Stash ==
Add a name to your stash.
git stash push -m "your_custom_name"

List your stash.
git stash list

Apply your stash.
git stash apply stash^{/your_custom_name}

Apply and remove your stash
git stash pop stash^{/your_custom_name}

Git

2026-04-28T16:33:50Z

Jfreier:

== Rebase ==
When you are on a branch, you get
git rebase master

You will get conflicts with the remote origin if you try and push. Here are some ways to solve this.

This will force the remote origin to stay up to date with your branch. But be aware, if there are more people working on the feature branch then just you, you may overwrite code.
git push --force origin feature_branch

With force with lease, git will warn you if anyone else has committed any code, this helps to prevent overwriting someones code.
git push --force-with-lease

Another good option after rebase with master is to just delete the branch on the remote origin, and then recreate it.
git checkout myFeature
git rebase master
git push origin --delete myFeature
git push origin myFeature

== Squash feature branch ==
This squashes all the commits in to one.
git merge --squash feature

and then you need to commit the new squashed changes.
get commit -m "squashed changes merged in."

== Squash Commits ==
This squashes the last 3 commits.
git reset --soft HEAD~3
git commit -m 'new commit message'

== View the logs ==
A another way to view the logs.
git log --oneline --decorate --graph --all

== Add all untracked changes. ==
Here is a couple of commands to help with backing things up.
This will add all untracked changes for a file type.
git ls-files --other | grep ".md" | xargs git add

This will add all tracked changes for a file type.
git ls-files | grep ".md" | xargs git add

==Sign with GPG
List your keys
gpg --list-secret-keys --keyid-format=long

Update git to use a specific key.
git config --global user.signingkey 3AA5C34371567BD2

Sign all commits by default.
git config --global commit.gpgsign true

==Stash
Add a name to your stash.
git stash push -m "your_custom_name"

List your stash.
git stash list

Apply your stash.
git stash apply stash^{/your_custom_name}

Apply and remove your stash
git stash pop stash^{/your_custom_name}

Git

2026-04-28T16:33:35Z

Jfreier:

== Rebase ==
When you are on a branch, you get
git rebase master

You will get conflicts with the remote origin if you try and push. Here are some ways to solve this.

This will force the remote origin to stay up to date with your branch. But be aware, if there are more people working on the feature branch then just you, you may overwrite code.
git push --force origin feature_branch

With force with lease, git will warn you if anyone else has committed any code, this helps to prevent overwriting someones code.
git push --force-with-lease

Another good option after rebase with master is to just delete the branch on the remote origin, and then recreate it.
git checkout myFeature
git rebase master
git push origin --delete myFeature
git push origin myFeature

== Squash feature branch ==
This squashes all the commits in to one.
git merge --squash feature

and then you need to commit the new squashed changes.
get commit -m "squashed changes merged in."

== Squash Commits ==
This squashes the last 3 commits.
git reset --soft HEAD~3
git commit -m 'new commit message'

== View the logs ==
A another way to view the logs.
git log --oneline --decorate --graph --all

== Add all untracked changes. ==
Here is a couple of commands to help with backing things up.
This will add all untracked changes for a file type.
git ls-files --other | grep ".md" | xargs git add

This will add all tracked changes for a file type.
git ls-files | grep ".md" | xargs git add

== Sign with GPG
List your keys
gpg --list-secret-keys --keyid-format=long

Update git to use a specific key.
git config --global user.signingkey 3AA5C34371567BD2

Sign all commits by default.
git config --global commit.gpgsign true

== Stash
Add a name to your stash.
git stash push -m "your_custom_name"

List your stash.
git stash list

Apply your stash.
git stash apply stash^{/your_custom_name}

Apply and remove your stash
git stash pop stash^{/your_custom_name}

Podman

2026-03-02T17:52:23Z

Jfreier:

== Podman ==

'''Start Podman'''
podman machine start

== Images ==

'''List Images'''
podman images

'''Pull an image'''
podman pull docker.io/library/httpd

'''Run an image'''
podman run -dt -p 8080:80/tcp docker.io/library/httpd

podman run -it --entrypoint="/bin/sh" docker.io/library/httpd

podman run -it -v /home/user/project:/app --entrypoint="/bin/bash" python:3.9.13-buster

* The -d will run the container in detach mode, so you wont see any console.
* The -t command connects the container to your terminal so it will not exit after it runs.

The following command with -rm will clean up the container and remove any persists data.
podman run -rm docker.io/library/httpd

To commit a container to the list of podman images.
podman commit {id}

'''Continue a container'''
This will start back up an exited container, it will continue where you left off.
podman start {id}

'''Get in to a running container'''
podman exec -it {id} /bin/sh

'''List running images'''
podman ps -a

'''Remove Image'''
podman rmi {image_sha}

'''Load an Image'''
Worked
cat cs-oci.tar | podman load

Did not work.
podman load oci-archive:cs-oci.tar:latest

'''Update the tag for an image'''
podman tag e7b8dd57dec6 cs:latest

== Containers ==

'''List all containers'''
podman ps -a

'''Remove Container'''
podman rm ff22b3bfecc1

'''Remove all stopped Containers'''
podman container prune

== Pods ==

'''Create a pod'''
podman pod create --name mypod

'''List pods'''
podman pod list

'''Start pod'''
podman pod start {podname}

'''Stop pod'''
podman pod stop {podname}

'''List all processes with pods'''
podman ps -a --pod

== Volume ==

Volume in Podman can be a virtual volume that is mounted through Podman. This virtual volume can be exported or imported as well.

You can also setup to point to a local host directory but because Podman is rootless Podman will need access to the directory, by either permissions on the directory or the user that runs the container from Podman.

'''Create Virtual Volume'''
podman volume create myvolume

'''Export Virtual Volume'''
podman volume export myvolume --output myvolume.tar

== Repositories ==
To login to a repository.
The below example is for harbor but could be used for others.
podman login --username JDOE --password {cli_secret} https://registry.harbor-url.com/

== Build ==

To build and avoid any cached layers use the following.
podman build --no-cache -t $container_name:$container_tag .

== Logs ==

'''View Logs'''
podman logs ff22b3bfecc1

'''Stop the latest container'''

podman stop ff22b3bfecc1

== Kube ==

'''Generate kubernetes yaml'''
podman generate kube -f infra.yaml mypod

'''Load kubernetes yaml'''
podman play kube infra.yaml

'''Kubernetes File'''
# Kubernetes setup for CS.
apiVersion: v1
kind: ConfigMap
metadata:
name: cs-config
data:
CS_DATABASE_MONGODB_EMBEDED_ENABLED: "false"
SPRING_DATA_MONGODB_HOST: "localhost"
---
apiVersion: v1
kind: Pod
metadata:
name: mypod
labels:
app: mypod
spec:
containers:
- name: database
image: docker.io/library/mongo:4.4.13
securityContext:
runAsUser: 0
volumeMounts:
- name: mongodb-data-volume
mountPath: /data/db
- name: application
image: cs:latest
ports:
- containerPort: 8080
hostPort: 8080
envFrom:
- configMapRef:
name: cs-config
volumes:
- name: mongodb-data-volume
persistentVolumeClaim:
claimName: mongodb-data-storage

== Examples ==

'''Example run MongoDB'''
podman run \
--detach \
--publish 27017:27017 \
--userns=keep-id \
--volume ./mongo-data:/data/db \
--name some-mongo \
mongo:4.4.13

# --detach, -d - Detached mode: run the container in the background and print the new container ID. The default is false
# --publish, -p - Publish a container’s port, or range of ports, to the host.
# --userns - Because podman runs rootless we need to assign a user that can access the local volumn. This sets the podman user to the same user who ran the podman command.
# --volume, -v - Create a bind mount.
# --name - Assign a name to the container.

'''Example running with pods'''
This is a test to see how apps can talk between each other in a podman network within a pod.

Create the pod
podman pod create --userns=keep-id --publish 8080:8080 --name mypod

podman run --detach --volume ./mongo-data:/data/db --pod mypod --name some-mongo mongo:4.4.13

podman run --detach --pod mypod --name myapp -e SPRING_DATA_MONGODB_HOST="localhost" -e CS_DATABASE_MONGODB_EMBEDED_ENABLED="false" e7b8dd57dec6

Not used - only for debug
podman run -it --pod mypod --name myapp --volume ./config:/config --entrypoint "/bin/sh" e7b8dd57dec6

Podman

2026-02-19T16:29:00Z

Jfreier: /* Containers */

== Podman ==

'''Start Podman'''
podman machine start

== Images ==

'''List Images'''
podman images

'''Pull an image'''
podman pull docker.io/library/httpd

'''Run an image'''
podman run -dt -p 8080:80/tcp docker.io/library/httpd

podman run -it --entrypoint="/bin/sh" docker.io/library/httpd

podman run -it -v /home/user/project:/app --entrypoint="/bin/bash" python:3.9.13-buster

* The -d will run the container in detach mode, so you wont see any console.
* The -t command connects the container to your terminal so it will not exit after it runs.

The following command with -rm will clean up the container and remove any persists data.
podman run -rm docker.io/library/httpd

To commit a container to the list of podman images.
podman commit {id}

'''Continue a container'''
This will start back up an exited container, it will continue where you left off.
podman start {id}

'''Get in to a running container'''
podman exec -it {id} /bin/sh

'''List running images'''
podman ps -a

'''Remove Image'''
podman rmi {image_sha}

'''Load an Image'''
Worked
cat cs-oci.tar | podman load

Did not work.
podman load oci-archive:cs-oci.tar:latest

'''Update the tag for an image'''
podman tag e7b8dd57dec6 cs:latest

== Containers ==

'''List all containers'''
podman ps -a

'''Remove Container'''
podman rm ff22b3bfecc1

'''Remove all stopped Containers'''
podman container prune

== Pods ==

'''Create a pod'''
podman pod create --name mypod

'''List pods'''
podman pod list

'''Start pod'''
podman pod start {podname}

'''Stop pod'''
podman pod stop {podname}

'''List all processes with pods'''
podman ps -a --pod

== Volume ==

Volume in Podman can be a virtual volume that is mounted through Podman. This virtual volume can be exported or imported as well.

You can also setup to point to a local host directory but because Podman is rootless Podman will need access to the directory, by either permissions on the directory or the user that runs the container from Podman.

'''Create Virtual Volume'''
podman volume create myvolume

'''Export Virtual Volume'''
podman volume export myvolume --output myvolume.tar

== Repositories ==
To login to a repository.
The below example is for harbor but could be used for others.
podman login --username JDOE --password {cli_secret} https://registry.harbor-url.com/

== Build ==

To build and avoid any cached layers use the following.
podman build --no-cache -t $container_name:$container_tag .

== Logs ==

'''View Logs'''
podman logs ff22b3bfecc1

'''Stop the latest container'''

podman stop ff22b3bfecc1

== Kube ==

'''Generate kubernetes yaml'''
podman generate kube -f infra.yaml mypod

'''Load kubernetes yaml'''
podman play kube infra.yaml

'''Kubernetes File'''
# Kubernetes setup for CS.
apiVersion: v1
kind: ConfigMap
metadata:
name: cs-config
data:
CS_DATABASE_MONGODB_EMBEDED_ENABLED: "false"
SPRING_DATA_MONGODB_HOST: "localhost"
---
apiVersion: v1
kind: Pod
metadata:
name: mypod
labels:
app: mypod
spec:
containers:
- name: database
image: docker.io/library/mongo:4.4.13
securityContext:
runAsUser: 0
volumeMounts:
- name: mongodb-data-volume
mountPath: /data/db
- name: application
image: cs:latest
ports:
- containerPort: 8080
hostPort: 8080
envFrom:
- configMapRef:
name: cs-config
volumes:
- name: mongodb-data-volume
persistentVolumeClaim:
claimName: mongodb-data-storage

== Examples ==

'''Example run MongoDB'''
podman run \
--detach \
--publish 27017:27017 \
--userns=keep-id \
--volume ./mongo-data:/data/db \
--name some-mongo \
mongo:4.4.13

# --detach, -d - Detached mode: run the container in the background and print the new container ID. The default is false
# --publish, -p - Publish a container’s port, or range of ports, to the host.
# --userns - Because podman runs rootless we need to assign a user that can access the local volumn. This sets the podman user to the same user who ran the podman command.
# --volume, -v - Create a bind mount.
# --name - Assign a name to the container.

'''Example running with pods'''
This is a test to see how apps can talk between each other in a podman network within a pod.

Create the pod
podman pod create --userns=keep-id --publish 8080:8080 --name mypod

podman run --detach --volume ./mongo-data:/data/db --pod mypod --name some-mongo mongo:4.4.13

podman run --detach --pod mypod --name myapp -e SPRING_DATA_MONGODB_HOST="localhost" -e CS_DATABASE_MONGODB_EMBEDED_ENABLED="false" e7b8dd57dec6

Not used - only for debug
podman run -it --pod mypod --name myapp --volume ./config:/config --entrypoint "/bin/sh" e7b8dd57dec6

Pickling

2025-10-21T16:47:51Z

Jfreier: Created page with "Pickled Jalapeños 1 Cup - Water 1 Cup - Vinegar 2 Tbs - Sugar 1 Tbs - Salt 10 - peppercorns 1 - Bay left 3 - Garlic Slice Jalapeños, boil ingredients, put all in jar. Cowb..."

Pickled Jalapeños
1 Cup - Water
1 Cup - Vinegar
2 Tbs - Sugar
1 Tbs - Salt
10 - peppercorns
1 - Bay left
3 - Garlic

Slice Jalapeños, boil ingredients, put all in jar.

Cowboy Candy
1 Cup - Apple Cider Vinegar
1 Cup - Sugar
1 Tsp - Garlic Powder
1/4 Tsp - Turmeric

Boil ingredients, then 5 mins on simmer, back to boil, add jalapeños, boil for 4 mins. Remove jalapeños, boil until reduced a bit, about 5 mins. Add mix to jalapeños. Wait 3-4 weeks, eat.

Food

2025-10-21T16:40:56Z

Jfreier:

Food Recipes
----
[[Hard Boiled Egg]]

[[Collard Greens]]

[[Brussel Sprouts]]

[[Broccoli]]

[[Carrots]]

[[Baked Chicken Legs]]

[[Kick-ass_Vodka...Sauce!]]

[[food_apple_cider|Apple Cider]]

[[food_chex_mix|Chex Mix]]

[[olive_mix|Olive Mix]]

[[beer_cheese_dip|Beer Cheese Dip]]

[[dirty_rice|Dirty Rice]]

[[potato_salad|Potato Salad]]

[[coleslaw|Coleslaw]]

[[pickling|Pickling]]

Coleslaw

2025-07-13T00:18:50Z

Jfreier: Created page with "1/2 cup milk 1/8 sugar (half 1/4 cup) 1/2 cup mayonnaise 1/2 tablespoon vinegar Lemon juice Salt & pepper Cabbage 1 carrot A little chopped onions"

1/2 cup milk
1/8 sugar (half 1/4 cup)
1/2 cup mayonnaise
1/2 tablespoon vinegar
Lemon juice
Salt & pepper
Cabbage
1 carrot
A little chopped onions

Food

2025-07-13T00:15:38Z

Jfreier:

Python poetry

2025-05-30T15:48:44Z

Jfreier: Created page with "Create new project poetry init"

Create new project
poetry init

Python

2025-05-30T15:47:41Z

Jfreier:

VIM

2025-02-25T17:02:09Z

Jfreier:

==Syntax Highlighting==
Inside VI type the command below.

:syntax on

Maybe

:syn on

== Bottom Page ==
This goes to the bottom of the page.
G

== Bookmarks ==
To bookmark a position press m and then a letter. Use capital letter for Global or multiple files.
ma

To go to the bookmark press ` and then letter marking you want to go to.
`a

To see all your bookmarks.
:marks

To to last edit location.
`.

== Record ==
To record a set of keys press q and then a letter to record to.
qa

To play back the recording press @ and then letter marking you want to play back.
@a

== Copy & Paste ==
To yank to a registered key
" + {key} + y

To paste from a registered key.
" + {key} + p

== Windows ==
'''Switch''' between windows. The arrow key or direction key you want to go to.
ctrl+w {arrow key} or {h,j,k,l}

Opens a new vertical split
CTRL+w, v

Opens a new horizontal split
CTRL+w, s

Closes a window but keeps the buffer
CTRL+w, c

Closes other windows, keeps the active window only
CTRL+w, o

Moves the current window to the right
CTRL+w, r

Makes all splits equal size
CTRL+w, =

== Show Whitespace ==

This will show all whitespace char
set list

You can also show only select char.
:set listchars=eol:$,tab:>-,trail:~

== Spelling ==
To turn spell checker on.
:set spell spelllang=en_us

To turn spell checker off.
:set nospell

To move between misspelled words.
]s and [s

To get misspelled recommendations, move in misspelled word and press.
z=

To add word to dictionary.
zg

To mark a word as incorrect
zw

== Autocomplete ==
This autocomplete tries to match word already in the document.
ctl+n or ctl+p

== Netrw ==
Open as a left window.
:Lexplore or :Lex

Open as a new tab.
:tabe .

Open file in new tab when in Netrw.
t

Create new file.
%

Create new directory.
d

Delete file or directory.
D

== Terminal ==
You can open a new terminal by typing.
:terminal

You can enter `normal` mode.
ctrl-\ ctrl-n

Exit terminal mode
ctrl-d

== Pipe in data from console ==
To pipe in data from the command line use the following
:%!{command}

or

If you in the terminal and want the output to go into vim.
ls | vim -

== Column Editing ==
Column editing is editing a bunch of lines at once.

ctrl-v - start highlight of columns.
h,j,k,l - to select the columns and/or rows
shift-i - to go to insert mode.

== Highlight blocks ==
To quick highlight blocks of code with in { or [

Move the curser inside the block, and type the following.
vi[
or
vi{

== Edit in VIM ==
To bring a command line in to VIM for editing
ctrl+x ctrl+e

== Switch bash to use VIM ==
This will allow the terminal to use vim keys.
set -o vi

== Diff ==
The following key combinations will show the diff between two copied registries.

:tabnew // Create a new tab.
" -> a -> p // Paste the text from registry 'a'
leftabove vnew diff1. // create a side window called diff1

ctr+w ->> // switch windows

" -> b -> p // paste the text from registry 'b'
ctr+w <<- // Switch windows again
:diffthis // diff the two windows

== Buffer ==
List all buffers
:ls

Open a buffer
:buffer {number from above}

Open a buffer in a new tab
:tab sb {number from above}

NetCat

2025-02-04T20:01:38Z

Jfreier:

Redirect ports.

This one redirect port 24 to port 22.

<code>24 stream tcp nowait nobody /usr/sbin/tcpd /bin/nc 192.168.1.1 22</code>

This one redirects port 6000(x11) to port 25

<code>x11 stream tcp nowait root /usr/local/bin/nc nc -n -w 3 127.0.0.1 25</code>

== Start a chat ==
host computer - 10.0.0.1
nc -l 8001

remote computer - 10.0.0.2
nc 10.0.0.1 8001

and then start typing

== Send a file ==
This will send a file to another computer on the same network

hosted file computer - 10.0.0.1
cat file.doc | nc 10.0.0.2 8001

remote file to receive the file
nc -l 8001 > file.doc

== Reverse Shell ==
This create a shell for a client to use.

hosted computer to get the shell from
nc 127.0.0.1 1234 –e /bin/bash

remote computer to use the shell
nc -l -p 1234

== Shell Listener ==
This creates a listener shell, at which point any client can connect to and use the shell.

The host computer with the shell to access.
nc –l –p 1234 –e /bin/bash

Connect to the host computer with the following command.
nc 127.0.0.1 1234

Side note: You can create a simple script and run this with nohup in the background to insure this continues running.
nohup ./script.sh &

You can also pipe all commands into bash
nc -l 1234 | /bin/bash

== Keep Listening ==
Continue listening after a connection is closed use the -k option.
nc -k -l 1234

== Echo everything that http requests ==
nc -kdl 8000

Python pdb

2024-12-04T20:20:53Z

Jfreier:

To debug python applications use the library pdb.

Add the following to the top of your file.

import pdb

To add a breakpoint in the python use
pdb.set_trace()
or
breakpoint() # 3.7 for higher

And then just add the following to your command.
--pdb

Example
pytest --pdb test/test.py

Once it starts up you will be brought to a promote.
From the there you can use any of the following.

Navigating Code (within the Pdb interpreter)
l(ist) list 11 lines surrounding the current line
l . list the current location
w(here) display the file and line number of the current line
n(ext) execute the current line
s(tep) step into functions called at the current line
r(eturn) execute until the current function’s return is encountered

Controlling Execution
b[#] create a breakpoint at line [#]
b list breakpoints and their indices
c(ontinue) execute until a breakpoint is encountered
clear[#] clear breakpoint of index [#]

Changing Variables / Interacting with Code
p<name> print value of the variable <name>
!<expr> execute the expression <expr> NOTE: this acts just like a python interpreter
q(uit) exit the debugger

Example Command
poetry run pytest -o log_cli=true --log-cli-level=INFO -v tests/functions/test_function.py::TestOne::test_one --pdb --no-cov

Issues
If pdb is breaking in the wrong location try adding the following flag.
--no-cov

Python pdb

2024-12-03T16:04:15Z

Jfreier:

To debug python applications use the library pdb.

Add the following to the top of your file.

import pdb

To add a breakpoint in the python use
pdb.set_trace()
or
breakpoint() # 3.7 for higher

And then just add the following to your command.
--pdb

Example
pytest --pdb test/test.py

Once it starts up you will be brought to a promote.
From the there you can use any of the following.

Navigating Code (within the Pdb interpreter)
l(ist) list 11 lines surrounding the current line
l . list the current location
w(here) display the file and line number of the current line
n(ext) execute the current line
s(tep) step into functions called at the current line
r(eturn) execute until the current function’s return is encountered

Controlling Execution
b[#] create a breakpoint at line [#]
b list breakpoints and their indices
c(ontinue) execute until a breakpoint is encountered
clear[#] clear breakpoint of index [#]

Changing Variables / Interacting with Code
p<name> print value of the variable <name>
!<expr> execute the expression <expr> NOTE: this acts just like a python interpreter
q(uit) exit the debugger

Issues
If pdb is breaking in the wrong location try adding the following flag.
--no-cov

Postgresql

2024-11-04T19:56:31Z

Jfreier:

Linux gpg

2024-10-30T16:50:47Z

Jfreier:

== Import Public/Private Key ==
It doesn't make a difference if its a private key or public key, this is the correct way to import a key.
gpg --import file.gpg

== Export Public Key ==

This is the command to export your public key, using the armor command will convert the key from binary to ascii, so you can email it or post it.

gpg --armor --export you@example.com > mykey.asc

Another way

gpg --output mykey_pub.gpg --armor --export me@email.com

If you have more then one key another way where ABAACA is the hash.

gpg --output mykey_pub.gpg --armor --export ABAACA

Export a base64 output of your public key.
gpg --export me@email.com | base64

== Export Private Key ==
To export your private key.

gpg --output mykey_sec.gpg --armor --export-secret-key me@email.com

another way, where ABAACA is the hash

gpg --output mykey_sec.gpg --armor --export-secret-key ABAACA

Base64 export of your private key.
gpg --export-secret-key me@email.com | base64

== List Keys ==
To see a list of all the keys in the system.

gpg --list-keys

== Sign a file ==

This will create a single file called text.sig that will contain both the file and the signature.
gpg --clear-sig --output text.sig text.txt

This will create a single file called text.sig that contains an ascii file with just the signature.
gpg --detach-sign --armor --output text.sig text.txt

This will create a single file called text.sig with a binary signature.
gpg --detach-sign --output text.sig text.txt

This will create an binary file with a signature and original document.
gpg --sign --output text.txt.sig text.txt

== Backup ==
I read somewhere to back up the GPG file system, you can just copy ~/. gnupg but I have not tried this before.

== Resources ==
https://www.debuntu.org/how-to-importexport-gpg-key-pair/

== Encrypt a File with Password ==
To encrypt a file with a password with gpg use the following
gpg -c filename

This will create a new encrypted file with the extension .gpg, you can delete the unencrypted file.

To decrypt the file.
gpg -d filename

== Encrypt a File from user key ==

Encrypt the file.
gpg --encrypt --user john.doe@email.com key.dv

decrypt the file to a bash variable.
export PGPASSWORD=$(cat $v_password | gpg --decrypt --user john.do@email.com)

== Extend the expiration date of a key ==
If you key expires you can extend the expiration date of the key

Command
gpg --quick-set-expire {key_id} {extended_amount}

key_id=the key id
extended_amount=The amount of time to add, d, m, y

example
gpg --quick-set-expire 38D3CD66D0671E54B78001B43FD6190BCDE08D11 2y

https://www.gnupg.org/documentation/manuals/gnupg/OpenPGP-Key-Management.html

Apache

2024-07-31T18:33:42Z

Jfreier:

== Virtual Host ==
This is how you setup apache for Virual Hosts. example if you have more domain names and only one server.
The serverAlias is used in case people don't put in the "www" before the URL.
<VirtualHost *:80>
DocumentRoot /home/{user}/public_html
ServerName www.{domainname}.com
ServerAlias {domainname}.com
</VirtualHost>

== Virtual Host ProxyPass ==
This will pass any http request along. It helps when you want to pass a connection to another server, example apache -> tomcat:8080.

<VirtualHost *:80>
ProxyPreserveHost On
ProxyPass / http://localhost:8080/
ProxyPassReverse / http://localhost:8080/
ServerName www.{domainname}.com
ServerAlias {domainname}.com
</VirtualHost>

== SSL Setup ==

I'm playing around with SSL setup for Apache. My overall goal would be to set up an SSL web address that would be only accessed with a single private key that would have to be imported into a browser and not handed off from the server.

1. Install SSL module for Apache on Fedora
yum install mod_ssl

2. I create a folder for housing any newly created certs to be used by Apache.
mkdir /etc/httpd/ssl

*.key = Key file kind of like a password.
*.csr = Certificate Signing Request, this is the built request to generate a certificate.
*.crt = Certificate
*.pem = Bundle of key, and certificates.
*.p12 = a combo file of key and cert.

1. Create files for openssl to use for records.
index.txt is an openssl database file.

touch index.txt
echo 1000 > serial

2. Create the private key for the CA ROOT certification.

# openssl genrsa -aes256 -out /etc/pki/CA/private/ca.key 4096

Enter pass phrase for ca.key: secretpassword
Verifying - Enter pass phrase for ca.key: secretpassword

# chmod 400 /etc/pki/CA/private/ca.key

3. Double check configs. I needed to uncomment out some.

Open your OpenSSL configuration file (/etc/pki/tls/openssl.cnf) and look for the [ usr_cert ] and [ v3_ca ] sections. Make sure they contain the following options:

[ usr_cert ]
# These extensions are added when 'ca' signs a request.
basicConstraints=CA:FALSE
keyUsage = nonRepudiation, digitalSignature, keyEncipherment
nsComment = "OpenSSL Generated Certificate"
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid,issuer

[ v3_ca ]
# Extensions for a typical CA
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid:always,issuer
basicConstraints = CA:true
keyUsage = cRLSign, keyCertSign

4. Create a CA certificate from your CA key.

Now you can use the root key above to issue a root certificate (ca.crt). In this example, the certificate is set to expire in ten years. As this is a CA certificate, use the v3_ca extension. You will be prompted for some responses, which you can fill with whatever you like. For convenience, defaults can be set in the openssl configuration file.

Important: The default digest is SHA-1. SHA-1 is considered insecure. Pass the -sha256 option to use a more secure digest.

Make sure the common name matches your server name, wiki.johnfreier.com.

openssl req -new -x509 -days 3650 -key /etc/pki/CA/private/ca.key -sha256 -extensions v3_ca -out /etc/pki/CA/certs/ca.crt

Enter pass phrase for ca.key:
You are about to be asked to enter information that will be incorporated
into your certificate request.
-----
Country Name (2 letter code) [XX]:GB
State or Province Name (full name) []:London
Locality Name (eg, city) [Default City]:London
Organization Name (eg, company) [Default Company Ltd]:Alice CA
Organizational Unit Name (eg, section) []:Certificate Authority
Common Name (eg, your name or your server's hostname) []:Alice CA
Email Address []:alice@example.com

chmod 444 /etc/pki/CA/certs/ca.crt

Root key: ca.key
Root certificate: ca.cert

1. Generate Signing Request Key. This creates a signing request key that is used to verify things.

openssl genrsa -out footballaz.key 4096

2. Create a certificate signing request (csr) - Make sure that the '''Organization Name''' you choose below matches the one set for your CA root certificate. The extra attributes can be left blank. If you are creating a self-signed certificate, you would also use the -x509 and -days options.

I did not use -x509 or -days not sure what i missed???

openssl req -sha256 -new -key footballaz.key -out footballaz.csr

3. Create Certificate

openssl ca -keyfile /etc/pki/CA/private/ca.key -cert /etc/pki/CA/certs/ca.crt -extensions usr_cert -notext -md sha256 -in footballaz.csr -out footballaz.crt

4. Verify new certificate

openssl verify -CAfile /etc/pki/CA/certs/ca.crt footballaz.crt

Need to generate a *.p12 certificate. Which is a special combination cert that is password protected. This one is need by the browser to get to the site.

openssl pkcs12 -export -in footballaz.crt -inkey footballaz.key -out footballaz.p12

5. Install the *.p12 file in a browser or computer and....

It WORKED!!!

These were extra SSL properties I needed to get it to work correctly.
<VirtualHost *:443>
SSLEngine on
SSLCertificateFile /etc/httpd/ssl/footballaz.crt
SSLCertificateKeyFile /etc/httpd/ssl/footballaz.key
SSLCACertificateFile {path_to_ca}/ca.crt
SSLVerifyClient require
SSLVerifyDepth 2
SSLProtocol all -SSLv2 -SSLv3
SSLHonorCipherOrder On
SSLCipherSuite ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:ECDHE-RSA-DES-CBC3-SHA:ECDHE-ECDSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA
</VirtualHost>
Resources

https://jamielinux.com/articles/2013/08/act-as-your-own-certificate-authority/

http://linuxconfig.org/apache-web-server-ssl-authentication

http://cs.uccs.edu/~cs526/secureWebAccess/secureWebAccess.htm

http://www.apachelounge.com/viewtopic.php?t=3571

https://www.linode.com/docs/security/ssl/ssl-certificates-with-apache-2-on-fedora-14

== SSL (StartSSL) ==
This is a free SSL certificate issue https://www.startssl.com

Follow the steps.

for my configuration I needed www.johnfreier.com as the common name.

After you follow the steps you will get a zip file with a bunch of *.crt files in folders.
You will want to unzip the ApacheBundle.zip

Use this configuration: https://www.startssl.com/Support?v=21

# openssl rsa -in www.key -out new.key

== Notes on updating crt ==
1. Paste current johnfreier.com csr to website that issues the new crt.
2. The new crt gets emailed, just replace it.

VIM

2024-07-09T21:53:18Z

Jfreier:

Splunk

2024-07-02T19:46:38Z

Jfreier:

Get the line result count.
host=server01 Error | stats sum(linecount) as Total

Get result count per day or hour
host=server01 Error | bucket _time span=hour |stats count by _time

Python pdb

2024-05-29T13:22:37Z

Jfreier:

Python pdb

2024-05-28T20:44:05Z

Jfreier:

To debug python applications use the library pdb.

Add the following to the top of your file.

import pdb
pdb.set_trace()

And then just add the following to your command.
--pdb

Example
pytest --pdb test/test.py

Once it starts up you will be brought to a promote.
From the there you can use any of the following.

Navigating Code (within the Pdb interpreter)
l(ist) list 11 lines surrounding the current line
l . list the current location
w(here) display the file and line number of the current line
n(ext) execute the current line
s(tep) step into functions called at the current line
r(eturn) execute until the current function’s return is encountered

Controlling Execution
b[#] create a breakpoint at line [#]
b list breakpoints and their indices
c(ontinue) execute until a breakpoint is encountered
clear[#] clear breakpoint of index [#]

Changing Variables / Interacting with Code
p<name> print value of the variable <name>
!<expr> execute the expression <expr> NOTE: this acts just like a python interpreter
q(uit) exit the debugger

To add a breakpoint in the python.
breakpoint()

Python pytest

2024-05-28T20:43:07Z

Jfreier:

To run tests in a specific dir
pytest path/to/dir

To run tests in a specific file
pytest path/to/test_file.py

To run a specific test in a file
pytest path/to/test_file.py::test_function

or

pytest path/to/test_file.py -k 'test_name'

To show the print statements.
-s or --capture=no

To show log statements
-o log_cli=true

To set the log level.
--log-cli-level=INFO

Python pdb

2024-05-28T20:42:11Z

Jfreier: Created page with "To debug python applications use the library pdb. Add the following to the top of your file. import pdb pdb.set_trace() And then just add the following to your command...."

To debug python applications use the library pdb.

Add the following to the top of your file.

import pdb
pdb.set_trace()

And then just add the following to your command.
--pdb

Example
pytest --pdb test/test.py

Once it starts up you will be brought to a promote.
From the there you can use any of the following.

Navigating Code (within the Pdb interpreter)
l(ist) list 11 lines surrounding the current line
w(here) display the file and line number of the current line
n(ext) execute the current line
s(tep) step into functions called at the current line
r(eturn) execute until the current function’s return is encountered

Controlling Execution
b[#] create a breakpoint at line [#]
b list breakpoints and their indices
c(ontinue) execute until a breakpoint is encountered
clear[#] clear breakpoint of index [#]

Changing Variables / Interacting with Code
p<name> print value of the variable <name>
!<expr> execute the expression <expr> NOTE: this acts just like a python interpreter
q(uit) exit the debugger

To add a breakpoint in the python.
breakpoint()

Python

2024-05-28T16:23:02Z

Jfreier:

Kubectl

2024-05-17T16:03:00Z

Jfreier:

Kubectl is an application that interacts with Kubernetes clusters.

'''Check the context'''

This checks who kubectl is connected to.
kubectl config current-context

'''Apply a configuration yaml file.'''
kubectl apply -f [name_of_file]

'''Get the configuration yaml file.'''
kubectl get pod [podname] --namespace [namespace] -o yaml

== Deploy ==
'''Get Deployments'''
kubectl get deployments --namespace=cs

'''Delete Deployments'''
kubectl delete deployment [name_of_deployment] --namespace=cs

== Pods ==
'''Get Pods'''

This gets all the pods.
kubectl get pods --namespace cs

Delete a pod
kubectl delete pod [pod_name]

== Remote in to a pod ==
This will allow you to execute a command which in the example below it will start up a shell.
kubectl exec --stdin --tty [pod_name] --namespace [namespace] -- /bin/sh

== Volume ==

List Persistent Volumes Claims
kubectl describe pvc --namespace=cs

== Logs ==
Get the logs from a pod.
kubectl logs -p [pod_name] --namespace=cs

For any sidecars you may need to specifiy a container.
kubectl logs -p [pod_name] --namespace=cs --container gce-proxy

You can also follow the logs live with the following flaf.
--follow

== Events ==
Get a list of events.

kubectl get events

== Extra commands to help.==
If you have to include a name space.
--namespace scdf-jf

To be past any SSL issues.
--insecure-skip-tls-verify

Kubectl

2024-05-17T16:00:36Z

Jfreier: /* Logs */

Kubectl is an application that interacts with Kubernetes clusters.

'''Check the context'''

This checks who kubectl is connected to.
kubectl config current-context

'''Apply a configuration yaml file.'''
kubectl apply -f [name_of_file]

== Deploy ==
'''Get Deployments'''
kubectl get deployments --namespace=cs

'''Delete Deployments'''
kubectl delete deployment [name_of_deployment] --namespace=cs

== Pods ==
'''Get Pods'''

This gets all the pods.
kubectl get pods --namespace cs

Delete a pod
kubectl delete pod [pod_name]

== Volume ==

List Persistent Volumes Claims
kubectl describe pvc --namespace=cs

== Logs ==
Get the logs from a pod.
kubectl logs -p [pod_name] --namespace=cs

For any sidecars you may need to specifiy a container.
kubectl logs -p [pod_name] --namespace=cs --container gce-proxy

You can also follow the logs live with the following flaf.
--follow

== Events ==
Get a list of events.

kubectl get events

== Extra commands to help.==
If you have to include a name space.
--namespace scdf-jf

To be past any SSL issues.
--insecure-skip-tls-verify

Kubectl

2024-05-17T15:55:16Z

Jfreier:

Python pytest

2024-05-08T23:35:41Z

Jfreier:

VIM

2024-04-17T15:52:25Z

Jfreier:

Git

2024-03-01T20:12:29Z

Jfreier:

== Rebase ==
When you are on a branch, you get
git rebase master

You will get conflicts with the remote origin if you try and push. Here are some ways to solve this.

This will force the remote origin to stay up to date with your branch. But be aware, if there are more people working on the feature branch then just you, you may overwrite code.
git push --force origin feature_branch

With force with lease, git will warn you if anyone else has committed any code, this helps to prevent overwriting someones code.
git push --force-with-lease

Another good option after rebase with master is to just delete the branch on the remote origin, and then recreate it.
git checkout myFeature
git rebase master
git push origin --delete myFeature
git push origin myFeature

== Squash feature branch ==
This squashes all the commits in to one.
git merge --squash feature

and then you need to commit the new squashed changes.
get commit -m "squashed changes merged in."

== Squash Commits ==
This squashes the last 3 commits.
git reset --soft HEAD~3
git commit -m 'new commit message'

== View the logs ==
A another way to view the logs.
git log --oneline --decorate --graph --all

== Add all untracked changes. ==
Here is a couple of commands to help with backing things up.
This will add all untracked changes for a file type.
git ls-files --other | grep ".md" | xargs git add

This will add all tracked changes for a file type.
git ls-files | grep ".md" | xargs git add

== Sign with GPG
List your keys
gpg --list-secret-keys --keyid-format=long

Update git to use a specific key.
git config --global user.signingkey 3AA5C34371567BD2

Sign all commits by default.
git config --global commit.gpgsign true

Osx-users

2024-02-29T16:20:56Z

Jfreier: Created page with "Add a user to a group sudo dseditgroup -o edit -a john -t user agroup Create a group sudo dscl . create /Groups/dev List items about a group. dscacheutil -q group -a n..."

Add a user to a group
sudo dseditgroup -o edit -a john -t user agroup

Create a group
sudo dscl . create /Groups/dev

List items about a group.
dscacheutil -q group -a name dev

Osx

2024-02-29T16:19:57Z

Jfreier:

Git

2024-02-28T19:55:13Z

Jfreier:

Plsql search constraints

2023-10-03T16:33:03Z

Jfreier:

Plsql search constraints

2023-10-03T16:30:42Z

Jfreier:

Run the query below to search for information on constraints.

* OWNER = Schema
* FK_NAME = Constraint name

select *
from all_constraints
where 1=1
--and owner = 'OWNER'
and constraint_name LIKE '%FK_NAME%';

Another way
SELECT *
FROM user_constraints
WHERE table_name = '<your table name>'
AND constraint_name = '<your constraint name>';

Plsql first records

2023-10-03T16:28:43Z

Jfreier: Created page with "To fetch the first 10 records from a result. SELECT * FROM table_a FETCH FIRST 1 ROW ONLY;"

To fetch the first 10 records from a result.

SELECT *
FROM table_a
FETCH FIRST 1 ROW ONLY;

Plsql

2023-10-03T16:27:51Z

Jfreier:

Bash

2023-08-03T21:05:10Z

Jfreier:

== Keyboard Shortcuts ==
To send the current line to VIM for editing.
ctrl+x ctrl+e

== One line conditional ==
Both the following lines will write to the screen "false"
[[ 1 == 0 ]] || echo "text"

[[ 1 == 1 ]] && echo "text"

== Check for environment variable ==
This will check to see if an variable is set
if [[ -z "$var" ]]; then
echo "var is not set"
fi

== Change the command prompt. ==
To change the command prompt, export the below value.
export PS1=">"
or
export PS1="${ret_status} %{$fg[cyan]%}%c%{$reset_color%} $(git_prompt_info)"

== Alias ==
To find the command associated with an alias.
type [alias_name]

To list all aliases, just type 'alias'.
alias

To create an alias.
alias myproject='cd /Users/jfreier/Projects/my_project'

== Edit in VIM ==
To bring a command line in to VIM for editing
ctrl+x ctrl+e

== Echo commands ==
This will print all commands that are ran.
set -x

== To set the CD Path ==
$CDPATH

== Alternative Screen ==
This happens when you run a command a new screen appears and then is closed when done.

To turn this feature off.
export LESS="-FRX"

This new screen is actually LESS and it just needs different flags.

== Temporary Environment Variables for Scripts ==
If you have a script or command that uses environment variables, you can set one time variables be just prefixing the comment with the environment variable and command.

Example

echo_env_var.sh
#!/bin/bash

echo $JOHN_FREIER

Command
# JOHN_FREIER=1 ./echo_env_var.sh

== Exit script on error ==
To immediately exit a script when an error happens use the following command.
set -e

== Loop through argument variables. ==
This sniplet will loop through the arguments of a script.

for var in "$@"
do
echo "arg: $var"
done

== Previous command arguments ==
To the the arguments from the previous command.

!^ first argument
!$ last argument
!* all arguments
!:2 second argument

!:2-3 second to third arguments
!:2-$ second to last arguments
!:2* second to last arguments
!:2- second to next to last arguments

!:0 the command
!! repeat the previous line, good with sudo

Postgresql

2023-07-21T16:25:38Z

Jfreier:

Podman

2023-07-12T20:00:07Z

Jfreier:

== Podman ==

'''Start Podman'''
podman machine start

== Images ==

'''List Images'''
podman images

'''Pull an image'''
podman pull docker.io/library/httpd

'''Run an image'''
podman run -dt -p 8080:80/tcp docker.io/library/httpd

podman run -it --entrypoint="/bin/sh" docker.io/library/httpd

podman run -it -v /home/user/project:/app --entrypoint="/bin/bash" python:3.9.13-buster

* The -d will run the container in detach mode, so you wont see any console.
* The -t command connects the container to your terminal so it will not exit after it runs.

The following command with -rm will clean up the container and remove any persists data.
podman run -rm docker.io/library/httpd

To commit a container to the list of podman images.
podman commit {id}

'''Continue a container'''
This will start back up an exited container, it will continue where you left off.
podman start {id}

'''Get in to a running container'''
podman exec -it {id} /bin/sh

'''List running images'''
podman ps -a

'''Remove Image'''
podman rmi {image_sha}

'''Load an Image'''
Worked
cat cs-oci.tar | podman load

Did not work.
podman load oci-archive:cs-oci.tar:latest

'''Update the tag for an image'''
podman tag e7b8dd57dec6 cs:latest

== Containers ==

'''List all containers'''
podman ps -a

'''Remove Container'''
podman rm ff22b3bfecc1

== Pods ==

'''Create a pod'''
podman pod create --name mypod

'''List pods'''
podman pod list

'''Start pod'''
podman pod start {podname}

'''Stop pod'''
podman pod stop {podname}

'''List all processes with pods'''
podman ps -a --pod

== Volume ==

Volume in Podman can be a virtual volume that is mounted through Podman. This virtual volume can be exported or imported as well.

You can also setup to point to a local host directory but because Podman is rootless Podman will need access to the directory, by either permissions on the directory or the user that runs the container from Podman.

'''Create Virtual Volume'''
podman volume create myvolume

'''Export Virtual Volume'''
podman volume export myvolume --output myvolume.tar

== Repositories ==
To login to a repository.
The below example is for harbor but could be used for others.
podman login --username JDOE --password {cli_secret} https://registry.harbor-url.com/

== Build ==

To build and avoid any cached layers use the following.
podman build --no-cache -t $container_name:$container_tag .

== Logs ==

'''View Logs'''
podman logs ff22b3bfecc1

'''Stop the latest container'''

podman stop ff22b3bfecc1

== Kube ==

'''Generate kubernetes yaml'''
podman generate kube -f infra.yaml mypod

'''Load kubernetes yaml'''
podman play kube infra.yaml

'''Kubernetes File'''
# Kubernetes setup for CS.
apiVersion: v1
kind: ConfigMap
metadata:
name: cs-config
data:
CS_DATABASE_MONGODB_EMBEDED_ENABLED: "false"
SPRING_DATA_MONGODB_HOST: "localhost"
---
apiVersion: v1
kind: Pod
metadata:
name: mypod
labels:
app: mypod
spec:
containers:
- name: database
image: docker.io/library/mongo:4.4.13
securityContext:
runAsUser: 0
volumeMounts:
- name: mongodb-data-volume
mountPath: /data/db
- name: application
image: cs:latest
ports:
- containerPort: 8080
hostPort: 8080
envFrom:
- configMapRef:
name: cs-config
volumes:
- name: mongodb-data-volume
persistentVolumeClaim:
claimName: mongodb-data-storage

== Examples ==

'''Example run MongoDB'''
podman run \
--detach \
--publish 27017:27017 \
--userns=keep-id \
--volume ./mongo-data:/data/db \
--name some-mongo \
mongo:4.4.13

# --detach, -d - Detached mode: run the container in the background and print the new container ID. The default is false
# --publish, -p - Publish a container’s port, or range of ports, to the host.
# --userns - Because podman runs rootless we need to assign a user that can access the local volumn. This sets the podman user to the same user who ran the podman command.
# --volume, -v - Create a bind mount.
# --name - Assign a name to the container.

'''Example running with pods'''
This is a test to see how apps can talk between each other in a podman network within a pod.

Create the pod
podman pod create --userns=keep-id --publish 8080:8080 --name mypod

podman run --detach --volume ./mongo-data:/data/db --pod mypod --name some-mongo mongo:4.4.13

podman run --detach --pod mypod --name myapp -e SPRING_DATA_MONGODB_HOST="localhost" -e CS_DATABASE_MONGODB_EMBEDED_ENABLED="false" e7b8dd57dec6

Not used - only for debug
podman run -it --pod mypod --name myapp --volume ./config:/config --entrypoint "/bin/sh" e7b8dd57dec6

Postgresql

2023-07-07T20:25:34Z

Jfreier:

Postgresql

2023-07-07T15:46:54Z

Jfreier:

Bash

2023-06-26T18:40:59Z

Jfreier:

Bash

2023-06-26T18:39:34Z

Jfreier:

Linux gpg

2023-06-26T17:31:58Z

Jfreier:

== Import Public/Private Key ==
It doesn't make a difference if its a private key or public key, this is the correct way to import a key.
gpg --import file.gpg

== Export Public Key ==

This is the command to export your public key, using the armor command will convert the key from binary to ascii, so you can email it or post it.

gpg --armor --export you@example.com > mykey.asc

Another way

gpg --output mykey_pub.gpg --armor --export me@email.com

If you have more then one key another way where ABAACA is the hash.

gpg --output mykey_pub.gpg --armor --export ABAACA

Export a base64 output of your public key.
gpg --export me@email.com | base64

== Export Private Key ==
To export your private key.

gpg --output mykey_sec.gpg --armor --export-secret-key me@email.com

another way, where ABAACA is the hash

gpg --output mykey_sec.gpg --armor --export-secret-key ABAACA

Base64 export of your private key.
gpg --export-secret-key me@email.com | base64

== List Keys ==
To see a list of all the keys in the system.

gpg --list-keys

== Sign a file ==

This will create a single file called text.sig that will contain both the file and the signature.
gpg --clear-sig --output text.sig text.txt

This will create a single file called text.sig that contains an ascii file with just the signature.
gpg --detach-sign --armor --output text.sig text.txt

This will create a single file called text.sig with a binary signature.
gpg --detach-sign --output text.sig text.txt

This will create an binary file with a signature and original document.
gpg --sign --output text.txt.sig text.txt

== Backup ==
I read somewhere to back up the GPG file system, you can just copy ~/. gnupg but I have not tried this before.

== Resources ==
https://www.debuntu.org/how-to-importexport-gpg-key-pair/

== Encrypt a File with Password ==
To encrypt a file with a password with gpg use the following
gpg -c filename

This will create a new encrypted file with the extension .gpg, you can delete the unencrypted file.

To decrypt the file.
gpg -d filename

== Extend the expiration date of a key ==
If you key expires you can extend the expiration date of the key

Command
gpg --quick-set-expire {key_id} {extended_amount}

key_id=the key id
extended_amount=The amount of time to add, d, m, y

example
gpg --quick-set-expire 38D3CD66D0671E54B78001B43FD6190BCDE08D11 2y

https://www.gnupg.org/documentation/manuals/gnupg/OpenPGP-Key-Management.html

Bash

2023-06-26T17:24:22Z

Jfreier: