I'am sane!

Is it important to make docker compose down before docker compose up -d and docker restart

noreply@blogger.com (Adv User) — Thu, 1 Oct 2026 03:37:39 +0300

Is it important to make docker compose down before docker compose up -d and docker restart

Generally, NO, it is not necessary or even recommended to run docker compose down before docker compose up -d.

docker compose up is designed to be declarative and intelligent; it compares your current running state with your docker-compose.yml file and only makes the changes necessary to match them.

Why You Usually Don't Need down

• Automatic Updates: If you change a configuration (like environment variables or port mappings) and run up -d again, Docker will automatically stop and recreate only the containers that were affected.

• Less Downtime: Using up alone is significantly faster and results in less downtime because it doesn't stop or remove containers that don't need changes.

• Resource Preservation: docker compose down removes networks and containers entirely. Re-running up forces everything to be rebuilt and reconnected from scratch.

When You Should Use down

• Full Reset: If you want a completely clean slate, including removing internal networks and "anonymous" volumes.

• Removing Orphans: If you removed a service from your .yml file, down will ensure its old container is deleted (though you can also use docker compose up -d --remove-orphans).

• Database Re-initialization: If you need to wipe out local data stored in non-persistent volumes to force a fresh setup.

Pro Tips for up -d

• Forcing a Rebuild: If you updated your code/Dockerfile but didn't change the .yml, use docker compose up -d --build to force a new image creation.

Forcing Recreations: Use docker compose up -d --force-recreate to restart everything even if no configurations have changed.

No. docker compose restart is not the same as running docker compose down followed by docker compose up -d.

Core Differences

The two commands operate completely differently regarding configuration updates, container lifecycle, and network resources:

Feature	docker compose restart	docker compose down && docker compose up -d
How it Works	Stops and starts the existing container process.	Destroys the container and builds a new one.
Picks up compose.yml changes?	No. Changes to environment variables, ports, or volumes are ignored.	Yes. Re-reads the file and applies all changes.
Resets Filesystem?	No. Ephemeral container data is preserved since it is the same container.	Yes. Destroys the filesystem; resets to the base image state (except mounted volumes).
Destroys Networks?	No. Keeps the internal Docker network intact.	Yes. Removes the network entirely and recreates it.
Builds new Dockerfile code?	No. Restarts using the exact same image currently in use.	No. Unless you pass the --build flag to up.

Deep Dive into Each Command

1. docker compose restart

Use this for a quick process bounce when you do not need to change how the container is built.
It simply stops the running processes inside the container and immediately starts them up again.
It saves time because it skips container creation and network configuration.

2. docker compose down && docker compose up -d

Use this for a complete infrastructure reset.
It completely removes the containers, networks, and internal Docker caches.
It rebuilds everything fresh based on the current state of your compose.yml file.

The Recommended Alternative: docker compose up -d

If you made changes to your compose.yml or your underlying image and want to restart to apply them, you do not need to run down.

Instead, simply run:

docker compose up -d

Docker Compose will automatically compare your current configuration against the running containers.
It will only recreate containers that have changed, while leaving untouched services running uninterrupted.
To force recreate the container even if the configuration did not change, use: docker compose up -d --force-recreate.

Right reset branch (clean history commits after some specific commit)

noreply@blogger.com (Adv User) — Thu, 27 Aug 2026 21:01:13 +0300

git reset --hard <SHA1>

git push origin <branch-name> --force-with-lease

or just git push --force-with-lease

--force-with-lease --> don't let us overwrite somebody's else dev's commits

How to recover all files in folder from specific branch

noreply@blogger.com (Adv User) — Tue, 21 Jul 2026 17:27:41 +0300

How to recover all files in folder from specific branch

To recover all files in a folder from a specific branch to your current working tree, use the git checkout or git restore command, specifying the branch name and the path to the folder.

Run this command from your terminal:

git checkout <branch-name> -- <folder-path>

For a safer, modern alternative (available in Git 2.23+), you can use Git Restore Documentation:

git restore --source=<branch-name> --staged --worktree -- <folder-path>

How It Works

<branch-name>: The name of the branch containing the files you want to recover.

<folder-path>: The relative path to the folder (e.g., src/components/).

The double dash (--): Tells Git to treat everything after it as a file or directory path, rather than a branch name.

Once the command is run, the files will be placed into your working directory, staged, and ready to be committed

How to compare 2 commits in git

noreply@blogger.com (Adv User) — Sat, 11 Jul 2026 10:04:56 +0300

How to compare 2 commits in git

To compare two commits in Git, you use the git diff command followed by the commit identifiers.

Compare via Command Line

Detailed code changes: Run git diff <commit1> <commit2> to see line-by-line differences between two commits.
High-level summary: Run git diff --stat <commit1> <commit2> to view a list of changed files and line counts.
Single file comparison: Run git diff <commit1> <commit2> -- <path/to/file> to restrict the comparison to one specific file.

Note: You can use full commit hashes, short 7-character hashes, or reference pointers like HEAD and HEAD~1.

Understanding Comparison Types

Notation Syntax	Comparison Logic	Best Used For
`git diff commit1 commit2`	Compares the exact states of the two snapshots directly.	Comparing arbitrary points in history.
`git diff commit1..commit2`	Identical to using a space; compares the tips of both commits directly.	Standard branch-to-branch or commit comparisons.
`git diff commit1...commit2`	Compares the common ancestor of both commits with `commit2`.	Seeing only changes introduced by a feature branch, ignoring target updates.

How to list only commits which was made after branch was splitted(checkouted)

noreply@blogger.com (Adv User) — Sat, 11 Jul 2026 10:02:50 +0300

To list only the commits made on your current branch after it split from a parent branch, use the double-dot (..) syntax with git log.

💻 The Best Commands

Run this command from your current branch:

git log main..HEAD

If you prefer a clean, single-line overview:

git log --oneline main..HEAD

(Note: Replace main with master, develop, or whatever the name of your parent branch is.)

🔍 How It Works

The .. operator acts as a set subtraction tool.

main..HEAD means: "Show me all commits reachable from HEAD (your current branch), but exclude any commits that are reachable from main."
This leaves you exactly with the new commits added to your feature branch since the day you used git checkout -b.

💡 Advanced Options

Depending on your workflow, you can add flags to handle specific scenarios:

Exclude Merge Commits: If you have pulled or merged other branches into your feature branch and only want to see your unique work, add --no-merges:
git log main..HEAD --no-merges
Automatic Parent Tracking: If you don't want to type out the parent branch name every time, you can instruct Git to find the merge base automatically:
git log $(git merge-base main HEAD)..HEAD

If you want to view these changes in a visual graph to verify where the split happened, I can show you how to configure a graph view alias. Would you like to see that?

Disk usage analysis in linux

noreply@blogger.com (Adv User) — Wed, 8 Jul 2026 18:08:12 +0300

Disk usage analysis in linux

Most common approach if you have access to install something is ncdu command

sudo apt update && sudo apt install ncdu -y

Подробнее ...

EchoAPI vs Postman

noreply@blogger.com (Adv User) — Tue, 7 Jul 2026 07:04:07 +0300

Whether EchoAPI is better than Postman depends entirely on your development needs: EchoAPI is significantly better if you want a lightweight, login-free, offline-first tool that embeds right into your code editor. However, Postman remains the superior option for massive enterprises that require deep multi-protocol support and complex, cloud-hosted team workspace permissions.

Core Differences at a Glance

Feature	EchoAPI	Postman
System Weight	Ultra-lightweight; fast startup	Bulky; heavy resource consumer
Account Req.	No mandatory login; works out of the box	Mandatory login for cloud/collections
Offline Mode	100% functional offline (Local storage)	Highly restricted / Cloud-dependent
Editor Integration	Native extensions for VS Code and IntelliJ	Separate native desktop application
Script Compatibility	100% Postman script syntax compatible	Native/Standard syntax
Pricing	Highly generous free tier / completely free plugins	Restrictive free limits (e.g., runner limits)

Why EchoAPI is Better

Zero Bloat & Better Speed: Reviewers notes that EchoAPI runs smoothly inside your IDE (like VS Code), avoiding the slow startup times and lagging UI often associated with Postman.
No Forced Login: You can test, save local collections, and design APIs immediately without creating an account or storing sensitive endpoint data on a public cloud.
Flawless Postman Migration: It features 100% compatibility with Postman's scripting syntax. You can import your existing Postman collections directly into EchoAPI, and pre-request scripts or test assertions will run perfectly without rewritten code. [
Scriptless Testing & Smart UI: For standard cases, it offers visual, GUI-based parameter extraction and assertion tools, eliminating the need to manually write JavaScript code for simple tests.

Why Postman is Better

Enterprise Ecosystem: Postman has been the market leader for years. Its mature ecosystem offers incredibly deep documentation, complex enterprise governance controls, and vast public API networks.
Advanced Multi-Protocol Testing: While EchoAPI handles standard REST, WebSockets, and GraphQL well, Postman features deeper edge-case tooling for complex gRPC streams, SOAP infrastructure, and intricate multi-step automated testing webhooks.

The Verdict

If you are an individual developer or work in a mid-sized team using VS Code, EchoAPI provides a faster, cleaner, and less restrictive environment. If you are tied to a massive organization that relies heavily on Postman's cloud workspaces, staying with Postman is necessary

Google Charts API - Gauge Chart Example

noreply@blogger.com (Adv User) — Sun, 26 Apr 2026 22:09:41 +0300

Google Charts API - Gauge Chart Example

https://developers.google.com/chart/interactive/docs/gallery/gauge#overview

Preparing your local Postges DB. Resolving timezone headache for developers.

noreply@blogger.com (Adv User) — Fri, 17 Apr 2026 06:12:00 +0300

Preparing your local Postges DB

Resolving timezone headache for developers.

To set your PostgreSQL server time to UTC, you can change the setting globally, per database, per user, or for a single session.

Permanent Global Change

Modify the main configuration file to set the default for the entire server.

Locate the file: Find your postgresql.conf file by running this SQL command in your database:
```
SHOW config_file;
```
Edit the file: Open postgresql.conf and find the timezone parameter. Change it to:
text
```
timezone = 'UTC'
```
Use code with caution.
Apply changes: Reload the configuration without restarting the server by running:
```
SELECT pg_reload_conf();
```
(Alternatively, use pg_ctl reload from your terminal).

Permanent Database or User Change

If you only want specific databases or users to use UTC, use these SQL commands:

Per Database:

ALTERDATABASE your_database_name SET timezone TO'UTC';

Per User:

ALTER USER your_username SET timezone TO'UTC';

Note: Users will need to reconnect for these changes to take effect.

Temporary Session Change

To change the time zone for only your current connection, run:

SET TIMEZONE 'UTC';

This is useful for testing but will reset once you disconnect.

Verification

To confirm your current settings, use these commands:

Check current time zone: SHOW timezone;
Check current server time: SELECT now();.

Tip: PostgreSQL internally stores TIMESTAMP WITH TIME ZONE (timestamptz) data in UTC regardless of your server's display settings. Changing the server time zone primarily affects how these timestamps are displayed to you and how "timezone-naive" timestamps are interpreted.

Axios returned 403 when i requesting resource which has proper CORS setup - why? (my case)

noreply@blogger.com (Adv User) — Fri, 3 Apr 2026 06:00:00 +0300

Axios returned 403 when i requesting resource which has proper CORS setup - why? (my case)

I fell for that trap🤯 - if you too, look into your infrastructure for CloudFlare DNS Proxy and rules inside Cloudflare which is blocking you and your Axios returned you 403 because it sees access denied from Cloudflare, not from your company resource you are trying to make request to and which is properly available for you by CORS (permissions). Happy coding, guys! 🤗

15 поширених команд Linux (repost з ITEDU.center)

noreply@blogger.com (Adv User) — Sat, 28 Mar 2026 19:42:00 +0200

У цій статті зібрали 15 поширених команд, які варто знати кожному сисадміну. Це не повний список можливостей Linux, але вони допоможуть моніторити систему, знаходити помилки й автоматизувати рутину.

htop — зручний перегляд процесів у реальному часі

Це вдосконалений варіант команди top, але з інтуїтивним інтерфейсом і можливістю управляти процесами безпосередньо. htop показує:

навантаження на CPU та RAM у вигляді графіків;
повну структуру процесів у вигляді дерева;
можливість завершити процес без введення PID.

lsof — перевірка відкритих файлів і портів

lsof (List Open Files) дозволяє дізнатися, які процеси використовують конкретні файли або порти. Корисно, якщо порт уже зайнятий, і сервіс не стартує.

lsof -i :80

Це допоможе зʼясувати, що саме використовує порт 80 — зазвичай вебсервер або інша мережева служба.

journalctl — перегляд логів у системах із systemd

Для Ubuntu 18.04+, CentOS 7+ та інших дистрибутивів із systemd ця команда — мастхев. Вона дозволяє:

читати системні журнали;
шукати помилки;
фільтрувати логи за сервісами.

journalctl -xe # перегляд останніх повідомлень і помилок

journalctl -u nginx # перегляд логів конкретного сервісу nginx

systemctl — керування службами

Це основна команда для взаємодії з systemd. За допомогою systemctl ти можеш

запускати та зупиняти сервіси;
вмикати автозапуск;
перевіряти статус служб.

systemctl status sshd

systemctl restart apache2

systemctl enable nginx

du — аналіз використання диска

du (disk usage) дозволяє побачити, які каталоги займають найбільше місця.

du -sh /var/*

Зручно, коли потрібно зʼясувати, чому диск майже заповнений.

df — перевірка вільного місця

Показує, скільки вільного простору залишилось на розділах. З прапорцем -h (human-readable) результат виводиться у зручному вигляді: мегабайти, гігабайти, замість байтів.

df -h

Цю команду найчастіше використовують, коли програми падають через нестачу місця.

free — моніторинг оперативної памʼяті

Ця команда покаже, скільки оперативки та swap розділу використовується.

free -h # вивід доступної та зайнятої памʼяті

Зручно для базової діагностики, якщо система почала гальмувати.

uptime — навантаження на систему

Показує аптайм системи, кількість активних користувачів і середнє навантаження за останні 1, 5 та 15 хвилин.

uptime # коротка зведена інформація про роботу системи

top — базовий моніторинг процесів

Менш зручна за htop: складніша навігація, але встановлена майже в кожному дистрибутиві.

top # перегляд процесів у реальному часі

ps aux — знімок усіх процесів

Команда показує всі запущені процеси в системі. Можна поєднувати з grep, щоб шукати конкретні сервіси:

ps aux | grep apache

ps aux –sort=-%mem | head

ss — перевірка мережевих зʼєднань

Сучасна альтернатива netstat. Вона швидша, детальніша і вже включена в більшість дистрибутивів.

ss -tuln # показує активні TCP/UDP-порти та процеси, що їх слухають

Показує, які порти відкриті, які служби їх використовують і які зовнішні зʼєднання активні.

ip — конфігурація мережі

Це сучасна утиліта для роботи з мережевими інтерфейсами, маршрутами й адресацією. Вона прийшла на заміну застарілому ifconfig і дає більше контролю.

За допомогою команди можна:

переглядати конфігурацію мережевих інтерфейсів (`ip a`);
керувати маршрутами (`ip r`);
призначати IP-адреси або змінювати їх вручну.

ping — перевірка доступності

Найпростіший спосіб перевірити, чи хост доступний у мережі. ping надсилає запити ICMP й чекає на відповідь

ping google.com

ping -c 4 192.168.0.1

traceroute — діагностика маршрутів

Допомагає зʼясувати, на якому етапі виникає проблема з мережею або де затримуються пакети.

traceroute google.com # відображення маршруту пакетів до хоста

nc — перевірка портів

Дозволяє перевірити, чи відкритий порт 22 (SSH) на віддаленому хості та чи відповідає служба. Корисно для діагностики SSH, вебсерверів, баз даних тощо.

nc -zv 192.168.1.10 22

Як дізнатися в якому шелі ті працюєш зараз

echo $0 ps -p $$: The $$ parameter holds the Process ID (PID) of the current shell.
echo $SHELL readlink /proc/$$/exe: (On Linux systems that support the /proc filesystem) This command will display the actual executable file that is running your current shell session, resolving any symbolic links

Git - merge investigation commands

noreply@blogger.com (Adv User) — Mon, 9 Mar 2026 17:35:00 +0200

1. How to find out if branch has been merged into your current branch

2. How to find out if your current branch has been merged into any other branch

3. Edge case with cherry 🍒 (pick)

1. Check if a feature or branch has been merged into your current branch, use the git branch --merged command, the git merge-base command, or inspect the git log.

Methods to Verify a Merge:

1. Using git branch --merged

This command lists all branches whose tips are reachable from your current branch's HEAD, meaning they are fully integrated.

First, ensure you are on the branch where you expect the feature to be merged (e.g., main):

git checkout <current-branch-name>

Then, run the command to list all merged branches:

git branch --merged

If the feature branch name appears in the output list, it has been merged into your current branch.

To see branches that have not been merged, you can use the --no-merged flag instead:

git branch --no-merged

2. Using git merge-base

This method determines the common ancestor between two branches. If the common ancestor is the same as the feature branch's tip, then the feature branch is fully merged.

Find the last commit hash of the feature branch:

git rev-parse <feature-branch-name>

Find the best common ancestor between your current branch and the feature branch:

git merge-base <current-branch-name> <feature-branch-name>

If the output of both commands is the same commit hash, the feature branch is merged.

To check if one branch is an ancestor of another: You can use the --is-ancestor flag, which returns an exit status of 0 if true, and 1 otherwise (useful for scripting):

if git merge-base --is-ancestor <ancestor-branch> <descendant-branch>; then
echo "<ancestor-branch> is an ancestor of <descendant-branch>"
fi

3. Using git log

You can visually inspect the commit history for the commits from the feature branch within your current branch's history.

Switch to your current branch:

git checkout <current-branch-name>

Check the log for commits from the feature branch:

git log <feature-branch-name>

If the commits from the feature branch are visible in the log, they are part of the current branch's history. For a more visual representation, you can use:

git log --decorate --oneline --graph --all

This shows a graphical history, making it easier to spot the merge commit.

4. Using a Git Hosting Service (GitHub, GitLab, etc.)

Check the status of the pull request (PR) or merge request (MR) associated with the feature branch on your web-based Git platform (e.g., GitHub, GitLab). The status will typically indicate whether the PR/MR has been successfully merged.

Подробнее ...

How to forget to run php ./vendor/bin/drush cr for ever

noreply@blogger.com (Adv User) — Thu, 12 Feb 2026 23:57:00 +0200

How to forget to run php ./vendor/bin/drush cr for ever

Yes, it is possible to automatically run php ./vendor/bin/drush cr on file save, typically by using file-watching tools like nodemon, entr, or IDE-specific plugins (e.g., VS Code "Run on Save"). These tools detect file changes in your Drupal directory and execute the drush command to clear the cache.

Using nodemon (Node.js):
Install nodemon and run:
nodemon --watch web/modules --watch web/themes --ext php,yml,twig --exec "php ./vendor/bin/drush cr"
Using entr (Unix tool):
find . -name "*.php" -o -name "*.yml" -o -name "*.twig" | entr -p php ./vendor/bin/drush cr
IDE Extension (VS Code):
Install an extension like "Run on Save" and configure it to trigger php ./vendor/bin/drush cr when PHP, YML, or TWIG files are saved.

Performance: Automatically clearing cache on every save can slow down development, especially with large projects.
Pathing: Ensure you are running the command from the project root or adjust the path to vendor/bin/drush accordingly.
PHP Version: If required, specify the PHP version explicitly if your server environment requires a specific version (e.g., php83 ./vendor/bin/drush cr).

Tmux - work cases and tune up

noreply@blogger.com (Adv User) — Fri, 6 Feb 2026 17:52:00 +0200

Tmux - work cases and tune-up

how to scroll rows in tmux terminal splited windows
how to save sessions, layout, dirs and even progs state in tmux
how to change horizontal split to vertical split in tmux
how to add horizontal and vertical splits in tmux + key bindings
how to exit tmux but leave session working
how to attach session to tmux
how to know how many sessions you have
how to kill sessions
how to swith-between sessions
how to rename sessions and panes (panes are small part of the window - splatted in tmux)
How to reload tmux configuration from tmux
How to enable clocks

BONUS: visual cheat-sheet

almost all settings are made in mine .tmux.conf you can download from my gist put this file into your home directory after you install tmux on your system

For those who don't aware what is it - this is terminal shell and you can install it for your distro like sudo apt-get install tmux (for Debian like Ubuntu etc.)

1. How to scroll rows in tmux terminal spitted windows

To scroll rows within a specific tmux split window (pane), you must first enter copy mode. This allows you to navigate and review the pane's scrollback buffer.

Scrolling with Keyboard

Enter copy mode: Press your tmux prefix (default is Ctrl+b), then immediately press the [ key. An indicator in the top right of the pane will show the current line number.
Scroll:
- Use the arrow keys (↑ and ↓) to move one line at a time.
- Use Page Up and Page Down (or Shift+Page Up/Shift+Page Down in some terminal emulators) to jump an entire page.
Exit copy mode: Press the q key or Esc to return to normal mode.

Scrolling with Mouse

For those who prefer using the mouse wheel, you need to enable mouse mode in your ~/.tmux.conf configuration file.

Edit your ~/.tmux.conf file with an editor like nano or vim.
Add the following line (for tmux versions 2.1 and up):
set -g mouse on
For older versions, use set -g mode-mouse on.
Reload your tmux configuration using the command line within a tmux session:
- Press the prefix Ctrl+b.
- Type : to enter the tmux command prompt.
- Type source-file ~/.tmux.conf and press Enter.
Scroll: You should now be able to use your mouse scroll wheel directly within any pane, even in split windows. This also enables clicking to select panes and resize them with the mouse.

--------------------------------------

2 . To save a `tmux` layout,

the recommended method is to use the tmux-resurrect plugin, as tmux does not have a built-in feature for saving sessions to a file by default.

Using the tmux-resurrect Plugin

The tmux-resurrect plugin saves all session details, including window and pane layouts, current working directories, and even running programs, to a file that can be restored later.

1. Installation (using Tmux Plugin Manager - TPM)

Install TPM first if you don't have it. Instructions can be found on the TPM GitHub page.

Add the tmux-resurrect plugin to your ~/.tmux.conf file:

set -g @plugin 'tmux-plugins/tmux-resurrect'

Run the plugin manager by pressing prefix + I (capital I, where prefix is Ctrl + b by default) inside a tmux session to fetch and source the plugin.

2. Saving the Layout

To manually save your current tmux environment, press prefix + Ctrl + s.

A notification message 'tmuxenvironmentsaved' will briefly appear in the status bar.

3. Restoring the Layout

To restore the last saved environment, press prefix + Ctrl + r.

The saved sessions, windows, and pane layouts will be restored.

Alternative Methods

Automatic Saving/Restoring: For continuous, automatic saving (e.g., every 15 minutes) and automatic restoration on startup, you can use the complementary tmux-continuum plugin alongside tmux-resurrect.

Add set -g @plugin 'tmux-plugins/tmux-continuum' to your ~/.tmux.conf

and press prefix + I to install it.

Scripting: You can also write a custom bash script that uses tmux commands to recreate a specific, predefined layout.

The list-windows command can display layout data that you can use in your scripts.

Tmuxinator/Tmuxp: For project-specific layouts defined in YAML files, tools like Tmuxinator or Tmuxp can be used to launch predefined workspaces with a single command.

--------------------------------------------------------------

3. how to change horizontal split to vertical split in tmux

You can change an existing horizontal split to a vertical split in tmux by cycling through the preset layouts with a keyboard shortcut or by using the select-layout command. There is no direct command to "transpose" an existing single horizontal split to a single vertical one while keeping the same panes.

Method 1: Cycle through preset layouts

The quickest method is to use the default keybinding to cycle through the available window layouts. This will rearrange your panes into one of the predefined configurations, including even-horizontal and even-vertical.

Press your prefix key (by default, Ctrl + b).
Press the spacebar (Space).

Repeat this until you reach the desired vertical layout.

Method 2: Use a specific preset layout command

If you want to apply a specific layout immediately, you can use a command or a keybinding that targets a particular preset. The default bindings for these are often mapped to Alt (or Meta) keys combined with numbers.

Press your prefix key (Ctrl + B), release, and then press Alt + 2 to arrange panes in an even-vertical layout.
Alternatively, you can access the tmux command prompt:
1. Press your prefix key (Ctrl + b).
2. Press the colon key (:).
3. Type select-layout even-vertical and press Enter or select-layout even-horizontal .

Method 3: Move a pane to create a vertical split (for specific cases)

If you have a complex layout and want more control over which pane goes where, you can move specific panes. This is more involved and generally requires using the command line within tmux.

Identify pane numbers: Press your prefix + Q to briefly display pane numbers.
Use swap-pane: For example, to swap the current pane's position with an "up" or "down" pane in the index order, press your prefix + b followed by { or }.

For a full explanation of advanced options, including how to configure custom key bindings in your ~/.tmux.conf file, you can consult the tmux man page.

--------------------------------------

4. how to add horizontal and vertical splits in tmux + key bindings

Tmux Split Pane Keybindings

Vertical Split (Side-by-Side): Press prefix then %.
Horizontal Split (Top/Bottom): Press prefix then ".
Close Current Pane: Press prefix then x.
Switch Between Panes: Press prefix then arrow keys.
Toggle Layouts: Press prefix then Space to cycle through layout arrangements.

Command Line Alternatives

You can also run these commands directly in your terminal or via the tmux command prompt (prefix followed by :):

Vertical: tmux split-window -v.
Horizontal: tmux split-window -h.

Customizing Key bindings

To make splits more intuitive (e.g., using | for vertical and - for horizontal), add these to your ~/.tmux.conf file:

creating new windows:

bind | split-window -h

bind - split-window -v

changing the layout (evenly - all windows will be in the same size!):

bind H select-layout even-horizontal

bind V select-layout even-vertical


accidentally i found similar article on LinkedIn

accidentally i found similar article on LinkedIn link

`5. How to exit tmux but leave session working`

 Press prefix then d

`6. How to attach session to tmux`

 in console type tmux attachif you have only one session or
tmux attach -t <session_number/session_name>

`7. How to know how many sessions you have`

 type in console tmux list-sessions or tmux ls

8. How to kill sessions

Press your prefixkey, then type :kill-session and press Enter.
Alternatively, you can press the prefix key followed by & This prompts for confirmation to close the current window, which in turn kills the session if it's the last window.

Kill a specific session (by name/number) from your current session:

Press your prefix key, then type : This opens the tmux command prompt.
Type kill-session -t <session-name> and press Enter.
First, you may want to list sessions to find the exact name/number using the command :list-sessions or the shortcut Prefix + s.

Kill all other sessions except the current one:

Press your prefix key, then type :
Type kill-session -a and press Enter

Pressing prefix +& prompts for confirmation then kills (closes) the current window. All panes in the window are killed at the same time.

prefix + xkills only the active pane. These are bound to the kill-window and kill-pane commands.

9. How to switch between sessions

Navigate between sessions using keybindings:

Press Prefix + s to open an interactive menu showing all sessions, windows, and panes. Use arrow keys to navigate and press Enter to switch.
Press Prefix + ( to switch to the previous session.
Press Prefix + ) to switch to the next session.
Press Prefix + L (capital L) to switch to the last used session, functioning like an "alt-tab" for sessions.

Switch to a specific session by name:

Press your prefix key, then type :
Type switch-client -t <session-name> and press Enter

10. How to rename sessions and panes (panes are small part of the window - splatted in tmux)

Naming Sessions and Panes

1. Use these commands or shortcuts to provide descriptive names:

Rename a Session:
- Shortcut: Press Prefix + $.
- Command: Use tmux rename-session -t current_name new_name from the shell.
Rename a Pane:
- Command: Enter Prefix + : then type select-pane -T "your_pane_name".
- Enable Display: To actually see these names, you must enable pane borders in your ~/.tmux.conf:
  set -g pane-border-status top set -g pane-border-format " [ #P #T ] "
  Use code with caution.
- Note: Some shells or programs may overwrite these titles automatically.

2. Switching Interactively

The most efficient way to switch between named items is through the built-in tree view:

Interactive Tree View: Press prefix + w.
- This opens a navigable list of all sessions, windows, and panes.
- Use Arrow Keys or j / k to move through the list.
- Press Enter to jump to the selected pane.
Display Pane Numbers: Press prefix + q. Large numbers will appear briefly over each pane; type the corresponding number to jump to it instantly.

3. Switching by Name

Sessions: Use prefix + s to show an interactive session-only list, or use tmux switch-client -t session_name from the command prompt.
Windows: Use prefix + f to search for a window by its name.

11. How to reload tmux configuration from tmux

1. From within a tmux session

Enter command mode: Press the prefix keys;
Type the command: Press : (colon) to bring up the command prompt at the bottom of the screen;
Execute the source command: Type source-file ~/.tmux.conf (or source ~/.tmux.conf in most modern versions) and press Enter.

2. From your shell/terminal (outside of tmux)

Run the following command in your terminal prompt:

tmux source-file ~/.tmux.conf

12. How to enable Digital Clocks in the tmux
    Press Ctrl + B (Prefix key combo) keys and t

Additional useful key bindings (add them in .tmux.conf):

Quick-Toggle Pane Titles:

bind b set-option -g pane-border-status

Renaming pane without typing command in command line:
bind-key T command-prompt -p "Pane Title:" "select-pane -T '%%'"

To reload ~/.tmux.conf file quickly
bind r source-file ~/.tmux.conf \; display "Config reloaded!"

Adding not root user to Docker container

noreply@blogger.com (Adv User) — Thu, 5 Feb 2026 22:45:00 +0200

Adding not root user to Docker container

in docker file:

ARG USERNAME=containeruser

ARG USER_UID=1000

ARG USER_GID=$USER_UID

RUN groupadd --gid $USER_GID $USERNAME \

&& useradd --uid $USER_UID --gid $USER_GID -m $USERNAME \

&& chown -R $USER_UID:$USER_GID /home/$USERNAME

# [Optional] Add sudo support if needed

# && apt-get update && apt-get install -y sudo \

# && echo $USERNAME ALL=(root) NOPASSWD:ALL > /etc/sudoers.d/$USERNAME \

# && chmod 0440 /etc/sudoers.d/$USERNAME

# Set the default user for all processes in the container (optional, but ensures everything runs as this user)

# USER $USERNAME

Visual representation - Timeline of a React Component With Hooks (link)

noreply@blogger.com (Adv User) — Mon, 19 Jan 2026 08:14:00 +0200

Visual representation - Timeline of a React Component With Hooks (link)

Timeline of a React Component With Hooks

30 маловідомих, але корисних команд Linux (repost)

noreply@blogger.com (Adv User) — Fri, 16 Jan 2026 05:07:00 +0200

30 маловідомих, але корисних команд Linux

Саме тому ми зібрали 31 команд, які не згадуються в кожному гайді, зате дійсно виручають. Особливо, коли часу обмаль, а результат потрібен вже.

lsd - те саме що ls але краще
lsd -l --permission octal --> тільки для нових версій lsd > 1.1.0

Базові трюки з терміналом

Тут зібрали ті маленькі команди, які часто рятують нерви. Повторити, очистити, знайти чи навіть написати.

Повтор останньої команди

Забув додати sudo та отримали «Permission denied»? Не переписуй всю команду заново — просто використай:

sudo !!

Очищення екрана

Коли термінал заповнений виводом і хочеться почати з чистого аркуша, натисни Ctrl+L, щоб миттєво очистити екран.

Редагування поточної команди в редакторі

Якщо команда занадто довга або складна, натисни Ctrl+x + e, щоб відкрити її в текстовому редакторі для зручного редагування.

Коротка довідка по команді

Замість читання довгих man-сторінок, юзай tldr для отримання коротких прикладів використання команди:

Автоматичне оновлення виводу команди

Хочеш спостерігати за змінами в системі у реальному часі? Ця команда дозволить періодично виконувати іншу команду і показувати її вивід:

watch -n 1 'df -h'

Нескінченне повторення тексту

Просто виконай:

yes "I agree"

Моніторинг системи та діагностика

Коли щось не так із системою — важливо мати під рукою прості інструменти перевірки. Тому замість нудних копань у логах тримай ці команди.

Версія твого дистрибутива

Щоб знайти таку інформацію, достатньо ввести таку команду:

lsb_release -a

Перегляд деталей файлу

Хочеш дізнатись, коли файл востаннє змінювали, який у нього розмір і права доступу? Просто звернись до stat file.txt.

Перегляд дерева процесів

Команда pstree відображає всі запущені процеси у вигляді дерева, що допомагає зрозуміти їх ієрархію.

Перевірка відкритих портів

Щоб швидко глянути, які порти відкриті і які з’єднання активні, використовуй ss -tuln. Мінімалістично й інформативно.

Історія входів у систему

Забагато підозрілої активності? last покаже історію входів користувачів і трохи заспокоїть (або навпаки).

Командний центр продуктивності

Команда dstat показує навантаження на CPU, диски, мережу. Ідеально, коли треба зрозуміти, чому сервер тупить.

Виведення усіх доступних змінних середовища

Застосуй команду printenv, коли потрібно розібратись, які змінні зараз активні.

Робота з файлами та текстом

Ці команди допоможуть краще тримати файли та текст під контролем і працювати з ними швидко та красиво.

Номери рядків у файлі

Додай номери рядкам до вмісту файлу цією командою:

nl file.txt

Форматування виводу у вигляді таблиці

Комбінація cat і column дозволяє красиво це зробити:

cat file.txt | column -t

Запис виводу у файлі

Хочеш бачити результат у терміналі і мати його під рукою в файлі? tee — твій друг:

echo "This is a test message." | tee file.txt

Кількість рядків у .txt файлах

Краще випити кави, ніж рахувати кожен рядок вручну. Замість цього використай:

find . -name "*.txt" | xargs wc -l

Архівування каталогу зі збереженням структури

tar — класика. Але з ключами czvf одразу створюєш .tar.gz-архів поточної директорії:

tar czvf archive.tar.gz folder/

Мережеві команди

Якщо щось не пінгується, не відкривається чи не працює — час перевірити мережу. Тут зібрали команди, з якими це можна зробити за секунди.

Перевірка маршруту до сервера

mtr поєднує функції ping та traceroute, показуючи стан мережі в реальному часі:

mtr google.com

Перевірка порту

nc (netcat) дозволяє перевірити, чи відкритий певний порт на сервері:

nc -zv localhost 80

Дізнатися свою IP-адресу

З цією командою зможеш легко це зробити:

curl ifconfig.me

Хочеш знати, куди реально веде домен? dig копає глибоко:

Перевірка DNS-запису домену

dig google.com

Команди для DevOps-інженерів і системних адміністраторів

Трохи різного — від HTTP-сервера до перегляду вмісту .deb-пакетів. Це утиліти, які часто лишаються в тіні, але дуже виручають у буднях.

Запуск простого HTTP-сервера

Потрібно роздати файли? python допоможе — піднімає HTTP-сервер у поточній директорії на порті 8000:

for Python 2:

python -m SimpleHTTPServer

for Python 3:

python3 -m http.server

Симулятор набору тексту

pv може симулювати повільний набір тексту:

echo "Linux is awesome" | pv -qL 10

Перегляд змонтованих файлових систем у вигляді таблиці

Комбінація mount і column дозволяє зручно все відобразити:

mount | column -t

Пошук символічних посилань

find допоможе знайти всі символічні посилання в поточному каталозі та підкаталогах:

find . -type l

Перегляд вмісту .deb-пакета

Ти можеш переглянути вміст Debian-пакета без його встановлення:

dpkg-deb -c package.deb

Перегляд використання мережі

lsof з параметром -i показує процеси, які використовують мережеві з’єднання.

Пошук команди в історії

Не пам’ятаєш, як саме тоді писав ту круту команду? Шукай по історії:

history | grep something

Перегляд доступних команд в системі

Не лише alias, а взагалі всі виконавчі команди, що є у $PATH. Ідеально, коли не пам’ятаєш точну назву або хочеш швидкий огляд:

compgen -c

Advanced work with git stash

noreply@blogger.com (Adv User) — Fri, 16 Jan 2026 01:29:00 +0200

Advanced work with git stash

In Git, the most recent stash is always assigned the index 0, appearing as stash@{0}. When you create a new stash, all existing stashes are pushed down the stack (e.g., the previous 0 becomes 1).

1. Identify which stash is yours

To see all your stashed entries and their assigned numbers, use:
git stash list

This will output a list like this:

stash@{0}: WIP on master: 4fd1101... (Latest)
stash@{1}: On develop: updated files...

2. View contents without applying

You can inspect the contents of any stash entry using the show command.

View a file summary (stat):
git stash show stash@{0}
(Shows only the list of files changed and the number of insertions/deletions)
View full code changes (diff):
git stash show -p stash@{0}
(The -p or --patch flag shows the actual line-by-line code changes)
View untracked files:
git stash show --include-untracked stash@{0}
View a specific file from a stash:
git diff stash@{0} -- path/to/file.txt

Quick reference commands

To do this...	Run this command
List all stashes	`git stash list`
Peek at latest stash (summary)	`git stash show`
Peek at latest stash (full code)	`git stash show -p`
Peek at specific stash (e.g., #2)	`git stash show -p stash@{2}`

3. create message along with git stash -p

by using the push subcommand with the -m (message) and -p (patch) flags together.

To stash specific parts of your code with a descriptive label, use:

      git stash push -p -m "your custom message here" 
or

      git stash -u -m "message"  //including untracked files

4. how to show git stash {number} diff

View full diff of a specific stash:
git stash show -p stash@{1}
(Replace 1 with whichever stash number you want to inspect).
View just the summary of changed files (diffstat):
git stash show stash@{1}

Alternative Comparisons

Depending on what you want to compare the stash against, you can also use git diff:

Compare stash to your current working directory:
git diff stash@{1}
Compare stash to the tip of a specific branch (e.g., main):
git diff stash@{1} main
View the diff of a single file inside a stash:

git diff stash@{1}^ stash@{1} -- path/to/file.txt

ENV variables files load ordering

noreply@blogger.com (Adv User) — Tue, 13 Jan 2026 22:51:00 +0200

ENV variables files load ordering

Standard Loading Order (Highest to Lowest)

.env.local (local overrides, all environments)
.env.[mode].local (local overrides, specific mode)
.env.[mode] (e.g., .env.development)
.env (default settings)

Example: If DB_HOST is defined in both files, the value in .env.local will be used.

Comparison VS Code, Cursor, Windsurf, Trae, Kiro, Replit

noreply@blogger.com (Adv User) — Sat, 3 Jan 2026 06:48:00 +0200

Comparison VS Code, Cursor, Windsurf, Trae, Kiro, Replit

VS Code, Cursor, Windsurf, Trae, Kiro, and Replit represent a spectrum of modern coding environments, ranging from a highly extensible, traditional local editor (VS Code) to fully cloud-based, AI-driven development and deployment platforms (Replit). Most of the others are AI-first IDEs built on or heavily inspired by VS Code.

Feature	VS Code	Cursor	Windsurf	Trae	Kiro	Replit
Platform	Local desktop app	Local desktop app	Local desktop app	Local desktop app	Local desktop/CLI	Cloud (browser-based)
Core Philosophy	Extensible, traditional editor	AI pair programmer w/ local control	Agentic automation & deep context	Fully free, AI-enhanced editor	Spec-first AI agent	All-in-one build/deploy platform
AI Integration	Via extensions (e.g., Copilot)	Deeply integrated AI chat & refactoring	Agent-focused, multi-file awareness	Built-in models (GPT-4o, Claude 3.5)	Agentic IDE, starts with a spec	Built-in Ghostwriter AI & Agents
Offline Support	Yes	Yes	Yes	Yes	Yes	No
Ecosystem	Vast extension marketplace	Full VS Code extension compatibility	VS Code-style extensions	Many VS Code extensions supported	AWS integrated ecosystem	Built-in services (DB, Auth, etc.)
Best For	Developers wanting control & flexibility	Pro developers who want a powerful local AI-first experience	Large, complex codebases & deep automation	Price-sensitive developers needing strong, free AI tools	Complex projects benefiting from structured planning & automation	Students, indie hackers, teams needing fast prototyping and deployment

Key Takeaways

VS Code is the industry standard for those who value extreme flexibility and a massive ecosystem of extensions. Its AI capabilities come through additions like GitHub Copilot.
Cursor is a fork of VS Code that integrates AI more deeply into the core workflow, focusing on context-aware completions, multi-file refactoring, and AI chat. It is a popular choice for professional developers who want a local, powerful AI assistant.
Windsurf (by Codeium) is an AI rules-based assistant focusing on workflow automation and deep codebase awareness for large projects. It is known for a polished chat experience and strong file lookup systems.
Trae stands out as a completely free, AI-powered IDE with built-in access to premium models like GPT-4o and Claude 3.5 Sonnet, making it highly attractive to developers on a budget.
Kiro is an "AI IDE for adults" that starts every feature with a spec, forcing developers to think through edge cases and security before generating code. It's best for structured planning in complex enterprise environments.
Replit is in a different category as a fully cloud-based IDE with integrated hosting and deployment, requiring zero local setup. It is excellent for collaboration, prototyping, and moving from idea to live application very quickly.

Export Git Stash as patches

noreply@blogger.com (Adv User) — Mon, 15 Dec 2025 10:26:00 +0200

Export Git Stash as patches

git stash show -u -p --binary stash@{0} > your_changes_name.patch

-u - for untracked files

-p - patch

-binary - for binary files (images)

stash@{0} - for fist stash (most fresh one)

now you can transfer the your_changes_name.patch file to the target machine/repository (e.g., via email, USB drive, or cloud storage). In the target repository:

Verify the patch (optional): git apply --check your_changes_name.patch

Apply the patch: git apply your_changes_name.patch. You may use --ignore-whitespace options if conflicts arise due to formatting differences.
The changes will appear in your working directory as unstaged modifications

Grep cheat sheet

noreply@blogger.com (Adv User) — Sat, 29 Nov 2025 03:31:00 +0200

Grep cheat sheet

source https://x.com/thatstraw/status/1789624772826890614

Git, how to know all committers names in the project

noreply@blogger.com (Adv User) — Tue, 18 Nov 2025 04:10:00 +0200

Git, how to know all committers names in the project

To identify all committer names in a Git project, use the git shortlog command with specific flags:

git shortlog -sne --all

Explanation of flags:

-s (or --summary):
This flag summarizes the output, showing the number of commits by each author.
-n (or --numbered):
This sorts the output by the number of commits, with the highest contributor at the top.
-e (or --email):
This displays the email address of each committer alongside their name.
--all:
This ensures that the command considers all branches in the repository, not just the currently checked-out branch.

Output:

The command will produce a list of committers, each followed by their email address and the total number of commits they have made across all branches. For example:

20 John Doe <john.doe@example.com>

15 Jane Smith <jane.smith@example.com>

8 Bob Johnson <bob.johnson@example.com>

Git patch workflow

noreply@blogger.com (Adv User) — Thu, 23 Oct 2025 23:21:00 +0300

In the Git, you can apply patches using the git apply command for changes from a git diff or git am for patches generated by git format-patch. The method you choose depends on the patch's format and whether you want to create a new commit.

Before you apply a patch

Back up your work. Before applying a patch, you should have a clean working directory. Either commit or stash your uncommitted changes to avoid complications.
Use a temporary branch. It's a best practice to create a new, temporary branch to test the patch. If something goes wrong, you can simply delete the branch without affecting your main codebase.
sh
git checkout -b temp-patch-branch
Use code with caution.
Check the patch. To see if the patch will apply cleanly, run a check with the --check flag.
sh
git apply --check my_patch.patch
Use code with caution.

Method 1: Using git apply

Use this command for patches created with git diff. It will apply the changes to your working directory and staging area but will not create a new commit. The commit message, author, and date from the original commit are not preserved.

How to use git apply

# Apply the patch to your working directory
git apply my_patch.patch

# If the patch was generated from a different subdirectory, you may need to strip leading path components.
# The number 'n' represents the number of leading directories to ignore.
git apply -p<n> my_patch.patch

# To add the changes directly to the staging index
git apply --index my_patch.patch

Use code with caution.

Method 2: Using git am

Use this command for patches generated by git format-patch, which are in a more robust "mailbox" format that includes commit metadata. This command automatically applies the patch and creates a new commit, preserving the original author and commit message.

How to use git am

# Apply the patch and create a commit
git am my_patch.patch

# If you are applying multiple patches
git am *.patch

# For complex patches or if a patch fails to apply cleanly,
# use a three-way merge to help resolve conflicts
git am -3 my_patch.patch

Use code with caution.

Handling patch conflicts

If Git cannot apply the patch cleanly, you will encounter conflicts.

If using git apply:
The process will stop and leave .rej (rejected) files in your working directory. You will have to manually resolve the conflicts in your files using the .rej file as a guide, and then use git add and git commit to finalize the changes.

If using git am:
Git will stop and inform you of the conflict.

Open the conflicted files and manually resolve the changes.
After resolving, stage the changes with git add ..
Continue the process with git am --continue.
To abort the process, use git am --abort.

Reversing a patch

If you need to revert a patch, you can use the --reverse or -R flag with git apply.

git apply -R my_patch.patch

Use code with caution.

Git Diff, Git Format-Patch, and Git Apply: What’s the difference?

PowerShell, how to search for a string in the output of the command like grep

noreply@blogger.com (Adv User) — Tue, 30 Sep 2025 16:15:00 +0300

PowerShell, how to search for a string in the output of the command, like grep

Your-Command | Select-String -Pattern "YourSearchString"

I'am sane!

Is it important to make docker compose down before docker compose up -d and docker restart

Is it important to make docker compose down before docker compose up -d and docker restart

Right reset branch (clean history commits after some specific commit)

How to recover all files in folder from specific branch

How to recover all files in folder from specific branch

How to compare 2 commits in git

How to compare 2 commits in git

How to list only commits which was made after branch was splitted(checkouted)

Disk usage analysis in linux

Disk usage analysis in linux

EchoAPI vs Postman

Google Charts API - Gauge Chart Example

Google Charts API - Gauge Chart Example

Preparing your local Postges DB. Resolving timezone headache for developers.

Preparing your local Postges DB

Resolving timezone headache for developers.

Axios returned 403 when i requesting resource which has proper CORS setup - why? (my case)

Axios returned 403 when i requesting resource which has proper CORS setup - why? (my case)

15 поширених команд Linux (repost з ITEDU.center)

htop — зручний перегляд процесів у реальному часі

lsof — перевірка відкритих файлів і портів

journalctl — перегляд логів у системах із systemd

systemctl — керування службами

du — аналіз використання диска

df — перевірка вільного місця

free — моніторинг оперативної памʼяті

uptime — навантаження на систему

top — базовий моніторинг процесів

ps aux — знімок усіх процесів

ss — перевірка мережевих зʼєднань

ip — конфігурація мережі

ping — перевірка доступності

traceroute — діагностика маршрутів

nc — перевірка портів

Як дізнатися в якому шелі ті працюєш зараз

Git - merge investigation commands

1. How to find out if branch has been merged into your current branch

2. How to find out if your current branch has been merged into any other branch3. Edge case with cherry 🍒 (pick)

1. Check if a feature or branch has been merged into your current branch, use the git branch --merged command, the git merge-base command, or inspect the git log.

How to forget to run php ./vendor/bin/drush cr for ever

How to forget to run php ./vendor/bin/drush cr for ever

Tmux - work cases and tune up

Tmux - work cases and tune-up

1. How to scroll rows in tmux terminal spitted windows

2 . To save a tmux layout,

3. how to change horizontal split to vertical split in tmux

4. how to add horizontal and vertical splits in tmux + key bindings

Tmux Split Pane Keybindings

5. How to exit tmux but leave session working

6. How to attach session to tmux

7. How to know how many sessions you have

8. How to kill sessions

9. How to switch between sessions

10. How to rename sessions and panes (panes are small part of the window - splatted in tmux)

11. How to reload tmux configuration from tmux

12. How to enable Digital Clocks in the tmux

Adding not root user to Docker container

Adding not root user to Docker container

Visual representation - Timeline of a React Component With Hooks (link)

Visual representation - Timeline of a React Component With Hooks (link)

30 маловідомих, але корисних команд Linux (repost)

Базові трюки з терміналом

Моніторинг системи та діагностика

Робота з файлами та текстом

Мережеві команди

Команди для DevOps-інженерів і системних адміністраторів

Advanced work with git stash

Advanced work with git stash

1. Identify which stash is yours

2. View contents without applying

3. create message along with git stash -p

Alternative Comparisons

ENV variables files load ordering

ENV variables files load ordering

Comparison VS Code, Cursor, Windsurf, Trae, Kiro, Replit

Comparison VS Code, Cursor, Windsurf, Trae, Kiro, Replit

Export Git Stash as patches

Export Git Stash as patches

Grep cheat sheet

2. How to find out if your current branch has been merged into any other branch

3. Edge case with cherry 🍒 (pick)

2 . To save a `tmux` layout,

`5. How to exit tmux but leave session working`

`6. How to attach session to tmux`

`7. How to know how many sessions you have`

`12. How to enable Digital Clocks in the tmux`