DEV Community: Yuil Tripathee

So I tried Odoo for the first time

Yuil Tripathee — Thu, 06 Jun 2024 01:57:53 +0000

From web developer's viewpoint, I'm going to setup Odoo for the first time. It is going to installed on my local computer (Ubuntu 22.04) and the installation will be from community edition.

Prerequisites

Git, Python (3.10+), Pip and basics (IDEs and stuff)
PostgreSQL database (can be community edition)

Initial steps

This is coming from Odoo's official documentation.

Fork the GitHub repo for the community edition.
Create a new postgres user. Odoo does not accept postgres default user.

sudo -u postgres createuser -d -R -S $USER
createdb $USER

Running Odoo for the first time

The two new databases created on PostgreSQL are: $USER whatever your username is and the other one called mydb. Run this command after you clone the Odoo repo and cd inside.

python3 odoo-bin --addons-path=addons -d mydb

After the server has started (the INFO log odoo.modules.loading: Modules loaded. is printed), open http://localhost:8069 in a web browser and log into the Odoo database with the base administrator account: use admin as the email and, again, admin as the password.

Check the database schema

I ran the ERD for database tool in pgAdmin to inspect the database design for the Odoo community base platform.

From the start there are 114 tables linked in a mesh. So, I chose to dig into the database structure a bit further.

Findings

Odoo's database model is quite mature as of Version 17 and incorporable to wide contextual range.
The database structure is monolith. Therefore, decoupling into possible micro-services would be a good prospect as some modules requires scaling different than the other.
You can refer to Server Framework 101 guide in order to develop your own modules.

References

Odoo on-premise setup from source guide

Reverse engineering C code with Cflow - GNU project (to trace back calling)

Yuil Tripathee — Sun, 14 Jan 2024 17:42:09 +0000

Install the program in Linux (Ubuntu used for this test case) using the below command:

apt search cflow
sudo apt install cflow

After this, go to the specific project folder. To run the analysis, you can run the following command.

cflow --verbose --tree main.c

In this example, we can analyze main.c. Changing the file name allows us to check other files as well. The output is printed on ASCII tree format with quality details. Now, you can use this information to draw on the software design applications such as PlantUML or StarUML manually if you would like to have a graphical presentation of your reverse analyzed C code.

Here's the example printout:

+-main() <int main (int argc, char *argv[]) at main.c:26>
  +-printf()
  +-serial_open()
  +-WitInit()
  +-WitRegisterCallBack()
  +-SensorDataUpdata() <void SensorDataUpdata (uint32_t uiReg, uint32_t uiRegNum) at main.c:100>
  +-AutoScanSensor() <void AutoScanSensor (char *dev) at main.c:142>
  | +-serial_close()
  | +-serial_open()
  | +-WitReadReg()
  | +-Delayms() <void Delayms (uint16_t ucMs) at main.c:136>
  | | \-usleep()
  | +-serial_read_data()
  | +-WitSerialDataIn()
  | \-printf()
  +-serial_read_data()
  +-WitSerialDataIn()
  +-Delayms() <void Delayms (uint16_t ucMs) at main.c:136>
  | \-usleep()
  \-serial_close()

The source is from Linux C SDK for Witmotion IMU sensor. Here's the link for documentation: https://support-73.gitbook.io/witmotion-sdk/wit-standard-protocol/

Redpanda setup in Linux: Installing Redpanda in Zorin 16.3

Yuil Tripathee — Fri, 29 Dec 2023 23:48:24 +0000

I had to modify the default setup script as below, to mask distro as Ubuntu: [1]

Process

#1 Getting things ready

curl -1sLf 'https://dl.redpanda.com/nzc4ZYQK3WRGd9sy/redpanda/cfg/setup/bash.deb.sh' | distro=ubuntu version=20.04 codename=focal sudo -E bash

Finally, try running apt search redpanda and check if there's the setup. You can gently install with the apt command now:

#2 Install and tune

sudo apt install redpanda redpanda-console

You can find this as the installation is completed:

Redpanda Console is installed succesfully. To start Console, run the
following:

    sudo systemctl start redpanda-console

Setting up redpanda (23.3.1-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/redpanda-tuner.service → /lib/systemd/system/redpanda-tuner.service.
Created symlink /etc/systemd/system/multi-user.target.wants/redpanda.service → /lib/systemd/system/redpanda.service.
redpanda:x:129:138::/var/lib/redpanda:/usr/sbin/nologin
redpanda:x:138:

To get the most out of the fastest queue in the west, enable production mode by
running the following:

    sudo rpk redpanda mode production

followed by:

    sudo rpk redpanda tune all
    sudo systemctl start redpanda

This will autotune your system to give you the best performance from Redpanda.
You can get more information on the tuning parameters here:
https://docs.redpanda.com/docs/introduction/autotune/

I also ran this in sequence (to go to production mode). Find you redpanda console at http://localhost:8080/overview.

Here's how tuning looked like for the first time when I did it:

user@laptop:~$ sudo rpk redpanda tune all
Restarting & Configuring 'irqbalance' with banned IRQs '[123]'
Restarting & Configuring 'irqbalance' with banned IRQs '[140]'
TUNER                           APPLIED         ENABLED         SUPPORTED       ERROR
aio_events             true   true   true   
ballast_file           true   true   true   
clocksource            true   true   true   
coredump               false  false  true   
cpu                    true   true   true   
disk_irq               true   true   true   
disk_nomerges          true   true   true   
disk_scheduler         true   true   true   
disk_write_cache       false  true   false  Disk write cache tuner is only supported in GCP
fstrim                 false  false  true   
net                    true   true   true   
swappiness             true   true   true   
transparent_hugepages  false  false  true

#3 Enjoy

You can expect this kind of dashboard opening on that URL.

Playing with clusters

sudo rpk container start -n 1

sudo rpk container purge

References

Docker setup in Linux: Setting up docker in Zorin 16.3

Yuil Tripathee — Fri, 29 Dec 2023 23:06:56 +0000

As Zorin 16.3 is based on Ubuntu/focal, there's a little workaround to have a usable docker setup.

Process

#1 Install Docker system

As you need to create containers, you need docker to do so. Here's simple process just cited from multiple references.

# preliminaries
sudo apt-get update
sudo apt-get install ca-certificates curl gnupg

Need to add keyrings:

# keyrings
sudo install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg — dearmor -o /etc/apt/keyrings/docker.gpg
sudo chmod a+r /etc/apt/keyrings/docker.gpg

Adding apt source next:

echo \
“deb [arch="$(dpkg — print-architecture)" signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu \
"$(. /etc/os-release && echo "$VERSION_CODENAME")" stable" | \
sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

I recommend this step to be done manually if you happen to face any issue. You should shoud be able to have contents as in below in the /etc/apt/sources.list.d/docker.list file. I've manually written this after running into a little issue which works like a charm now.

deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu   focal stable

After that its just installing stuffs:

# installation just starts now
sudo apt-get update
sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

Finally, testing step is as an usual hello-world container.

sudo docker run hello-world

Now, you're good to go if you see welcome message running down this hello-world container. Go through this link if you've been facing issues with APT repository. [3]

#2 Docker Desktop

A GUI makes it easy to navigate through the whole docker system. Have a look here to setup docker desktop after installation of docker system. Here's the summary: [2]

# if don't exist
sudo apt install gnome-terminal

# removing previous installations
sudo apt remove docker-desktop
rm -r $HOME/.docker/desktop
sudo rm /usr/local/bin/com.docker.cli
sudo apt purge docker-desktop

# install by apt after downloading from the page
sudo apt-get update
sudo apt-get install ./docker-desktop-<version>-<arch>.deb

# launch
systemctl --user start docker-desktop

Next time if you want to upgrade the application, its quite easy:

sudo apt-get install ./docker-desktop-<version>-<arch>.deb

Check the whole installation as below:

docker compose version
Docker Compose version v2.17.3

docker --version
Docker version 23.0.5, build bc4487a

docker version
Client: Docker Engine - Community
 Cloud integration: v1.0.31
 Version:           23.0.5
 API version:       1.42
<...>

#3 Optional: Install kubernetes

As you've installed docker desktop, you can do this installation from the GUI settings in the app quite easily.

References

Network interfacing issues faced using WSL 2 (and fixes)

Yuil Tripathee — Wed, 19 Apr 2023 17:05:18 +0000

#1 - Memory not releasing back

It becomes overload to the system and eventually leading to Blue Screen of Death if not treated on time.

# only termination (still VM is alive)
wsl -t kali-linux

# shutdown
wsl --shutdown kali-linux

#2 - WSL2 network ports are virtual and cannot be accessed from LAN

# for port forwarding
netsh interface portproxy add v4tov4 listenport=8001 listenaddress=192.168.0.10 connectport=80 connectaddress=192.168.0.10

# for listing
netsh interface portproxy show all

# for cleanup
netsh interface portproxy reset

# or,
netsh interface portproxy delete

# ON and OFF
netsh interface portproxy add v4tov4 listenport=4422 listenaddress=192.168.1.111 connectport=80 connectaddress=192.168.0.33

netsh interface portproxy delete v4tov4 listenport=4422 listenaddress=192.168.1.111

You need to get Linux IP (use ip route). Check official docs for more information. Also, you can use NGINX with the following configuration:

events {}

http {
     server {

        listen 192.168.1.111:4422;

        location / {
            proxy_pass http://192.168.2.33:80/;
        }
     }
}

Web Dev setup in WSL2 Kali Linux 2022 Edition - Part 2: Coding Tools setup - Python, C++, Go, JS, PHP

Yuil Tripathee — Sat, 04 Jun 2022 18:48:45 +0000

Please be noted that the whole or a part of the article is applicable in the full Linux installation.

Before beginning be sure to check the IP address of your VM and the host machine. This is better to know when you are working with WSL2. You can get the IP address using ip route command in your Linux terminal. For some cases, like in the apache2 server, it has been found that loopback for http://localhost:80 works properly even when running the g Apache server on WSL2.

Code Editor (Visual Studio Code)

I have been using Visual Studio Code for a long time (since 2016), and I realized programming experience is lit💯. Also, the plus is it keeps evolving and getting better over time. To work on WSL with VS Code together, VS Code is installed in Windows and called from the WSL system as simple as a code command.

Python

We would certainly get python3 pre-installed in the Linux system, but if not, then just install using sudo apt install python3 in the terminal. Type python3 and you will get an interactive environment. If this works, you have just confirmed your python setup is working properly. Check man python3 for more details.

Python virtual environments

Python setup can be fun, to begin with, but can go tricky when you pursue advanced stuff in it. Managing packages using virtual environments is aa a new chore here to do things more proficiently. Here in this setup, we will simply use venv based approach.

python3 -m venv [LOCATION] # to create a source for a new virtual env.

source [LOCATION]/bin/activate # to activate the virtual env.

deactivate # to deactivate the virtual env.

pip list # list packages in the virtual env.

pip freeze > requirements.txt # list the installed packages into requirements.txt (from the virtual env.)

pip install -r requirements.txt # install the packages from requirements.txt (into virtual env.)

After the activation of a certain environment, the packages will be installed/used/removed from there only. For better results, it is recommended to use an individual environment for each project. But, for learners, you can create virtual environments such as WebDev, DataScience, and so on.

For data science/machine learning use cases, I had been using miniconda for a while and the setup was consistent, easily reproducible, and easy to maintain. Though this can be managed simply using Python venv environment, we opt for setting up using miniconda preferably to data science application. Miniconda is a free minimal installer for conda. To get conda-related packages, we need to add -c conda-forge if not found to be installed by regular means. Here are some of the commonly used commands.

conda create -n py3k anaconda python=3 # includes optional setup here
conda env list      # shows the list of environments in the system
conda activate py3k # activates the environment
conda install numpy # installs the package in the environment
conda deactivate    # deactivates current conda environment

Check this video from Google Cloud Tech to learn about choosing a Python package manager.

C/C++

Nowadays, we can use C/C++ code in our web development projects (frontends to be specific) using WebAssembly. So, it is indeed now part of our web development setup. You can go through the steps below for a standard setup using GNU tools in Debian.

sudo apt update
sudo apt install build-essential # installs make, gcc, g++, and other packages

Build-essential contains a list of packages required to create a Debian package (.deb). Now, let's run a simple C++ code from Programiz:

// Your First C++ Program

#include <iostream>

int main() {
    std::cout << "Hello World!";
    return 0;
}

Save the file (say app.cpp) and run this in the terminal to see "Hello World". This confirms the installation of required tools to work with C/C++ in the WSL2 Linux system.

g++ hello.cpp

Golang

Standard setup:

sudo apt install golang-go

Here is the sample Go code from the official Go website:

// You can edit this code!
// Click here and start typing.
package main

import "fmt"

func main() {
    fmt.Println("Hello, 世界")
}

Now, save this file (say app.go) and run the app. To confirm if Go is installed in your system.

go run app.go

We can use the gvm Go version manager to use versioned installation which is a tool that provides an interface to manage Go versions.

bash < <(curl -s -S -L https://raw.githubusercontent.com/moovweb/gvm/master/binscripts/gvm-installer)

gvm install go1.4 # to install Go v1.4
gvm use go1.4 [--default] # to use Go v1.4

TinyGo is recommended for embedded systems and WebAssembly.

JavaScript (NodeJS)

Instead of going with an apt-based setup for NodeJS, we prefer nvm which allows using multiple nodejs versions installed and using them selectively.

wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | bash

It also should add the following lines in ~/.bashrc, ~/.profile or ~/.bash_profile, which can also be added manually if the setup does not add as below:

export NVM_DIR="$([ -z "${XDG_CONFIG_HOME-}" ] && printf %s "${HOME}/.nvm" || printf %s "${XDG_CONFIG_HOME}/nvm")"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # This loads nvm

Then, we can proceed with installing Node:

source ~/.bashrc # for bash

nvm install node # installs the latest version
nvm use node # uses the recently installed version in the terminal

nvm uninstall [version] # removes the node for update (or reinstall)

Run node -v and npm -v to confirm node and npm installation.

PHP (Apache Server)

Installing, PHP is easy using the apt.

sudo apt update
sudo apt install apache2

sudo service apache2 start

How, create a file /var/www/html/phpinfo.php and write <?php phpinfo(); ?>. Now, restart Apache and check if the PHP server is working in your Linux system. To perform the test my way, edit the file /var/www/html/index.html as below and check http://localhost:80 for verification.

<!DOCTYPE html>
<html>
    <head>
        <title> Test Document </title>
        <style>
            span {
                font-family: monospace;
                background-color: #1a78e6;
                padding: 5px;
                color: white;
                border-radius: 5px;
            };
        </style>
    </head>
    <body>
        <h1>Test content</h1>
        <p>This page comes from <span>/var/www/html/index.html</span> in WSL2.</p>
        <p>To enable, start apache service and get the IP from <span>ifconfig&gt;inet</span></p>
    </body>
</html>

Or simply check by inserting <?php phpinfo(); ?> in /var/www/html/phpinfo.php and check for http://localhost/phpinfo.php if the server is running.

References

https://dev.to/hymanzhan/setting-up-wsl-2-for-web-development-3202#python-amp-node

Web Dev setup in WSL2 Kali Linux 2022 Edition - Part 1: Connecting MariaDB and PostgreSQL database across Windows and WSL2

Yuil Tripathee — Wed, 01 Jun 2022 18:27:39 +0000

When I first began familiar with WSL 1.0 , the network interfacing was simpler. But since WSL2 uses dynamic virtual IP address for each VM, now the things has got little trickier. Here, we will learn to install Postgres and MariaDB server and client in both Windows and WSL2 Linux and access them across the virtual Ethernet connection. By the term using interchangeably we mean accessing database in Windows from WSL2 Linux and vice versa.

PROBLEM STATEMENT: WSL2 IPv4 has access to PostgreSQL from localhost in Linux but not in Windows requires virtual ethernet adaptor's assigned IP to communicate between each other and also other issue found was them requiring the firewall.

REQUIREMENTS: Database clients should be able to access database servers both in same OS and in other. WSL Client should access server in Windows and Windows clients should access database in WSL2.

To begin, one must need a good installation of Windows and WSL2 based distro in their machine.

Working with databases interchangeably

Source: https://dev.to/hymanzhan/setting-up-wsl-2-for-web-development-3202

Please be aware that you need to identify the IP address of the virtual machine (WSL) and the host machine you are working with, which might be different from the IP address of your local physical machine. You can find the IP address using Task Manager, and also using this command in WSL:

ip route # or

ip addr | grep eth0

You might also need to enable firewall on port 3306 for MariaDB and 5432 for Postgres for interconnectivity.

If you require port forwarding in WSL for reason, this article has it covered well. For Postgres vs MySQL comparison, you can check this blog from EDB, so you can choose the database system based on your need.

Database Servers

Database Servers in Windows

For Windows, you can get PostgreSQL from EDB and pgAdmin 4 from their download page. Simply install them and all add their bin directories to path folder if necessary.

For MariaDB, I recommend using XAMPP since it is robust and simple for beginners. But, if you like to install standalone version, you can download and install from official MariaDB site. You can use both MySQL Workbench and phpmyadmin to access such them as a client.

You must be able to access normally in Windows by psql and mysql commands.

Enabling/Disabling database servers in Windows is done through 'Windows Services'. It can be accessed by entering service.msc in Windows Run (Win+R).

Database Servers in Linux

PostgreSQL Server in WSL

Most of the Linux distribution already have source for installing Postgres packages.

sudo apt update
sudo apt install postgresql postgresql-client postgresql-client-common postgresql-common postgresql-contrib -y
psql --version # to confirm installation
sudo service postgresql start # replace ending by stop to stop server, restart to restart server

sudo -u postgres psql # to access Postges via command line (both in Linux)

TIP: can check the status of your services in Linux using sudo service --status-all in the shell.

This is the expected output after proper installation.

To fix connection refused issue, here's the workaround for it:

sudo -u postgres psql -c 'SHOW config_file' # to locate config file

Once you find the file, change the listen_addresses to * in postgresql.conf, the restart Postgres by sudo service postgresql restart command.

Also, update this in pg_hba.conf to allow remote auth from Windows host.

...
host  all       all       0.0.0.0/0            scram-sha-256
host  all       all       ::/0              scram-sha-256

This is a less recommended method (for security) you can try in case above methods still don't let you connect in Windows:

#newline
host    all             all             all                     trust

Here's the detail article if you like to dig deeper into this. Also, check this for better insights.

MariaDB Server in WSL

Here's the command enough to setup MariaDB server in WSL:

sudo apt install mariadb-server
sudo service mariadb start
sudo mysql # to access the database CLI

To change port, edit the configuration file /etc/mysql/my.cnf that suits your needs.

This StackOverflow thread suggests to edit the file /etc/mysql/mariadb.conf.d/50-server.cnf, replace bind-address = 127.0.0.1 (localhost) by bind-address = 0.0.0.0 or * (all). After you restart the server by $ sudo service mariadb restart, you may be able to login your Linux database server in Windows client too with proper credentials (username, password) configuration.

Database Clients

Database Clients in Windows accessing database in both Windows & WSL

We need to enable firewall for both in and out bound in Windows (for working across). To access, we need to find IP of VM in which the database server is active, the we can get along by mentioning host, port, user and password from any database client. This process if enough for the well-configured server.

Here's the sample psql command to log in for dev user, to avoid conflict:

psql -U dev -d postgres -h 192.168.176.181 -p 5432 # server host IP

In pgAdmin mention host IP address from ip route and add other credentials to access WSL based Postgres server.

To access MariaDB in Windows using XAMPP phpmyadmin, create a user in WSL MariaDB server (say wsl_user with no password) and grant ALL PRIVELEDGES. Now, you can go to login portal for phpmyadmin and find Debian in server version.

Here, mysql accesses the server in Windows in the first one, and in the second one, the server is natively installed within WSL. Therefore, both side accessed.

In phpMyAdmin, you also need to change its config.inc.php on $cfg['Servers'][$i]['auth_type'] = 'config'; to cookie to get login page.

Here's a sample showing access in Command Line (Database server is in Windows):

Database Clients in WSL accessing database in both Windows and WSL

For psql in WSL to access Windows database, you need to find host IP (using ip route for example) and then hit the command below:

psql -h [HOST ADDRESS] -U [USER NAME]

For MariaDB client access, it is simple as mysql like mysql -u wsl_root -p -h 172.24.xxx.xxx:

To make things simpler, simply create new user and access through it:

CREATE USER 'wsl_root'@'localhost' IDENTIFIED BY 'password';
GRANT ALL PRIVILEGES ON *.* TO 'wsl_root'@'localhost' WITH GRANT OPTION;
CREATE USER 'wsl_root'@'%' IDENTIFIED BY 'password';
GRANT ALL PRIVILEGES ON *.* TO 'wsl_root'@'%' WITH GRANT OPTION;
FLUSH PRIVILEGES;

You can get more details in these blogs: https://dev.to/hymanzhan/setting-up-wsl-2-for-web-development-3202 and https://dev.to/qviper/connecting-mysql-server-in-windows-machine-from-wsl-4pf1

Tips

Complete Postgres removal

Here's the solution in detail for the process:

Remove Postgres from apt (or from other installation if any):

  sudo apt-get --purge remove postgresql postgresql-*

Verify if packages are uninstalled:

  dpkg -l | grep postgres

Here's the solution in detail for the process:

Remove Postgres from apt (or from other installation if any):

  sudo apt-get --purge remove postgresql postgresql-*

Verify if packages are uninstalled:

  dpkg -l | grep postgres

Here, you must find this to be empty. If not, remove them manually.

Remove the configuration folders below:

  sudo rm -rf /var/lib/postgresql/
  sudo rm -rf /var/log/postgresql/
  sudo rm -rf /etc/postgresql/

Finally, remove postgres user:

  sudo deluser postgres

Work-around for error in `phpmyadmin`

Grant all permissions to root and pma and remove password too:

CREATE USER 'pma'@'localhost' IDENTIFIED BY '';

SET PASSWORD FOR root@localhost='';

DEV Community: Yuil Tripathee

So I tried Odoo for the first time

Prerequisites

Initial steps

Running Odoo for the first time

Check the database schema

Findings

References

Reverse engineering C code with Cflow - GNU project (to trace back calling)

Redpanda setup in Linux: Installing Redpanda in Zorin 16.3

Process

#1 Getting things ready

#2 Install and tune

#3 Enjoy

Playing with clusters

References

Docker setup in Linux: Setting up docker in Zorin 16.3

Process

#1 Install Docker system

#2 Docker Desktop

#3 Optional: Install kubernetes

References

Network interfacing issues faced using WSL 2 (and fixes)

#1 - Memory not releasing back

#2 - WSL2 network ports are virtual and cannot be accessed from LAN

Web Dev setup in WSL2 Kali Linux 2022 Edition - Part 2: Coding Tools setup - Python, C++, Go, JS, PHP

Code Editor (Visual Studio Code)

Python

Python virtual environments

C/C++

Golang

JavaScript (NodeJS)

PHP (Apache Server)

References

Web Dev setup in WSL2 Kali Linux 2022 Edition - Part 1: Connecting MariaDB and PostgreSQL database across Windows and WSL2

Working with databases interchangeably

Database Servers

Database Servers in Windows

Database Servers in Linux

PostgreSQL Server in WSL

MariaDB Server in WSL

Database Clients

Database Clients in Windows accessing database in both Windows & WSL

Database Clients in WSL accessing database in both Windows and WSL

Tips

Complete Postgres removal

Work-around for error in phpmyadmin

References

Work-around for error in `phpmyadmin`