-- Leo's gemini proxy
-- Connecting to gemini.tuxmachines.org:1965...
-- Connected
-- Sending request
-- Meta line: 20 text/gemini;lang=en-GB
Tux Machines
Posted by Roy Schestowitz on Oct 29, 2022
> Docker is my go-to container deployment tool. I’ve always found it exponentially easier to use than, say, the likes of Kubernetes. Of course, Docker isn’t suited for every deployment. However, when Docker is apropos, it cannot be beaten for simplicity, reliability, and stability. And then you throw in Docker Swarm and you can scale to meet needs.
> But one thing that can still be rather challenging, even with the likes of Docker, is troubleshooting. With container deployments (especially full-stack applications), there are a lot of moving parts to go wrong, and, when something does go wrong, figuring out the culprit can be a real pain in the keister.
> A headless browser means a web browser without a graphical user interface. This implies the users can access the webpages but in the command line interface, not in a graphical user interface. Headless browsers are particularly used by developers and system administrators for testing web pages. It is because in headless they can understand the rendering of HTML in a better way including styling elements such as page layout, color, font selection, and execution of JavaScript and Ajax which are usually not available when using other testing methods.
> Well, in Google Chrome and FireFox, apart from the Graphical user interface, headless support is also there out of the box.
> Using Google Chrome headless or other browsers we can perform automation testing of web apps, javascript libraries; the interaction of web pages, and even save the website page in PDF or can take screenshots. Headless browsers are also useful in web scraping.
> The case statement is generally used in Bash when you have multiple choices to select from. Using it instead of nested if-else statements helps keep your Bash scripts easier to read and maintain.
> The Bash case statement has been designed similar to the case statement from JavaScript and C. Unlike the switch statement from C, the Bash case statement stops searching for other matches as soon as it finds one and completes the statements that are written for the pattern.
> In this guide, we will explain how you can use the Bash case statement using two examples and some scenarios in Ubuntu 22.04.
> Everyone loves music, and despite the advent of streaming, subscription models, and having music available in the cloud, audiophiles still maintain a carefully curated collection of audio files on their local machines.
> If you're a terminal-dwelling Linux user, it's easy to play your tunes while you work, without ever leaving the command line.
> In this tutorial, we will show you how to install Audacious on Ubuntu 22.04 LTS. For those of you who didn’t know, Audacious is a free advanced audio player for Linux and many other UNIX-compatible systems. It is a lightweight music player as it uses few resources. Enjoy the modern Qt-themed interface or change things up with Winamp Classic skins. Use the plugins included with Audacious to fetch lyrics for your music, display a VU meter, and more.
> This article assumes you have at least basic knowledge of Linux, know how to use the shell, and most importantly, you host your site on your own VPS. The installation is quite simple and assumes you are running in the root account, if not you may need to add ‘sudo‘ to the commands to get root privileges. I will show you the step-by-step installation of the Audacious audio player on Ubuntu 22.04 (Jammy Jellyfish). You can follow the same instructions for Ubuntu 22.04 and any other Debian-based distribution like Linux Mint, Elementary OS, Pop!_OS, and more as well.
> I run a number of Tmux sessions, one for each project or context, (via Byobu) to do my work on a daily basis. Tmux uses a client-server architecture, so there's a Tmux server running that all of these sessions connect to. Some time ago, I began noticing that all my Tmux sessions were being killed while I worked. I knew this wasn't a random occurrence. A look at the logs told me that systemd-oomd was killing my Tmux server, and all my sessions and their windows with it---all my vim sessions, all of it.
> This, of course, is far from ideal. What's happening here is that one of the processes occupying a Tmux window consumes lots of CPU/memory and systemd-oomd needs to kill it. However, systemd-oomd does not work on a per-process level. It works on a cgroup level. So, it kills the whole cgroup, taking the Tmux server down.
-- Response ended
-- Page fetched on Sat Jun 1 08:10:13 2024