deleted by creator

deleted by creator

Use

set -x

For debugging

I use bash and I usually put /bin/bash in my scrtipts, because that’s where I know it works. /bin/sh is only if it works on many/all shells.

I don’t have many such scripts, so I just have one. I don’t really share them, as they are made for my usecase. If I do create something that I think will help others, then yes, I share them in git somewhere.

I do have a scripts folder in my Nextcloud that I sync around with useful scripts.

Some of your examples can probably just be made into aliases with alias alias_name="command_to_run".

Am I missing something - doesn’t bash have tab completion or of the box?

#!/usr/bin/env bash

A folder dotfiles as git repository and a dotfiles/install that soft links all configurations into their places.

Two files, ~/.zshrc (without secrets, could be shared) and another for secrets (sourced by .zshrc if exist secrets).

• I use bash, because I never had the time to learn anything else.
• Like @[email protected] said, I use the #!/usr/bin/env bash shebang.
• Nope
• Also nope
• Nope. Shell scripts reside in Git repos on Gitlab/Gitea/Forgejo and are checked out using Ansible playbooks onto the servers as necessary.
• For scripts? Python. Read this blog post by the great @[email protected]. For interactive use? bash is just fine for me, though I’ve customized it using Starship and created some aliases to have colored/pretty output where possible.
• Use shellcheck before running your scripts in production, err on the side of caution, set -o pipefail. There are best practices guides for Bash, use those and you’ll probably be fine.
• Be prepared to shave yaks. Take breaks, touch grass, pet a dog. Use set -x inside your Bash script or bash -x scriptname on the CLI for debugging. Remember that you can always fallback to interactive CLI to test/prepare commands before you put them into your script. Think before you type. Test. Optimize only what needs optimization. Use long options for readability. And remember: Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows your address.
• Nope, it’s absolutely not bad practice to create aliases to save you some typing in interactive shell. You shouldn’t use them inside your scripts though, because they might/will not be available in other environments.

I switched to fish because it has tab completion Yeah, so does Bash, just install it.

Oh, I also “curate” a list of Linux tools that I like, that are more modern alternatives to “traditional” Linux tools or that provide information I would otherwise not easily get. I’ll post i

Tools

Debian-Packages available

• mtr
• iputils-tracepath
• iproute2
• zsh
• httpie
• aria2
• icdiff
• progress
• diffoscope
• atop
• powertop
• ntopng
• ethtool
• nethogs
• vnstat
• ss
• glances
• discus
• dstat
• logwatch
• swatch
• multitail
• lynis
• ncdu (du-clone), alias du=“ncdu --color dark -rr -x --exclude .git --exclude node_modules”
• nnn (fully-featured terminal file manager. It’s tiny, nearly 0-config and incredibly fast. https://github.com/jarun/nnn)
• slurm
• calcurse
• newsbeuter
• tig (“ncurses TUI for git. It’s great for reviewing and staging changes, viewing history and diffs.”)
• qalc -ttyrec
• taskwarrior
• ttytter
• ranger
• ipcalc
• pandoc
• moreutils
• googler
• weechat
• pdftk
• abcde
• dtrx
• tload
• ttyload
• cockpit
• sar
• ht (hte Hex Editor)
• dhex
• ack (grep-clone)
• silversearcher-ag (grep-clone)
• ripgrep (“recursively searches file trees for content in files matching a regular expression. It’s extremely fast, and respects ignore files and binary files by default.”, https://github.com/BurntSushi/ripgrep)
• exa (statt ls) https://the.exa.website/ (“replacement for ls with sensible defaults and added features like a tree view, git integration, and optional icons.”)
• fzf (CLI fuzzy finder), alias preview=“fzf --preview ‘bat --color "always" {}’”
• fd (simple, fast and user-friendly alternative to ‘find’, https://github.com/sharkdp/fd) -entr (watch-clone)
• csvkit (awk-clone)
• ccze (log coloring)
• surfraw -hexyl (“hex viewer that uses Unicode characters and colour”, https://github.com/sharkdp/hexyl) -jq (“awk for JSON. It lets you transform and extract information from JSON documents”, https://stedolan.github.io/jq/) -pass (“password manager that uses GPG to store the passwords”, https://github.com/lunaryorn/mdcat)
• restic (“backup tool that performs client side encryption, de-duplication and supports a variety of local and remote storage backends.”, https://restic.net/)
• mdp (Markdown Presentation on CLI) -grepcidr
• qrencode
• caca-utils (show images on the CLI)
• fbi ( & fbgs) (show images in Framebuffer device)
• fbcat (take screnshot on framebuffer device)
• nmap
• micro (CLI Text Editor, ab Debian 11, https://micro-editor.github.io)
• masscan (https://github.com/robertdavidgraham/masscan)
• socat (Nachfolger von netcat, https://www.heise.de/select/ix/2017/11/1509815804306324)
• dc3dd (patched version of GNU dd with added features for computer forensics)
• smem (memory reporting tool)
• free (Show Linux server memory usage)
• mpstat (Monitor multiprocessor usage on Linux, part of sysstat package)
• pmap (Montor process memory usage on Linux, part of the procps)
• monit (Process supervision)
• oping & noping
• saidar (Curses-basiertes Programm für die Anzeige von Live-Systemstatistiken)
• reptyr (Tool for moving running programs between ptys)
• gron (https://github.com/tomnomnom/gron, makes JSON greppable, kann HTTP-Requests absetzen)
• jc (https://github.com/kellyjonbrazil/jc, CLI tool and python library that converts the output of popular command-line tools and file-types to JSON or Dictionaries. This allows piping of output to tools like jq and simplifying automation scripts.)
• bat (cat-clone), alias cat=‘bat’ (“alternative to the common (mis)use of cat to print a file to the terminal. It supports syntax highlighting and - git integration.”, https://github.com/sharkdp/bat)
• ioping (https://github.com/koct9i/ioping, simple disk I/0 latency measuring tool, auch für disk seek rate/iops/avg)
• vd (Visidata, multipurpose terminal utility for exploring, cleaning, restructuring and analysing tabular data. Current supported sources are TSV, CSV, fixed-width text, JSON, SQLite, HTTP, HTML, .xls, and .xlsx)
• pdfgrep
• duf https://github.com/muesli/duf (combined df and du, ncurses-based)
• nala (apt-alternate, https://gitlab.com/volian/nala, https://christitus.com/stop-using-apt/)
• iprange
• tldr
• rmlint
• nvtop (https://github.com/Syllo/nvtop, GPUs process monitoring for AMD, Intel and NVIDIA)
• lf (lf (as in “list files”) is a terminal file manager written in Go with a heavy inspiration from ranger file manager)

no Deb pkg avail

• oh-my-zsh (http://ohmyz.sh)
• webmin
• observium
• cheat (https://github.com/cheat/cheat, create and view interactive cheatsheets on the command-line.)
• bropages
• ipbt / its-playback-time
• todo
• earthquake
• suplemon
• Newsroom
• unity
• ired
• wpe
• prettyping (ping), alias ping=‘prettyping --nolegend’
• diff-so-fancy (diff-clone)
• q (query CSV Files with SQL) https://harelba.github.io/q/
• gping (ping with a graph in CLI)
• http-prompt (install via pip)
• alt (“finding the alternate to a file. E.g. the header for an implementation or the test for an implementation. I use it paired with Neovim”, https://github.com/uptech/alt)
• chars (“shows information about Unicode characters matching a search term.”, https://github.com/antifuchs/chars)
• dot (“dotfiles manager. It maintains a set of symlinks according to a mappings file”, https://github.com/ubnt-intrepid/dot)
• dust (“alternative du -sh. It calculates the size of a directory tree, printing a summary of the largest items.”, https://github.com/bootandy/dust)
• eva (“command line calculator similar to bc, with syntax highlighting and persistent history.”, https://github.com/NerdyPepper/eva)
• hyperfine (“command line benchmarking tool. It allows you to benchmark commands with warmup and statistical analysis.”, https://github.com/sharkdp/hyperfine)
• mdcat (“renders Markdown files in the terminal”, https://github.com/lunaryorn/mdcat)
• podman (“alternative to Docker that does not require a daemon. Containers are run as the user running Podman so files written into the - host don’t end up owned by root. The CLI is largely compatible with the docker CLI.”, https://podman.io/)
• skim (“fuzzy finder. It can be used to fuzzy match input fed to it. I use it with Neovim and zsh for fuzzy matching file names.”)
• z (“tracks your most used directories and allows you to jump to them with a partial name.”, https://github.com/rupa/z)
• alias wetter_graph=‘finger [email protected]’
• alias wetter_color=‘curl wttr.in’
• alias maps_cli=‘telnet mapscii.me’
• https://github.com/say4n/crappybird
• https://asciicker.com
• cbonsai https://gitlab.com/jallbrit/cbonsai
• GNU poke binary editor http://www.jemarch.net/poke / https://git.savannah.gnu.org/cgit/poke.git
• gdu GoDiskUsage https://github.com/dundee/gdu
• Cirrus CLI https://github.com/cirruslabs/cirrus-
• tuxi https://github.com/Bugswriter/tuxi personal CLI assistant
• ngrep https://github.com/jpr5/ngrep
• topgrade https://github.com/r-darwish/topgrade
• ndiff https://nmap.org/ndiff/ compare nmap scans
• natlas https://github.com/natlas/natlas
• sift https://sift-tool.org grep-alternative
• xplr https://github.com/sayanarijit/xplr (hackable, minimal, fast TUI file explorer, stealing ideas from nnn and fzf)
• croc https://github.com/schollz/croc (allows any two computers to simply and securely transfer files and folders, great for forensics)
• slidev https://sli.dev (HTML5 presentations)
• lfs https://github.com/Canop/lfs (df alternative)
• vtop (https://github.com/MrRio/vtop)
• gtop (https://github.com/aksakalli/gtop)
• up (Ultimate Plumber https://github.com/akavel/up)
• ttyd (https://github.com/tsl0922/ttyd, Share your terminal over the web)
• nms (no more secrets, https://github.com/bartobri/no-more-secrets, A command line tool that recreates the famous data decryption effect - seen in the 1992 movie Sneakers.)
• xsv (https://github.com/BurntSushi/xsv, A fast CSV command line toolkit written in Rust.)
• fx (https://github.com/antonmedv/fx, Terminal JSON viewer)
• ccat (https://github.com/owenthereal/ccat, colorized cat mit Syntax Highlighting)
• delta (https://github.com/dandavison/delta, A syntax-highlighting pager for git, diff, and grep output. VORSICHT: Paket einer anderen Software mit gleichem Namen unter Debian Bullseye als Paket verfügbar!)
• dyff (https://github.com/homeport/dyff, /ˈdʏf/ - diff tool for YAML files, and sometimes JSON)

___

A good idea i have been spreading around relevant people lately is to use ShellCheck as you code in Bash, integrate it in your workflow, editor or IDE as relevant to you (there’s a commandline tool as well as being available for editors in various forms), and pass your scripts through it, trying to get the warnings to go away. That should fix many obvious errors and clean up your code a bit.

I use Bash for scripts, though my interactive shell is Fish.

Usually I use #!/usr/bin/env bash as shebang. This has the advantage of searching your PATH for Bash instead of hardcoding it.

My folders are only differentiated by those in my PATH and those not.

Most of my scripts can be found here. They are purely desktop use, no syncing to any servers. Most would be useless there.

For good practice, I’d recommend using set -euo pipefail to make Bash slightly less insane and use shellcheck to check for issues.
This is personal preference, but you could avoid Bashisms like [[ and stick to POSIX sh. (Use #!/usr/bin/env sh then.)

With shortened commands the risk is that you might forget how the full command works. How reliant you want to be on those commands being present is up to you. I wouldn’t implement them as scripts though, just simple aliases instead.
Scripts only make sense if you want to do something slightly more complex over multiple lines for readability.

That’s the way I do it:

#!/usr/bin/env nix
#! nix shell nixpkgs#nushell <optionally more dependencies>  --command nu

<script content>

But those scripts are only used by me

• Do you use bash? If not, which one do you use? zsh, fish? Why do you do it?
• Do you write #!/bin/bash or #!/bin/sh? Do you write fish exclusive scripts?

I use bash, and I use #!/bin/bash for my scripts. Some are POSIX compliant, some have bashisms. But I really don’t care about bashisms, since I explicitly set the bash as interpreter. So no, no fish exclusive scripts, but some “bash exclusive” scripts. Since fish is aimed towards being used as interactive shell I don’t see a real reason to use it as interpreter for scripts anyways.

• Do you have two folders, one for proven commands and one for experimental?
• Do you publish/ share those commands?
• Do you sync the folder between your server and your workstation?

I have my scripts in $HOME/.scripts and softlink them from a directory in $PATH. Some of the scripts are versioned using Git, but the repository is private and I do not plan sharing them because the repoand the scripts scripts contain some not-tho-share information and mostly are simply not useful outside my carefully crafted and specific environment. If I want to share a script, I do it individually or make a proper public Git repository for it.

Since my server(s) and my workstations have different use cases I do not share any configuration between them. I share some configuration between different workstations, though. My dotfiles repository is mainly there for me to keep track of changes in my dotfiles.

is it bad practice to create a handful of commands

It becomes bad practice if it is against your personal or corporate guidelines regarding best practices. While it is not particularly bad or insecure, etc. to create bash scripts containing a single command, maybe use an alias instead. The $1 is automatically the first parameter after typing the alias in the shell.

alias podup="podman compose up -d"
alias poddown="podman compose down"
alias podlog="podman logs -f --tail 20"

Not quite sure about the podman syntax, if podman exec /bin/sh -it "$1" also works, you can use alias podenter="podman exec /bin/sh -it, Otherwise a simple function would do the trick.

I make my scripts with modern shells in mind since they let you use arrays for arguments which is vastly superior to doing \ for continuing the script line, I give the example here https://docs.blissos.org/installation/install-in-a-virtual-machine/advanced-qemu-config/#flexible-bash-scripting

Bash script for simple things (although Fish is my regular shell) and Node or Python scripts for complex things. Using #!/usr/bin/env node works just like it would for Bash so you know.

I use bash for scripts almost exclusively even though i use zsh interactively (startup scripts for zsh are an obvious exception).

The vast majority of my scripts start with

  set -e -u

which makes the script exit if a command (that is not in a few special places like an if) exits with an error status code and also complains about unbound variables when you use them.

Use

bash -n

and

shellcheck

to test your script for errors and problems if you try it.

Always use curly braces for variables to avoid issues with strings after the variable name being interpreted as part of the variable name.

Always use 10# before numbers in $(()) expressions to avoid leading zeroes turning your decimal number variables into octal ones.

Always use

while read -r foo
do
...
done < <(command ...)

instead of

command ... | while read -r foo
do
...
done

to avoid creating a subshell where some changes you make will not affect your script outside the loop.

In

while read -r foo
do
...
done < ...

loops always make sure you redirect all stdin from /dev/null or otherwise close it with suitable parameters or the content of your loop will eat some of the lines you meant for the read. Alternatively fill a bash array in the loop and then use a for loop to call your commands and do more complex logic.

When using temporary directories or similar resources use

cleanup()
{
 ...
}
trap cleanup EXIT

handlers to clean up after the script in case it dies or is killed (by SIGTERM or SIGINT,…; obviously not SIGKILL).

When writing scripts for cronjobs take into account that the environment (PATH In particular) might be more limited. Also take into account that stderr output and non-zero exit status can lead to an email about the cronjob.

Use pushd and popd instead of cd (especially cd …), redirect their output to /dev/null. This will prevent your scripts from accidentally running later parts of the script in a wrong directory.

There are probably many other things to consider but that is just standard stuff off the top of my head.

If you do need any sort of data structure and in particular arrays of data structures use a proper programming language. I would recommend Rust since a compiled language is much easier to run on a variety of systems than the Python so many others here recommend, especially if you need to support the oldest supported version of an OS and the newest one at the same time.

Do you use bash?

Personally I use Bash for scripting. It strikes the balance of being available on almost any system, while also being a bit more featureful than POSIX. For interactive use I bounce between bash and zsh depending on which machine I’m on.

Do you write #!/bin/bash or #!/bin/sh?

I start my shell scripts with #! /usr/bin/env bash. This is the best way of ensuring that the same bash interpreter is called that the user expects (even if more than one is present or if it is in an unusual location)

Do you have two folders, one for proven commands and one for experimental?

By commands, do you mean bash scripts? If so, I put the ones I have made relatively bulletproof in ~/bin/, as bash usually makes them automatically on the path with this particular folder name. If I’m working on a script and I don’t think it’s ready for that, or if it goes with a specific project/workflow, I will move it there.

Do you sync the folder between your server and your workstation?

No. I work on lots of servers, so for me it’s far more important to know the vanilla commands and tools rather than expect my home-made stuff to follow me everywhere.

good practice? general advice?

Pick a bash style guide and follow it. If a line is longer than 80 characters, find a better way of writing that logic. If your script file is longer than 200 lines, switch to a proper programming language like Python. Unless a variable is meant to interact with something outside of your script, don’t name it an all caps name.

is it bad practice to create a handful of commands like podup and poddown that replace podman compose up -d and podman compose down or podlog as podman logs -f --tail 20 $1 or podenter for podman exec -it "$1" /bin/sh?

This is a job for bash aliases.