DEV Community: Akash

Automate your requirements.txt with few lines of code

Akash — Mon, 21 Aug 2023 20:21:06 +0000

We all get an one common problem with what's libraries we use in our python project.Today I discovered a very simple solution.Yeah, you can also follow this process to make your SDL ( Software Development Life Cycle).I hope it will be gotcha for you.

I hope as a python developer you are familiar with pip.
Wow! you are almost done.

Step 1: Install pip-tools

pip install pip-tools

Step 2: Create a file in root directory with name requirements.in and list down libraries what you want to install.
Step 3: Compile your requirements.in file with pip-tools

 pip-compile requirements.in

Final step: Use known to all of you

pip install -r requirements.txt

Done. You get all the libraries you need at all in you requiements.txt file.

See below :

Bye . Happy Coding !! :)

What make you confused on Crypto-Js package for Node.js

Akash — Mon, 28 Nov 2022 04:33:51 +0000

Prerequisite:
1. KEY [ Private key ]
2. Secret Passphrase

What is a Private Key?
A Private Key is a string of random characters, representing a cryptocurrency wallet address, allowing you to access, receive, send your crypto funds. The Private Key is created from mixed letters and letters. Similar to a Password, it’s the key of your crypto account.

A Private Key is a string of numbers and letters with the following form:

0xb46e06d22ce739ce1961724c45acd57831a21eca12fcf691c25d0f0562b5b5f6

Main features of Private key:
Private Key contains characters including uppercase letters, lowercase letters, numbers.
The complexity of the Private Key is reflected in the random mixing of characters, without any rules, which makes it difficult for hackers to crack.
The Private Key is generated from the Passphrase by encrypting it.
Each Private Key can generate an address that allows you to make transactions in your wallet.

What is a Passphrase?
A passphrase is a sequence of words used to control access, secure, and recover your wallet in case you cannot access your main wallet. The wallet service provider will issue you a PassPhrase as soon as you create the wallet.
Passphrase is a sequence of words with the following form: race fog come flash position garbage glass rule dizzy behind use tape
Main features of Passphrase:
Passphrase is usually a sequence of readable English words, from 12 to 24 words, randomly generated.
Passphrase is mainly used to create and restore crypto wallets.

Rust with visual studio code

Akash — Wed, 23 Nov 2022 19:36:20 +0000

It is very rare who doesn't use vscode at this time. Almost all of us use visual studio code for our daily development and when we learn new technologies or new languages we always prefer our daily uses IDE or editor what you say.

So who are new to learn rust as usual you also finding some extension if i not wrong. Here is my preference to use this extensions to easy your journey with Rust and your beloved visual studio code.

Recomanded:

1. Rust-analyzer

Most probably you came across with official rust extension for vscode. At this time of writing rust official extension deprecated now.which was not able to go to definition.
By the way , rust analyzer solve this .
see more

2.Better TOML

If you came from node.js ecosystem , you all know node.js use package.json file to track their dependencies and for many other things which is essential to run a node project.Rust also use something like that. But difference is rust doesn't use package.json file instead it use cargo.toml file.But problem is vscode doesn't recognize .toml file .That's why we don't get color highlighting feature.
see more

Optional:

1. CodeLLDB

CodLLDB extension helps to debug your code. When one new on a new language to debug our code we use console.log or print something like that. To get rid of this kind of action CodeLLDB help us more.
see more

2. Crates

This extension is not for only rust. Cargo is the package manager of rust. You can check the dependencies of your packages in cargo.toml file.Here is a common problem of detecting outdated packages and sometimes there exist vulnerabilities with outdated packages .so it is good to be up to date with your used packages.Crates extension helps us to know about it.
see more

Happy coding with rust.

Multiple git account to maintain github bitbucket .. etc with different account from a single machine

Akash — Tue, 22 Nov 2022 12:11:34 +0000

Sometimes we need to config our local machine to make contribution on open source project as usual to work on our professional workspace also. It also happened that you are tightly coupled to use your official email account which is bind with your official repo.
On such a moment very often we need to maintain your personal repo or whatever you say. To contribute on this repo, every time you need to switch and config your git for every workflow. That's not good enough. So we need a optimal solution to maintain this obstacle since it is not an obstacle. Git also provide a way to maintain this. To understand this we need to deep drive in git mechanism.

But we have not time to learn git first on large scale to do this things at this first running world. :)

Let's follow the steps:

You need to generate different SSH key for each an every account. Your each SSH key is the identity of your account. To generate SSH key :

ssh-keygen -t ed25519 -C "your_email@example.com"

Let we are generate two account for this time one for user_one and another is user_two. Since for each ssh-keygen command, it create two file of public key and private key.
For our case it will create 4 file .(Here we use ed25519 algorithm to create SSH key.).For each keygen it ask you to make custom file name if any one want, so distinguish that's two file at working time, it is best choice to change file name with as you prefer.
[ By default this command generate file with name of id_{algorithm name}. so our case one file will be id_ed25519( private SSH key ) and other one is id_25519.pub ( as public SSH key ) ].
For our better development we need to change file name without changing id_{algorithm_name} part. Excluding change full name we add our prefer name to make unique this file we just add an extra name with this file. Like id_ed25519_user_one.

Finally we got four SSH key file :

id_ed25519_user_one id_ed25519_user_one.pub id_ed25519_user_two id_ed25519_user_two.pub

Step 2: Now we need to make a config file to say our git machine how it know which account we want now.
Make a config file without extension. Past below code

.ssh/config                                                  file

Host user_one github.com
    HostName github.com
    PreferredAuthentications publickey
    IdentityFile ~/.ssh/id_ed25519_personal_user_one

Host user_two bitbucket.com
    HostName bitbucket.com
    PreferredAuthentications publickey
    IdentityFile ~/.ssh/id_ed25519_personal_user_two

step 3: How to clone repo for different account ?
Go to the github account . Press clone button it will pop up option on which option you want to clone. Make sure you are going with SSH option . I am make it clear later.

Step 4: Open your terminal . Make clone command in your terminal.
In general case we clone repo like:

git clone git@github.com:user_name/DS-ALGO.git

But in this case we need to make a pretty change in our command. Since you make config file to make decision which account you want , that's why just change [ git@******:user_name/DS-ALGO.git ] *(astarick) part.
Now make command like:

git clone git@user_one:user_name/DS-ALGO.git.

As a result now git can understand by which account you want to clone repo .

And finally you are done with multiple git account.

Last question over this process is how we make push and all other command. Are those command work by this process ?
Yes by this process all of the command and features of git will work pretty well. But you remember, I said in step 3 that make sure you clone your repo with SSH key. It is the main key of this way. When you clone your repo with SSH key it will automatically config your local directory( Local repo ) with proper config. To discover you can see .git folder in your local repo.

Location: .git/config

[core]
    .
    .
    .
[remote "origin" ]
    .
    . Find here
    .
    .
[branch "main"]
    .
    .