DEV Community: Jaeyson Anthony Y.

Simple way to send Github events to a Discord channel using webhook

Jaeyson Anthony Y. — Sat, 27 Nov 2021 10:37:25 +0000

You can create a test server to try this out.
Create or select a text channel you want to send the events (e.g. general), mine's in github-webhook channel:

Go to channel's settings (gear icon) > Integrations > Webhooks > New Webhook > Copy Webhook URL

Go to your repo's settings > Webhooks > Add webhook
Paste the webhook URL to Payload URL, make sure to append /github. You can choose which event(s) to listen. For this example I set it to Send me everything.:

Proof:

AWS S3 CLI docker for the impatient (also wasabi)

Jaeyson Anthony Y. — Mon, 26 Oct 2020 13:44:05 +0000

What's the problem with AWS cli guide (it has good docs anyway)? well, nothing really complex unless you really want to use it asap. This is more of a basic setup and quick run using docker.

0. Things needed: Docker and AWS S3 creds (access key id/secret access key)

There's a guide for linux distro, and a post-installation steps to run Docker as non-root

1. Pull Docker image

docker image pull amazon/aws-cli

2. Make credentials

Create ~/.aws dir if not exists, then inside that dir create a file credentials and config:

~/.aws/credentials

[default]
aws_access_key_id=fffff3333ff55555GGGG
aws_secret_access_key=kkkkkkkkkkkkkkkeeeeeeeeeeeeeyyyyyyyyyyyy

~/.aws/config

[default]
region=us-west-2
output=json

Or use an interactive setup

# interactive setup for creds
docker container run --rm -it \
  -v ~/.aws:/root/.aws \
  amazon/aws-cli \
  configure

Check creds:

docker container run --rm -it \
  -v ~/.aws:/root/.aws \
  amazon/aws-cli \
  configure

# or view
cat ~/.aws/credentials

3. `cp` copy, `sync` , `mv` move and `ls` list files

3.a. `cp` copy command

$ aws s3 cp <source> <target> [--options]

source could mean your files from your computer or from S3

Add --recursive option if dir:

# upload a local file hyena.png (current dir) to mammals dir
docker container run --rm \
  -v ~/.aws:/root/.aws \
  -v $(pwd):/aws \
  amazon/aws-cli s3 \
  cp hyena.png \
  s3://animal-bucket/mammals/

# download lynx.png from s3 to current dir
docker container run --rm \
  -v ~/.aws:/root/.aws \
  -v $(pwd):/aws amazon/aws-cli s3 \
  cp s3://animal-bucket/mammals/lynx.png ./

# upload all contents from reptiles dir (local) to s3
docker container run --rm \
  -v ~/.aws:/root/.aws \
  -v $(pwd):/aws amazon/aws-cli s3 \
  cp reptiles/ s3://animal-bucket/reptiles/ \
  --recursive

3.b `ls` command

# list all files in reptiles dir
docker container run --rm \
  -v ~/.aws:/root/.aws \
  amazon/aws-cli s3 \
  ls s3://animal-bucket/reptiles/

e.g. get the size of a bucket

docker container run --rm \
  -v ~/.aws:/root/.aws \
  amazon/aws-cli s3 \
  ls s3://animal-bucket/ \
  --summarize \
  --human-readable \
  --recursive \
  --profile profile-name \
  --endpoint-url=https://s3.<region>.<provider>.com

3.c `sync` command

aws s3 sync <source> <target> [--options]

Using cp will require the --recursive option to copy multiple files in a dir, while sync command will, by default, copy a whole directory. It will only copy new/modified files.

Add --delete option to remove <target> files that aren't in <source> dir.

# using new-reptiles folder as basis
docker container run --rm \
  -v ~/.aws:/root/.aws \
  -v $(pwd):/aws \
  amazon/aws-cli s3 \
  sync new-reptiles/ s3://animal-bucket/old-reptiles/

3.c `mv` move command

aws s3 mv <source> <target> [--options]

# Only markdown files are moved from new-reptiles
# to animal-bucket/old-reptiles. The rest aren't included.

docker container run --rm \
  -v ~/.aws:/root/.aws \
  -v $(pwd):/aws \
  amazon/aws-cli s3 \
  mv s3://new-reptiles/ s3://animal-bucket/old-reptiles/ \
  --recursive --exclude "*" --include "*.md" \
  --profile wasabi \
  --endpoint-url=https://s3.<region>.<provider>.com

The rest of the commands can be found in their docs.

4. Using another cloud storage (`ie` Wasabi)

Same thing with step 2:

~/.aws/credentials

[default]
aws_access_key_id=fffff3333ff55555GGGG
aws_secret_access_key=kkkkkkkkkkkkkkkeeeeeeeeeeeeeyyyyyyyyyyyy
[wasabi]
aws_access_key_id=wwwaaasssaaabbbiiiii
aws_secret_access_key=wwwwwwwaaaaaassssssaaaaaabbbbbbbiiiiiiii

~/.aws/config

[default]
region=us-west-2
output=json
[wasabi]
region=us-east-1
output=table

Or use an interactive setup. Notice I added --profile <PROFILE_NAME> option:

# interactive setup for creds
docker container run --rm -it \
  -v ~/.aws:/root/.aws \
  amazon/aws-cli \
  configure --profile wasabi

Check creds:

docker container run --rm -it \
  -v ~/.aws:/root/.aws \
  amazon/aws-cli \
  configure --profile wasabi

Doing some commands (with --profile and --endpoint-url):

docker container run --rm \
  -v ~/.aws:/root/.aws \
  amazon/aws-cli s3 \
  ls s3://wasabi-bucket/ \
  --profile wasabi \
  --endpoint-url=https://s3.us-west-2.wasabisys.com

Shorten the command with alias:

alias aws=$(docker container run --rm -it \
  -v ~/.aws:/root/.aws \
  -v $(pwd):/aws \
  amazon/aws-cli)

Errors

An error occurred (NoSuchTagSetError) when calling the GetObjectTagging operation: There is no tag set associated with the bucket.

If you came across this error while using sync, a fix could be either:

Grant the s3:GetObjectTagging permission to that user, or
adding this option --copy-props metadata-directive (it tells the cli not to get source object tags).

source can be found here.

how to remap broken keys with Xmodmap

Jaeyson Anthony Y. — Sun, 25 Oct 2020 03:51:40 +0000

We can use Xmodmap instead of installing yet-another-tool for remapping keys, ie your r or v died and you want to use a spare CapsLock + <key> to trigger that dead key.

Create a file `~/.Xmodmap`

touch ~/.Xmodmap && vim &_

Here's my example how to remap keys:

! keycode 66 is caps lock
keycode 66 = Mode_switch
keysym h = h H Left
keysym l = l L Right
keysym k = k K Up
keysym j = j J Down
keysym q = q Q z
keysym w = w W x
keysym e = e E c
keysym r = r R v
keysym i = i I Insert
keysym g = g G Home
keysym b = b B End

! ^: asciicircum, |: bar
keysym f = f F asciicircum bar

! u: Page Up, d: Page Down
keysym u = u U Prior
keysym d = d D Next

keysym BackSpace = BackSpace BackSpace Delete

if you want to find a specific key like caps lock:

# press any key to get the key code
# after running this command:
xev

Then add these to ~/.zshrc or ~/.bashrc file:

#you may logout to see changes
xmodmap ~/.Xmodmap

how to mount another drive and install updates

Jaeyson Anthony Y. — Sun, 25 Oct 2020 02:59:08 +0000

Few months ago my 9-year-old motherboard died of natural cause, leaving my ssd drive (ubuntu 18) and the rest of parts working. How can I install updates to it?

1. Check mount point of [external] drive

If you don't see a mount point of your external drive (e.g. /dev/sdc1)

# either check the mount points via
sudo lsblk -f

# or
sudo fdisk -l

Mine's showing /dev/sdc1 so we'll use that as mount point example. Otherwise skip step 1

2. Mount drive (sudoer user)

sudo mount /dev/sdc1 /mnt

# bind
sudo mount --bind /dev /mnt/dev
sudo mount --bind /sys /mnt/sys
sudo mount --bind /proc /mnt/proc
sudo mount --bind /run /mnt/run

sudo chroot /mnt

3. Install updates

Add -S for reading standard input instead of /dev/tty

sudo -S apt update

Add non-sudoer user with ssh access to a specific directory

Jaeyson Anthony Y. — Sat, 24 Oct 2020 16:52:47 +0000

Suppose you want to add another public key (id_rsa.pub) on an existing non-sudoer user, e.g. ftpuser for your teammate or another machine that you'll sshing often and you want this user to have access to a specific dir. In this example we'll use /var/www/html as the specific dir, also I'm using ubuntu as an example server.

1. (optional) where's the home dir of `userA`?

If for some odd reason your non-sudoer user has a different home directory like /var/www/html, you may want to move it back to its default dir and symlinking it instead:

# server
sudo usermod -m -d /home/userA userA

2. create `.ssh` dir and `authorized_keys` file if not exists

# server
mkdir /home/userA/.ssh && chmod 700 $_
touch authorized_keys && chmod 600 $_

3. symlink a directory (e.g. `/var/www/html`)

# server
# ln -s /var/www/html /home/userA/link_name
ln -s /var/www/html /home/userA/www

4. `authorized_keys` file in `/etc/ssh/sshd_config`

This is where we read keys that are authorized to log in:

# server
# add/update this line accordingly
AuthorizedKeysFile /home/old_user/.ssh/authorized_keys  /home/userA/.ssh/authorized_keys

then restart it with sudo service sshd restart

5. add client's public key (`id_rsa` file) to server:

let's check if we have keys:

# client
# check if there's any keys exists
ls -al ~/.ssh

# otherwise create one
# for the rsa file you could
# name it like userA_id_rsa
ssh-keygen -t rsa -b 4096 -C "your comment"

# start in background
eval "$(ssh-agent -s)"

# adds key to ssh-agent, it'll ask for passphrase
ssh-add ~/.ssh/userA_id_rsa

# copy public key to authorized_keys in server
cat ~/.ssh/userA_id_rsa | ssh sudouser@host.domain -vvv "cat - >> /home/userA/.ssh/authorized_keys"

# or if the sudo user uses key for loggin in
cat ~/.ssh/userA_id_rsa | ssh sudouser@host.domain -vvv -i ~/.ssh/sudouser_id_rsa "cat - >> /home/userA/.ssh/authorized_keys"

6. then log in:

userA@host.domain -vvv -i ~/.ssh/userA_id_rsa

# remember step 3 symlink?
# once logged in successfully, confirm if
# you can see /var/www/html in your home dir:
# ls -la ~/home/userA/link_name
ls -la ~/home/userA/www

saving ssh config

have some ssh config handy (~/.ssh/config):

Host userA.domain
  HostName host.domain
  User userA
  PreferredAuthentications publickey
  IdentityFile ~/.ssh/userA_id_rsa
  IdentitiesOnly yes
  RemoteForward 52698 localhost: 52698

then log in ssh userA.domain -vvv

DEV Community: Jaeyson Anthony Y.

Simple way to send Github events to a Discord channel using webhook

AWS S3 CLI docker for the impatient (also wasabi)

0. Things needed: Docker and AWS S3 creds (access key id/secret access key)

1. Pull Docker image

2. Make credentials

3. cp copy, sync , mv move and ls list files

3.a. cp copy command

3.b ls command

3.c sync command

3.c mv move command

4. Using another cloud storage (ie Wasabi)