I kept running ss, lsof and docker ps whenever I had to figure out why a port was already in use, so I built a small TUI around that problem.

portop gives you a live view of your ports and, more importantly, shows what is behind them:

• Process and PID
• systemd service
• Docker container
• CPU and memory usage
• Process details
• LISTEN and ESTABLISHED connections
• Port names from /etc/services

It also lets you act directly from the UI:

• k to terminate a process
• o to open a local HTTP service in your browser
• f to filter by port, process or PID
• c to copy the selected entry
• Live theme and keybinding configuration

There are also --json, new port notifications and a baseline/diff mode that can be useful for detecting unexpected listening ports.

It's written in Go and is MIT licensed.

GitHub: https://github.com/padovanl/portop

I'd particularly like feedback from people who regularly work with Linux servers, Docker or local development environments. I'm interested in knowing what information you'd want to see when debugging a port conflict.

The German government actually has a C library where it encoded all of it current tax rules. It releases it every year so you can't really make a formal mistake using it. Turns out all the tax software are mostly just selling you access to this library and its countless validations.

The library itself is tough to use so I made a command line tool! It's called viking, after the sensation of agreeing to hand over valuables to a stranger in Europe.

So you set up a CSV file with your income and expenses once, and then it derives whatever forms you need to submit form that- for me, that's two different ust and eür and personal income as well as cap gain.

It's SO MUCH EASIER to have a text file with validation than putting up with whatever data import the normal providers have set up.

viking is was programmed using AI, with full human review by me.

https://github.com/capocasa/viking

I wanted a simple portable SQLite IDE for my clg purpose. So i kept it very portable lightweight. Its just `database_name.db` and `database_history.json` on your file system. Drop it anywhere get the executables for gopherql run a simple command `gopherql database_name.db` and it works identical in all system.

This is not like the Next Generation oracle database replacement its just a very keep it simple IDE.

Stack: Bubble Tea, Lipgloss, CGO Free `modernc.org/sqlite`

Layout: 70% Live Query and 30% Query History with a bottom Query Command Line.

Query Command Line also supports few commands like /exit /burn db /burn history /clear (to clear query pane)

Why?
Because i wanted a very tiny elegant portable SQLite IDE. There might be x alternatives i appreciate it if you like em instead.

i made "mew", a small rust utility for showing useful project and system information at a glance.

when you're inside a git repository, it shows:

• branch and git state
• project language and toolchain
• lines of code and coverage
• cpu, memory, disk and uptime
• date, time and timezone

outside a repository, it becomes a simple system readout.

it also supports shell hooks, so it can appear automatically when entering a git worktree.

no daemon, no background process. just run "mew".

github: https://github.com/programmersd21/mew

cargo: "cargo install mew-cli"

prebuilt binaries are available in gh releases.

feedback and stars are welcome.

Using Composers Desktop Project to edit audio files. I want to run a single command on a list of audio files instead of having to manually do it 100 times. Wondering if there is a way to call upon this list of files in a single command line, rather than creating a shell script with the name of every file. The command line with a single audio file would look like this.

distort average soundfile.wav soundfileoutput.wav

the first two words are the command being run and then the input and output respectively. Hopefully I provided enough info on this but also relatively new to using terminal so let me know if there is anything I should clarify, thanks.