Whether you are an experienced shell user, or just a newbie, have a look at this article for a collection of the great tools and examples of how to process text in the shell. It includes all the usual suspects: cat, head, tail, wc, grep, cut, paste, sort, uniq, awk, tr, fold, and sed. Great examples and real life scenarios for each are also provided, with the logic explained and more complex use cases broken down into steps.
ctop is a very simple, but very useful tool for when you run a number of Docker containers and want to have a top-like overview of their CPU, memory, and network usage.
This article provides more details on how to install, run, and use ctop effectively, including container filtering, single container view, etc.
Postman is a great tool for building and testing APIs. Unfortunately, however, it doesn’t come packaged as an RPM, so there’s some trickery involved in installing it on Fedora.
This blog post was very useful, with some minor corrections. Here’s what I had to do:
- Download Postman from the site.
- Move the archive to somewhere global: mv Postman-linux-x64-7.16.1.tar.gz /opt/
- Extract the archive: tar xzvf Postman-linux-x64-7.16.1.tar.gz
- Remove the archive: rm Postman-linux-x64-7.16.1.tar.gz
- Check which directories are in the path: echo $PATH
- Create a symbolic link in one of path directories: sudo ln -s /opt/Postman/Postman /usr/local/bin/postman
- Create the desktop file: touch ~/.local/share/applications/postman.desktop
- Edit the file with the content below.
[Desktop Entry] Name=Postman GenericName=API Client X-GNOME-FullName=Postman API Client Comment=Make and view REST API calls and responses Keywords=api; Exec=/usr/local/bin/postman Terminal=false Type=Application Icon=/opt/Postman/app/resources/app/assets/icon.png Categories=Development;Utilities;
Now you can run bitcoin casino Postman both via the command line (postman) and from the Gnome/Mate menu. You’ll find it under Applications->Programming.
dive is a Docker image explorer. This is a very handy tool when you are trying to figure out how a Docker image was built and what’s in it, and you don’t have the original Dockerfile.
It uses the meta information for each layer to show you which command was used to create the layer, and which files were added, removed, or changed.
Additionally, you can use dive to make sure your Docker images are optimized and their size is under control. You can even integrate dive into your CI/CD pipeline!
I’ve updated my laptop to Fedora 31 over the Christmas holidays. Pretty much everything works as it did before. Except for Docker, which suddenly fails to start the service.
A quick Google search pointed to the discussion in this bug report, where I found the solution that worked for me:
- Edit /etc/sysconfig/grub
- Append systemd.unified_cgroup_hierarchy=0 to the GRUB_CMDLINE_LINUX variable
- Run “grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg“
Once the machine came back up gambling bitcoin, docker service was running normally.