Fueling Curiosity, One Insight at a Time

while doing npm install or yarn install we might run into this error mentioned below:

error /Users//project/node_modules/sharp: Command failed.
Exit code: 127
Command: (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)

to fix this just do npm rebuild & then run npm install or yarn install .
#sharp-error #npm #node

git stash want to store commit temporarily then , stashing will save your modifications and revert your working directory to its clean state

SAP is divided into two types of data:
• Master Data - Consists product data , person data (eg: vendor, customer) or place data.
• Transaction Data - Consists of quotation , sales order , good issue, good receipt , invoice.
#SAP

Docker Hub & Pushing Docker Images
• Why We Need Docker Hub: Docker Hub is like a social media platform, but instead of sharing photos or updates, we share Docker images. Docker Hub provides a centralized place for storing and managing these images. We use Docker Hub to:
◦ Share our Docker images with others.
◦ Store different versions of our Docker images.
◦ Access our Docker images from any machine, making deployment and scaling much easier.
◦ Find and use Docker images created by others, which can be very helpful.
• How to Push a Docker Image to Docker Hub: To push a Docker image, we follow a few simple steps:
a. Log In: Just like logging into your favorite app, we log in to Docker Hub on our computer.
b. Tagging: We give our image a label (or a tag) that describes what it is and which version it is—kind of like tagging a friend in a photo docker tag flix-rails:latest nishanthmathiyazhagan/flix-rails:latest
c. Pushing: With our image tagged, we ‘push’ it to Docker Hub, which means uploading it so others can download and use it.
docker push nishanthmathiyazhagan/flix-rails:latest
• What Happens After Pushing the Image to Docker Hub: Once the image is pushed:
◦ It’s stored in our Docker Hub repository,
◦ Other people can ‘pull’ the image to their own computers or servers to run the application it contains.
◦ If we update the application, we can push the new version to Docker Hub so everyone can get the update.
◦ We can pull it down on any server
#devops #docker

Sidekiq Capsule allows to configure queues to execute jobs serially.
Before Sidekiq version 7, to manage dependencies between jobs, a delay was often manually set with set(wait: 30.seconds) to ensure the sequential execution of dependent jobs. This can be achieved now by setting their concurrency to 1.

Sidekiq.configure_server do |config|
  config.capsule("capsule") do |cap|
    cap.concurrency = 1
    cap.queues = %w[capsule-queue]
  end
end

#rails #sidekiq

Use pluck to fetch only the necessary columns if you don't need the entire object
This reduces memory usage and database load

For example

 adults = User::User.where("age > ?", "18").pluck(:name)

The above code will return an array of name of users who are above age of 18

#rails #db

ps aux | grep defunct displays information about any zombie processes (that have completed execution but still have an entry in the process table with specific PID because, their parent process has not yet collected their exit status) currently running on the system.
#devops

When eslint is not working on your repository in local for any reason you can try restarting the ES Lint Server on VS Code, and if the issue is cause cause server is not reading the config from root directory you can set root: true in your eslint config file, that should resolve the issue. And to fix all your lint issue in a single commit you can use command npx eslint . --fix.

#javascript #eslint

Rails db:prepare command follows these steps:
1. It first attempts to run db:migrate to apply any pending migrations. This step ensures that the database schema is up to date with the latest changes defined in your migration files.
2. If the database does not exist, it falls back to db:setup to create the database, load the schema, and seed it with initial data. This step is crucial for setting up a new database or ensuring that an existing database is correctly initialized.
In summary, rails db:prepare is a powerful command for ensuring your database is ready for use in your Rails application
#rails

The rails plugin command simplifies plugin management. Plugins can be installed by name or their repository URLs. You need to have Git installed if you want to install a plugin from a Git repo.
$ rails plugin install https://github.com/countries/countries.git
#rails #gem