Forem: darker

How to execute any command from anywhere to anywhere in your laptop !

darker — Sun, 18 Dec 2022 12:13:56 +0000

Sometimes i got in situations where i want to execute a specific command or multiple commands inside a given directory without moving there as quickly as i can !
This may sound obvious to just jump there, do the stuff and come back but as a lazy guy, i like doing that as quickly as possible and hit enter once !

So in this tip, you will need zoxide, a nice tool that cache all your paths by their finals dirname, that mean wherever you are in your linux system ~/zig/zag/toum/yyyy, you just have to type cd xxxx (which is here ~/boum/bam/xxx), to go there !

So this is my tip:

go to the target dir ($1 as the given dir)
execute the command ({$@:2} as all strings after the dir)
get back from where i was (cd -)

Then add it inside your ~/.bash_aliases and you're good to go !

You can copy the source code from here !

How to list commits from the current branch.

darker — Sun, 28 Aug 2022 13:18:37 +0000

Let's say, you're on your terminal and you want to have the list of commits from your current branch !

There is some tricks to do that, the faster one is just to git log and scroll !
But i found useful to made a simple alias to do so !

As you can see, this is quite simple, it's a combination of 2 main commands i set up in my ~/.gitconfig as an alias :

[alias]
    ; to list commits from the current branch
    commit-list = !git log --no-merges --oneline --decorate master..$(git branch --show-current)

HOW

First, i need to get the branch where i am right now, and to do that, i use git branch --show-current
Second, am going to compare with git log, the difference commits from my branch to the master branch, because i don't want merges, nor too much details, i added two flags, --no-merges and --oneline + a simple --decorate. git log --no-merges --oneline --decorate

DEMO

PS: Don't worry about the "passphrase" on the demo, i added a lot of security checks for any git command on my local machine, i may do a future post about that soon !

EDIT : From Christophe Colombier, you can do the same thing with a native command, such as : git cherry -v origin

Thanks for reading, feel free to like and/or subscribe for more 🐼.

How to git resolve conflicts quickly from two commands lines.

darker — Sat, 20 Aug 2022 11:51:27 +0000

When rebasing/merging, you may face sometimes conflicts, and if you're like me... "LAZY", you just want to get all new changes from the main branch or keep all your current changes as fast as possible depending on the file !

So, for conflicts on some file, you may need to get incoming changes or keep your current changes ! I made two alias for that, git add-their and git add-our !

Under the hood, what it's done is quite simple, in your ~/.gitconfig section, you just have to add those lines :

[alias]
      add-their = !git checkout --ours $@ && git add $@
      add-our = !git checkout --theirs $@ && git add $@

So, how this work, it's mostly two main commands, a checkout command and an add command, let's focus on keywords (theirs and ours) and how they are reverted !

In a context of rebasing, if you're willing to set current changes with these aliases, you should do git add-our and git add-their for incoming ones, that logic is inverted when you're dealing with merge conflicts. this is a good article that go deeply on explanations !

IMPORTANT NOTE : these aliases are only for the one knowing what they are doing, cuz on a complicated conflicts, there is some stuff you will want to keep on both side !

Bash and exclamation marks !!!!

darker — Thu, 18 Aug 2022 14:40:33 +0000

In case you didn't know, exclamation marks play an important role in the bash workflow, especially for your command history!

ok... let me explain this weird thing, actually it's simple :

The first part of the command will take the first command item from the second most recent command you wrote, then concatenate to "add" and the second item of the most recent command, git add second_folder.
For the second part, it's a substitution command of "status" by "checkout" for the second command that i wrote, in reverse order on my bash history; it will take as arguments, those that i gave to my second command in the same order.
That said, the output of this command will be:
git checkout second_folder

Pretty NEAT right !?

So let's talk about it, the ! invokes history expansion, a feature that originally appeared in the C shell, back in the days before you could count on terminals to have arrow keys. It's especially useful if you add the current command number to the prompt (PS1="\!$ ") so you can quickly look at your screen to get numbers for past commands.

So, am not going to go deep inside possibilities here but just give some cool cheat-sheets from exclamations marks when you're on your terminal !

This is a pretty short list of the cool ones :

!! run the latest command,
```
 # Ex :
 $ apt-get update
 $ sudo !!
```
!-3 run the third command in the reverse order from my bash history; this is also available for positive values such as the first command, from your ~/.bash_history -> !1

!* get arguments passed to the most recent command ran,

 # Ex :
 $ touch filex, test4, example
 $ chmod 777 !*

!ls to run a command from your history starting with ls

With these 4 items, you can basically play/mix around with your bash history and get great stuffs like the one up there with a substitution string.

Thanks for reading, feel free to like and/or subscribe for more 🐼.

How to count lines of your code from your SHELL.

darker — Mon, 15 Aug 2022 21:42:30 +0000

So, this one is quite simple, let say, you want to count the lines of code you have inside a project, from a file or a whole directory, how are you going to do it ?

HOW

This is done with a simple bash function

loc(){
    echo -ne "Lines of Code : ";
    if [ -n "$1" ]; then
        find . -wholename $1 | xargs wc -l;
    else
        find . -name '*' -type f | xargs cat | wc -l;
    fi
}

Basically, it will find files depending on your input and use wc to count lines of your code.

You can then add this in your ~/.bashrc and source before use it or save it in separate shell file that you can call and use when you want !

Thanks for reading, feel free to like and/or subscribe for more 🐼.

How to copy/paste files/directories into non-existent destination path

darker — Sat, 13 Aug 2022 18:24:40 +0000

Have you ever tried to copy some file(s) or directory(ies) to a destination that doesn't exist yet ? It's possible with a smart bash function !

HOW ?

How to obtain that ?
Using this bash script function :

cpd(){
    mkdir -p "$(dirname ${@: -1})"
    cp -r $@
}

First, we create recursively the destination folder by getting the dir name of the last argument passed to the function.
And we copy recursively depending on the array of arguments passed to the function.

As the final step, You just have to add it in your .bashrc, source ~/.bashrc and you're good to go !

DEMO ?

Thanks for reading, feel free to like and/or subscribe for more 🐼.

How to clone a sub directory of a git project (not a zip)

darker — Fri, 12 Aug 2022 19:10:19 +0000

Have you ever tried to get a folder from a git repository either on github, gitlab or bitbucket ?

hop hop hop, am not talking about Downloading a ZIP folder (like DownGit does), but only cloning a sub-directory with the git clone... command !

I got that question from a friend, and i wrote a small and interesting bash script to do so !

We're going to do that in 2 steps.

WRITE A BASH SCRIPT FUNCTION

We're going to write a function in our .bashrc that will update our sparse-checkout like this :

_git_clone_sub ()
{
    REPO_NAME="$(echo $2 | grep -oE '[^/]+$')";
    git clone --filter=blob:none --no-checkout $2
    cd $REPO_NAME;
    git sparse-checkout set --no-cone "$1/*"
    if [ -n "$3" ]; then
        git pull origin $3;
        git checkout $3;
    else
        git fetch origin;
        git checkout main
        [[ $? != 0 ]] && git checkout master;
    fi
}

This script is quite simple, this is what it does:

Extract the repo name from the link (github.com/author/repo-name).
Create a git project with the repo name + add the origin from the link.
Then update the tree configuration of our project.
As an optional parameter, we have the branch, if it's provide, the script will clone a sub directory from that branch, otherwise, it will clone from master (you can change that with main if you want).

Now we can easily clone sub directories like this (after a source ~/.bashrc) :

_git_clone_sub subDir1 https://github.com/auth/repo

or by specifying the branch name :

_git_clone_sub subDir1 https://github.com/auth/repo dev-branch

WRITE A GIT ALIAS

So far so good... but we can do better !
We could call that bash function from git directly by adding an alias in our ~/.gitconfig file like this :

[alias]
    clone-sub = !bash -i -c '_git_clone_sub "$@"' -s

Yeah yeah wait a minute, i know, that one looks weird, but let me explain... it's actually simple !

First, since we are going to run a bash function, we embrace that with 'bash -c'; then we call our function.
The $@ is to get all arguments got using the -s flag at the end of the alias.

That's been said, you can now do :

git clone-sub subDir1 https://github.com/auth/repo

git clone-sub subDir1 https://github.com/auth/repo dev-branch

DEMO

Thanks for reading, feel free to like and/or subscribe for more 🐼.

Delete multiple locals branches in two commands

darker — Thu, 02 Sep 2021 10:37:51 +0000

Sometimes, we forgot about all branches we're creating when coding, bumping versions, and doing some releases, in result we can have a lot of useless branches in our local project... and it can become frustrating when you need to switch from a branch to another one.

Soooo, i made a really simple and short bash script to help me delete multiple branch at the same time called gbd, like git branch delete, yeahhh yeah i know, too lazy... and the code looks like this :

#!/bin/bash
# by d4rk3r

# this function will loop over the list of branches you provided
# and if the branch name is upper than 2
# it will delete it
#
# $1 can be a file_name or an <<EOF ... EOF
_del_branch_list(){

    for bb in $(cat $1);
    do
        if [ ${#bb} -ge 2 ];
        then
            echo "[-] Deleting '$bb' branch..."
            git branch -D "$bb" # we delete the branch
        fi
    done
}

# the main function
main(){

    echo "[-] Deleting locals branches is my job"!
    _del_branch_list $1
}

main $1

After saving that file and add an alias to it in your .bashrc, you just have to work with two commands:

First, i need to get the list of commands, and i can have that by hitting git branch, as an output, i can have :

  chore/some-bump-here
  chore/some-bump-here
  chore/some-bump-here
  chore/some-bump-here
  chore/some-bump-here
  chore/some-bump-here
  feat/some-feature-here
  feat/some-feature-here
  feat/some-feature-here
  feat/some-feature-here
  feat/some-feature-here
  feat/some-feature-here
  feat/some-feature-here
  feat/some-feature-here
  feat/some-feature-here
  feat/some-feature-here
  feat/some-feature-here
  feat/some-feature-here
  feat/some-feature-here
  feat/some-feature-here
  feat/some-feature-here
* master
  release/some-release-here
  release/some-release-here
  release/some-release-here
  release/some-release-here
  release/some-release-here
  release/some-release-here
  release/some-release-here
  release/some-release-here
  release/some-release-here

I just have to select multiple branches and copy that

Second, i can jut call the bash script and pass what i just copy in parameters like this (and add at the end the EOF then press ENTER):

d@k:project$ gbd <<EOF
> release/some-release-here
> release/some-release-here
> release/some-release-here
> release/some-release-here
> release/some-release-here
> release/some-release-here
> release/some-release-here
> release/some-release-here
> release/some-release-here
>
> EOF

output :

[-] Deleting locals branches is my job
[-] Deleting 'release/some-release-here' branch...
[-] Deleting 'release/some-release-here' branch...
[-] Deleting 'release/some-release-here' branch...
[-] Deleting 'release/some-release-here' branch...
[-] Deleting 'release/some-release-here' branch...
[-] Deleting 'release/some-release-here' branch...

Source code : https://gist.github.com/Sanix-Darker/f93b7fc029fc82e37d53693eca8d8471

Have FUN !

git search for code whatever the branch, the time or the commit

darker — Sat, 21 Aug 2021 09:56:41 +0000

Git has a nice feature called grep, when you want to get a commit for an old code, and it's a kind of search, but not enough for me !
I wrote a bash script to search for a "piece of code" inside a git project history whatever the branch and time.

It can :

Search a word and return the list of commits where the word was found.
Switch the project to the target commit, open the file at the specified line, for you, to copy your code, then restore yourself to your working branch !

If we save the file as ./gf.sh, we give execution rights chmod +x ./gf.sh and we add it in our .bashrc as an alias : alias gf=${HOME}/gf.sh.

We can wrote interesting command easily.

Example :

$ gf search 'vieux code'
$ gf open 'commit-id:fichier:ligne'

This is how the code looks :

#!/bin/bash
# by d4rk3r

# A smart way to search for a code
# inside your git history whatever the branch you're

# -- Setup :
# -- After getting the bash script

# chmod +x /path/to/gf.sh 
# -- to add the execute right to the script
# -- You can add it to your .bashrc env

# gf s 'pattern' -- to search for some code
# -- then after copy the line of the commit,

# gf o commit_id:line:file_name....
# -- gf will switch to that commit and open the line where the code is,
# -- after quitting, gf will restore your repo to the precedent branch where you were working

_git_search(){
    # a smart git command to get commit, file and line where
    # the string is available
    git rev-list --all | (
        while read revision; do
            git grep -n -F ${1} $revision
        done
    ) > ${HOME}/.gf-out
}

_search(){
    echo "[-] Searching for '${1}' in this repo..."
    sleep 2
    # We less in the list of results
    _git_search "${1}"
    cat ${HOME}/.gf-out | less
}

_open_code(){
    # getting your current branch
    branch=$(git branch | sed -n -e 's/^\* \(.*\)/\1/p')

    # A smart split from the incomming $1 parameter
    arr=($(echo "$1" | tr ':' '\n'))
    commit=${arr[0]}
    file=${arr[1]}
    line=${arr[2]}

    # some verbose
    echo "[-] Moving on commit : $commit"
    sleep 1
    echo "[-] Moving on file : $file"
    sleep 1
    echo "[-] Moving on line : $line"
    sleep 1

    # A checkout on the commit then a less on the line of the file
    git checkout "$commit"
    less +"$line" "$file"

    sleep 2
    echo "\n[-] Rolling back to your precedent branch..."
    # comming back to reality
    git checkout "$branch"
}

_help_commands(){
    echo "[-] gf help center:"
    echo "[-] gf s 'search-kwy-word'"
    echo "[-] gf o 'commit-id:line:file-name'"
}

main(){
    echo "[-] gf started..."

    if [ "$1" == "search" ] || [ "$1" == "s" ]; then
        _search $2
    elif [ "$1" == "open" ] || [ "$1" == "o" ]; then
        _open_code $2
    else
        echo "[x] Error: Bad parameter provided..."
        _help_commands
    fi
}

main $1 $2

Source code : Gist-Code

Have FUN !

Asymetric RSA encryption/decryption of your clipboard

darker — Sat, 21 Aug 2021 09:40:25 +0000

Do you trust your clipboard enough to copy secret information like credentials, tokens, etc... into it ?

In fact it's possible for an hacker to watch changement from your clipboard and get all text/elements you're copying/pasting, in this case using xclip !
So i was thinking about a solution on hide what am copying so that if the hacker get the content of my clipboard he will not get anything from it !

I did asymmetric clipboard encryption using RSA with bash, you can customize the paths of your public/private keys.

Then I added shortcuts to my system to encrypt the data I'm copying... using Ctrl+Alt+C instead of Ctrl+C and to paste, 'Ctrl+Alt+V' instead of 'Ctrl+V'...

#!/bin/bash
# By d4rk3r

# This script can :
#    - generate keys pair (rsa 2048)
#    - rsa encrypt the content of your clipboard/selected element
#    - rsa decrypt the content of your encrypted clipboard storage

# requirements :
# - apt install xclip
# - apt install openssl
# - apt install xdotool

PUBLIC_KEY_PATH="${HOME}/.css/darker.pub"
PRIVATE_KEY_PATH="${HOME}/.css/darker.pri"

# the path where the encrypted data will be saved
SECRET_STORE_PATH="${HOME}/.css/css_secret_store.dat"


_generate_keys(){
    mkdir ${HOME}/.css/

    openssl genrsa -out $PRIVATE_KEY_PATH 2048;
    openssl rsa -in $PRIVATE_KEY_PATH -out $PUBLIC_KEY_PATH -outform PEM -pubout
}

_copy_encrypt(){
    # We get the output of xclip and encrypt it
    echo "$(xclip -o)" | openssl rsautl -encrypt -inkey $PUBLIC_KEY_PATH -pubin -out $SECRET_STORE_PATH

    # We save a custom message to the clipboard
    echo "-css-encrypted-value-" | xclip -i
}

_decrypt_paste(){
    # We decrypt using our private key
    string=`openssl rsautl -decrypt -inkey $PRIVATE_KEY_PATH -in $SECRET_STORE_PATH`;

    # We print to the clipboard de decrypted value
    sleep 0.5;
    xdotool getactivewindow type "$string"

    echo "" | xclip -i
}

_help_commands(){
    echo "./css.sh gen # To generate keys pair"
    echo "./css.sh enc # To encrypt the clipboard selection/saved"
    echo "./css.sh dec # To decrypt the clipboard and put"
}

# The main function
main(){
    if [ "$1" == "generate" ] || [ "$1" == "gen" ]; then
        _generate_keys
    elif [ "$1" == "encrypt" ] || [ "$1" == "enc" ]; then
        _copy_encrypt
    elif [ "$1" == "decrypt" ] || [ "$1" == "dec" ]; then
        _decrypt_paste
    else
        echo "[x] Error: Bad parameter provided..."
        _help_commands
    fi
}

main $1

Source code : github project

Have FUN !

Test your entire project(Php, Js, Python, Ruby) with just comments.

darker — Wed, 10 Mar 2021 16:16:20 +0000

Hey there, today am presenting you something really special i made about tests, i hope you're going to like the way i build this solution !
Now, let's jump into it !

Introduction

Let's face it frankly, tests are certainly important but they are sometimes extremely boring to write, when you couple that with the fact that each language or each framework has its own way of handling unit tests, it does not help them. things !

So I asked myself a fairly simple question, is it possible to manage unit tests in a universal way whatever the programming language "script" or the framework !

1-) First question: What do all code projects have in common?

The answer is quite simple, the comments; they are the only elements which are present in almost any project, whether it is with a scripting language or a compiled language.

2-) Second question: How can we transform simple comments to unit tests ?

Here we are trying to create a system that will do unit tests in a file or a project based on comments, so it was a question for us to define a kind of uniform syntax whatever the programming language in which we are, then create a pseudo test environment like a file in which we put all the elements of testa class and we test the corresponding assertion !

Behind all of this we would have a cli program that will browse and fetch all tests cases and test them to generate a final report.

For a simple assertion we end up with something like this :

# ::testa_start::
# ::case_start::
# >> testa.isEqual(2, 2)
# << true
# ::case_end::
# ::testa_end::

In this example, we use ::testa_start:: and ::testa_end:: to surround our pseudo test environment, we can now define a test case with ::case_start:: and ::case_end::, then using >> and << to define the expected inputs and outputs, here testa.isEqual just checks if 2 is equal to 2, and we expect a true in output, we also have testa.isSup, etc ...

With this structure, we can therefore structure several test cases in a single test pseudo environment in the code :

# Inside a python code

# ::testa_start::
# ::case_start::
# >> testa.isEqual(2, 2)
# << true
# ::case_end::

# ::case_start::
# >> testa.isSup(3, 2)
# << true
# ::case_end:

# ::testa_end::

What should be remembered here is that if I want to do the same tests on javascript for example, I just have to replace the comments because, on javascript, the comments per line are // and not #; so we are going to have :

// Inside a javascript code

// ::testa_start::

// ::case_start::
// >> testa.isEqual(2, 2)
// << true
// ::case_end::

// ::case_start::
// >> testa.isSup(3, 2)
// << true
// ::case_end:

// ::testa_end::

3-) Third question: How to encapsulate a method and define the correct output relative to a precise input ?

Just like the assertion of a simple test case, we define a precise syntax to surround our method !

# ::testa_start::
# ::case_start::
# >> addition(2, 2)
# << 4
# ::case_end::
# ::code_start::
def addition(a, b):
    """ This method will return the sum
    of a and b """

    return a+b
# ::code_end::
# ::testa_end::

Unlike the simple case tests, here we have ::code_start:: and ::code_end:: which define the pieces of code that must be taken into account in the pseudo test environment.

After the execution of the tests in a file/project, testa we generate a test report parraport to the tests which are in success and those which are in failed !

4-) Fourth question: How to manage imports from external libraries !

In some cases we often have functions that call external libs or other functions in other files, to solve this problem, I added to the syntax of testa ::import_start:: and ::import_end::, this part in a file includes all the imports which will be necessary for the tests in each pseudo environment (files with assertion).

# ::import_start::
Your imports here
# ::import_end::

5-) Fifth question: How to standardize these tests with only one command line.

For this last problem I used the configuration file model, a bit like the package.json with npm or yarn, in this case tesla.json, but a fairly simple file which describes which directory (file or project) to test, from which language it is and what is the interpreter that must be used, so we have this semblance of structure:

An example on PHP:

{
    "module": "ta-php",
    "path": ["./square.php"],
    "extensions": [".php"],
    "launcher": "php"
}

An example with python:

{
    "module": "ta-py",
    "path": ["./sha256.py", "./square.py"],
    "extensions": [".py"],
    "launcher": "python"
}

An example on Ruby:

{
    "module": "ta-rb",
    "path": ["./my_ruby_app/", "./square.rb"],
    "extensions": [".rb"],
    "launcher": "ruby"
}

Conclusion

In conclusion, we can say that we have made a kind of library which works on the CLI allowing to do unit tests whatever the scripting programming language is and to set it up, it's quite simple.

Testa is a free and open source project, this is some link !

Source code : On github,
The demo : VIDEO-DEMO

Thank you for reading, make sure to like, suscribe or leave a comment !

Video+Audio conferencing in your terminal !

darker — Sat, 06 Mar 2021 12:08:07 +0000

Yeah i know, what you guys are thinking "Why ?", "Why do you do that ?", well "just for fun ?" and a way to mastering "real-time parallelism", this is also my first POST ever made!

Let's jump into it !
First of all, a videoconferencing system is a real-time application which consists in broadcasting to each person connected the audio and video stream of all the other participants with the least possible latency !

As I had to work on the terminal, I only had characters and "bytes" for data entry!

First question : how to transform an image into a perceptible string of characters on a terminal ?

My algorithm is very simple, I first use OpenCv to retrieve the image that the camera /dev/0 device gives me, after that, i convert to black on white using the cvtColor method from OpenCV; then i cut this image into a sort of grid which gives me the color contrast by squares ranging from 0 to 255, I have a sort array equivalence of each pixel! By setting another array of characters ranging from "" to "B", I have a match against the occupancy rate in the pixel !
To complicated ?

Let me explain again, more a pixel is dark, the less dense the character will be, so we will have either a "." or a "," with the color value 10 or 12 unlike "B" or "K" which is closer to 250 or 255 From there, I manage to have my transcription of a color image in characters on a terminal !

Second question: how to retrieve the audio stream and transmit it ?

To do this I use PyAudio which connects to the microphone to retrieve the audio stream, then transmit it in the form of bytes per sequences, at the reception, i do a remodeling according to bit rate !

Third question: how to send and retrieve the stream(video and audio) for each session ?

Here I am using a byte formatting system in json by adding elements allowing me to identify the one sending and in which session it is sending it, when a client retrieves the data, analyzes it, then retrieves the contents of the package

Fourth question: how does security work in such a system ?

I have implemented two types of data encryption, asymmetric encryption and symmetric encryption, for both systems there is key sharing that needs to be done first, but in the version being tested I have disabled all encryption, as this has an impact on the final rendering quality!

AES (Symmetric encryption)	RSA (Asymmetric encryption)

To use s2c, just install it via pip !

pip install s2c

Start the server :

s2c_server -p 1122

Then start the client :

s2c -s session1 -c darker -i 127.0.0.1 -p 1122

Or you can use help to see the manual :

Of course, all this article would be useless without a DEMO: WATCH ME

s2c is Open Source and free !

Source Code : https://github.com/sanix-darker/s2c
Pypi-Package : https://pypi.org/project/s2c/

PS : Any comments or constructive advice are welcome !