# scripts Published articles for scripts. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Libreboot 20220710 released! DevFeed: [Libreboot 20220710 released!]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: release Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [releases](), [coreboot](), [Linux]() Tags: [article](), [bios](), [build-system](), [canoeboot](), [coreboot](), [documentation](), [free-software](), [gcc](), [hardware](), [libre](), [libreboot](), [linux](), [opensource](), [release](), [releases](), [scripts](), [security](), [speed](), [testing](), [uefi](), [upgrade](), [usb](), [version]() ### AI overview Libreboot 20220710 is a stable bug-fix release relative to version 20211122. It adds documentation snapshots and fixes or improves GRUB boot performance, laptop compatibility, build behavior, USB keyboard support, coreboot configuration, and related tooling. No new boards or major features were added. ### Source excerpt Article: Libreboot 20220710 released! Web link: https://libreboot.org/news/libreboot20220710.html ## I taught a robot to detect Joshes DevFeed: [I taught a robot to detect Joshes]() Original publisher: [Read original article]() Author: Josh Sherman Published: 2026-08-16T00:00:00Z Content type: opinion Language: en Sources: [Josh Sherman]() Topics: [Website](), [Script](), [Code](), [SRE]() Tags: [agent](), [claude-code](), [code](), [review](), [scripts]() ### AI overview A developer describes experiments to automate a web directory for people named Josh. Scripts discover relevant websites and open pull requests, while a robot reviews them and the author retains final approval. ### Source excerpt This journey starts like most of the things I've been doing this year, as an experiment to run a website 100% unattended with an agent. Ideally this post won't go down as an epitaph in a future where robots hunted down unsuspecting humans named Josh. I'm aware of "claws" and I know I could probably just boot up Claude Code with a /goal or /loop prompt like: build and maintain an awesome website, autonomously. seriously don't freakin' bother me, like ever. you're the boss here. make the site really great, and ideally figure out how to make me a bajillionaire. loljk, but tres commas shouldn't be an afterthought. What this actually looks like: robot files a request, and I approve or reject it. It's still very permission based. The gathering of the Joshes I already phoned in a post about this back in January. I started a simple web directory for humans named Josh. As to not be exclusionary, Joshuas, Joshis, and other Josh-adjacent names are welcome. Not wanting to bother with outbound sales for this project, I got creative with some discovery efforts along the way. It's a series of scripts to seek out Josh websites, with the help of my friendly robot Igor to screen PRs and handle SRE duties during merges. Thus far, I am still the final approval on the PRs. It's a tough job, and quite frankly, I don't want to do it. Living in the future, today These experiments are all part of what I think the future is going to look like. I'm clearly living in the shared hallucination of what still feels like a smaller number of my peers. I also live in reality, where the tech still doesn't feel like it's quite there yet. My thought is, if you conduct yourself like it's 2032 and we're all being shuffled around in our hover chairs like in WALL-E, maybe it will all happen sooner. I also think the tech is fun, and watching a computer take my human words and turn them into dumb ideas I described feels like magic. The same magic I felt when I made an Atari computer spew a wall of "JOSH" acro ## Proxmox VE Helper-Scripts: guía y buenas prácticas DevFeed: [Proxmox VE Helper-Scripts: guía y buenas prácticas]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-04T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Proxmox](), [Bash](), [Script](), [Command-line interface](), [qemu](), [GitHub]() Tags: [bash](), [community](), [github](), [http](), [proxmox](), [qemu](), [root](), [script](), [scripts](), [shell]() ### AI overview This guide explains what Proxmox VE Helper-Scripts are, how community-scripts.org uses Bash scripts to deploy applications in LXC containers or QEMU virtual machines, and how the main script downloads and runs the required components. It also highlights the security risk of executing third-party code as root on a Proxmox hypervisor. ### Source excerpt Qué son los Proxmox VE Helper-Scripts de community-scripts.org, cómo despliegan LXC y VMs con un solo comando y qué riesgos de seguridad debes valorar. ## Python Automation Script Ideas for Network Engineers DevFeed: [Python Automation Script Ideas for Network Engineers]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-20T20:33:48Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [Python](), [networking](), [Automation](), [BGP]() Tags: [automation](), [devops](), [network](), [network-operations](), [python](), [scripts]() ### AI overview This tutorial presents Python automation script ideas for network engineers. It covers running commands across devices, scanning configurations, generating inventory reports, monitoring optical power, and verifying BGP sessions. ### Source excerpt Python has become one of the most valuable tools in a network engineer's toolbox. You do not need to write thousands of lines of code or become a software developer to get value from it. If you are kind of old school like me, anything other than bash scripting might be new. In this article, ... Read more The post Python Scripts Every Network Engineer Should Know appeared first on Justin Wilson (j2sw). ## Why your platform control plane belongs on Temporal DevFeed: [Why your platform control plane belongs on Temporal]() Original publisher: [Read original article]() Author: Joshua Smith Published: 2026-03-31T00:00:00Z Content type: opinion Language: en Sources: [Temporal Blog]() Topics: [control-plane](), [Automation](), [Orchestration](), [Terraform]() Tags: [automation](), [control-plane](), [error](), [infrastructure](), [orchestration](), [platform](), [platform-teams](), [provisioning](), [scripts](), [self-service](), [temporal-voices]() ### AI overview This article argues that Temporal can serve as a durable backbone for platform teams building internal control planes. It describes the difficulty of managing infrastructure across creation, monitoring, upgrades, configuration changes, and decommissioning, and contrasts Temporal's orchestration model with Terraform's declarative provisioning and reconciliation focus. ### Source excerpt Discover why platform teams use Temporal to build resilient internal control planes. Learn how Durable Execution solves brittle infrastructure automation. ## Git para sysadmins: control de versiones DevFeed: [Git para sysadmins: control de versiones]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-02-16T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Git](), [Linux](), [Ansible](), [nginx](), [Firewall](), [Terraform](), [Command-line interface](), [Script](), [Terminal](), [Gitea](), [GitHub](), [GitLab]() Tags: [ansible](), [env-file-security](), [firewall](), [git](), [github](), [gitlab](), [linux](), [scripts](), [sysadmin](), [sysadmins](), [terminal](), [terraform]() ### AI overview A practical Spanish-language guide explains how sysadmins can use Git to version server configurations, infrastructure-as-code files, and maintenance scripts. It covers repository setup, commits, branches, remotes, collaboration, and avoiding secrets in version control. ### Source excerpt Guía práctica de Git para sysadmins: versiona configuraciones, gestiona infraestructura como código y colabora en equipo sin miedo a romper nada. ## 10 scripts Bash útiles para sysadmins DevFeed: [10 scripts Bash útiles para sysadmins]() Original publisher: [Read original article]() Author: Alois Published: 2026-01-14T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Scripting, bash](), [Bash](), [backups](), [monitor](), [rsync]() Tags: [backups](), [bash](), [logs](), [rsync](), [script](), [scripts](), [shell](), [sysadmin](), [sysadmins]() ### AI overview A Spanish-language tutorial presents ten practical Bash scripts for system administrators, including disk monitoring, rotating backups, log cleanup, and other routine tasks. It notes that Bash scripts suit focused tasks on individual machines but are not a replacement for configuration-management tools when managing many servers. ### Source excerpt Colección de scripts Bash prácticos para monitorización, backups, limpieza de logs y tareas comunes de administración de sistemas. ## How to convert your job scheduling system to Temporal Schedules DevFeed: [How to convert your job scheduling system to Temporal Schedules]() Original publisher: [Read original article]() Author: Irina Belova Published: 2024-04-15T04:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Job](), [migration](), [systems](), [retry](), [Script]() Tags: [how-to](), [job](), [migration](), [replacement](), [retry](), [scheduling](), [scripts](), [worker](), [workflow]() ### AI overview This tutorial explains how to migrate existing cron and other scheduled jobs to Temporal Schedules. It covers wrapping non-Temporal scripts in Activities, assessing schedule and overlap requirements, handling retries and failures, and deploying workflows in a Temporal Worker. ### Source excerpt Temporal Schedules offer a reliable, efficient alternative to traditional job schedulers, replacing Cron, systemd timers, and task queues like Celery. ## My Second Brain... 6 Months later: Obsidian update DevFeed: [My Second Brain... 6 Months later: Obsidian update]() Original publisher: [Read original article]() Published: 2023-09-13T00:00:00Z Content type: article Language: en Sources: [Mutt0-ds Notes]() Topics: [Obsidian](), [Markdown](), [Automation](), [Documentation](), [Python]() Tags: [automation](), [code](), [documentation](), [markdown](), [notes](), [obsidian](), [ocr](), [plugins](), [repository](), [scripts](), [search](), [security](), [update]() ### AI overview The author provides a six-month update on using Obsidian as a secure, structured repository for team documentation and personal notes. They describe collecting and organizing varied information, linking orphaned notes, storing code snippets, and experimenting with automation, including OCR-based conversion of PowerPoint and Word content into searchable Markdown. ### Source excerpt It's been quite the journey since I first delved into Second Brain technologies for organizing my team's documentation. I previously shared... ## My Personal Airflow - How I'm monitoring my scripts with Python, Appsmith and SQL Server DevFeed: [My Personal Airflow - How I'm monitoring my scripts with Python, Appsmith and SQL Server]() Original publisher: [Read original article]() Published: 2022-04-21T00:00:00Z Content type: tutorial Language: en Sources: [Mutt0-ds Notes]() Topics: [Monitoring](), [Python](), [sql-server](), [Full-Stack](), [airflow](), [Back end]() Tags: [backend](), [dashboard](), [database](), [full-stack](), [monitoring](), [python](), [scripts](), [sql-server]() ### AI overview A personal project uses Python, SQL Server, and Appsmith to monitor locally run scripts. The author describes the monitoring problem, the proposed backend, database, and frontend, and a Python logging module built around a decorator. ### Source excerpt Here's the story of how I created my first full-stack project for monitoring my daily activities, using Python and SQL Server in backend... ## Creating a Reverse Proxy for Partytown with AWS Cloudfront DevFeed: [Creating a Reverse Proxy for Partytown with AWS Cloudfront]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2022-02-18T15:49:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Amazon Web Services](), [proxy](), [Cross-origin resource sharing (CORS)](), [JavaScript](), [Library]() Tags: [aws](), [cloudfront](), [cors](), [create](), [easily](), [insights](), [javascript](), [learn](), [library](), [party](), [partytown](), [performance](), [performantly](), [proxy](), [quickly](), [reverse](), [reverse-proxy](), [scripts](), [third-party](), [tracking](), [worker]() ### AI overview A tutorial on creating an AWS CloudFront reverse proxy for Partytown so third-party tracking scripts can run in a web worker. It explains that some scripts require a reverse proxy because their origins do not provide permissive CORS headers. ### Source excerpt Learn how to quickly & easily create a reverse proxy with AWS Cloudfront for Partytown, so your third party tracking scripts can run performantly in a web worker ## Joining Charm to work on command-line tools DevFeed: [Joining Charm to work on command-line tools]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2021-12-28T00:00:00Z Content type: opinion Language: en Sources: [Carlos Becker]() Topics: [Command-line interface](), [dotfiles](), [Script](), [Tool]() Tags: [cli](), [command-line](), [scripts](), [tools](), [work]() ### AI overview The author announces that they are joining Charm to work on command-line tools, drawing on their experience with dotfiles, scripts, automations, and other tools. ### Source excerpt $ glow charm.md ## Tasteless 21: Godot Game Hacking in Tasteless Shores DevFeed: [Tasteless 21: Godot Game Hacking in Tasteless Shores]() Original publisher: [Read original article]() Published: 2021-10-03T00:00:00Z Content type: tutorial Language: en Sources: [mahaloz.re]() Topics: [Godot](), [Hacking](), [ctf](), [Script](), [client](), [servers](), [Linux]() Tags: [challenges](), [ctf](), [game](), [game-hacking](), [game-servers](), [github](), [hacking](), [hosting](), [ida](), [linux](), [multiplayer](), [reversing](), [scripts]() ### AI overview A writeup of Tasteless 21 multiplayer game-hacking challenges involving a Godot game. It describes analyzing resource packs and binaries, modifying and recompiling Godot scripts, and abusing client-side computations to create hacks such as flying, taking no damage, moving faster, and manipulating random-number behavior. ### Source excerpt A series of game hacking challenges hosted in Tasteless 21. Decompiling, modifying, and recompiling Godot scripts to abuse client-side computations for a multiplayer game. Fly hacks, no-damage, super speed, and rng abuse. ## Using GoReleaser includes feature DevFeed: [Using GoReleaser includes feature]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2021-07-03T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [configuration](), [Template](), [GitHub Actions](), [Script](), [deprecated]() Tags: [config](), [deprecated](), [files](), [github-actions](), [include](), [modular](), [scripts](), [using](), [variables](), [workflow]() ### AI overview This tutorial explains how to use GoReleaser Pro's includes feature to share full or partial configuration files across projects. It describes a modular repository of reusable configuration files, custom template variables, recursive imports, and a GitHub Actions workflow that detects deprecated or invalid settings. ### Source excerpt GoReleaser Pro was released about a month ago, and with it, the ability to include GoReleaser config files. ## stup - Daily notes in the terminal DevFeed: [stup - Daily notes in the terminal]() Original publisher: [Read original article]() Author: Lazarus Lazaridis Published: 2020-04-20T09:00:00Z Content type: tutorial Language: en Sources: [Lazarus Lazaridis]() Topics: [Command-line interface](), [Terminal](), [Code](), [opensource]() Tags: [bash](), [blocking](), [cli](), [code](), [linux](), [meetings](), [opensource](), [productivity](), [programming](), [scripts](), [terminal](), [tools]() ### AI overview The article introduces stup, an open-source command-line tool for recording, organizing, and retrieving daily work notes from a terminal. It explains the tool's note categories, date-based storage, and commands for adding, viewing, and listing notes over time. ### Source excerpt Over the past few years I have been participating in Stand-up meetings and it took me some time to find a convenient and effective way for keeping notes about what I was doing every day. I needed to be able to: keep notes on the issues I worked on, the meetings I participated in and stuff that blocked my work easily access these notes based on their date have an overview of what I did for example the last week all of the above from inside a terminal without having to manually structure and update a single document having to manually create a document for each day stup I created stup (the name derives from stand-up), an opensource CLI tool that deals with these issues and allows to easily save, access and organize my notes. The source code of the project is available on GitHub here. Usage examples Find below some examples showing the most important usage of stup. Adding notes # Adding a note to the default category at current date stup add -n "Worked on issue #ABC123" # Adding a note to the default category setting the current date explicitly stup add today -n "Worked on issue #ABC123" # Adding a note to the meetings category stup add today -c "meetings" -n "2 hours with @phoebe for the project kick off" # Adding a note to the blocking category for April 10th, 2020 stup add @ 2020-04-10 -c "blocking" -n "connectivity issues" Showing notes # Showing yesterday's notes $ stup # Showing yesterday's notes explicitly setting the date $ stup yesterday # Showing today's notes $ stup today # Showing notes on a specific date $ stup show @ 2020-04-18 # Showing notes on a specific date for the meetings category $ stup show @ 2020-04-18 -c "meetings" Retrieving all notes for a period of time # List current week's notes stup log week # List previous week's notes stup log previous-week # List notes between January 20th, 2020 and March 2nd, 2020 stup log --from 2020-01-20 --to 2020-03-02 # List meeting notes between January 20th, 2020 and March 2nd, 2020 stup log --from 2020-01-20 - ## Find palindrome dates in the Linux command line - explained DevFeed: [Find palindrome dates in the Linux command line - explained]() Original publisher: [Read original article]() Author: Lazarus Lazaridis Published: 2020-02-06T10:00:00Z Content type: tutorial Language: en Sources: [Lazarus Lazaridis]() Topics: [Command-line interface](), [Linux](), [Terminal]() Tags: [awk](), [bash](), [climagic](), [command-line](), [commands](), [how-to](), [linux](), [opensource](), [programming](), [scripts](), [terminal]() ### AI overview A tutorial explains a Linux command-line pipeline for finding palindrome dates. It breaks down brace expansion, date formatting, whitespace removal, reversing and comparing date strings with standard command-line tools. ### Source excerpt Yesterday I saw a great command that finds the palindrome dates between now and x days ago. The command was posted on Twitter by @climagic (a great account to follow if you want to find awesome command line stuff). In this post we are going to break it down and explain how it works. What is a palindrome Palindrome is a word/number/phrase or other sequence of characters that reads the same backward as forward. - Palindrome - Wikipedia Few days ago, the date was 02/02/2020 which was a palindrome: The command printf "now - %d days\n" {1..332044} |date -f- +%Y%_m%_d$'\n'%Y%m%d |tr -d ' ' > alldates.txt; rev alldates.txt >revdates.txt; paste alldates.txt revdates.txt |awk '$1==$2{print $1}' And here's a more readable version using new lines after each pipe. printf "now - %d days\n" {1..332044} | date -f- +%Y%_m%_d$'\n'%Y%m%d | tr -d ' ' > alldates.txt; rev alldates.txt >revdates.txt; paste alldates.txt revdates.txt | awk '$1==$2{print $1}' I am going to explain each part of the command separately. Note that the output of each part is the input of the next part (following the pipe |). printf "now - %d days\n" {1..332044} The first part seems pretty straight forward but it does have an interesting part, the brace expansion mechanism, which I didn't know of. Open a terminal and type the following commands: # From 1 to 10 $ echo {1..10} 1 2 3 4 5 6 7 8 9 10 # From a to z $ echo {a..z} a b c d e f g h i j k l m n o p q r s t u v w x y z # From 10 to 20 $ echo Before-{10..20}-After Before-10-After Before-11-After Before-12-After Before-13-After Before-14-After Before-15-After Before-16-After Before-17-After Before-18-After Before-19-After Before-20-After As you can see, the brace expansion allows the generation of values based on a "sequence" we set. Learn more about the Brace expansion mechanism here. Part explained we print the phrase "now - x days" so many times as the number of values expanded from the sequence {1..332044} will generate 332044 values starting from 1 and in ## When TCP sockets refuse to die DevFeed: [When TCP sockets refuse to die]() Original publisher: [Read original article]() Author: Marek Published: 2019-09-19T22:00:00Z Content type: tutorial Language: en Sources: [Marek Majkowski]() Topics: [Linux](), [Kernel](), [Server]() Tags: [article](), [blog](), [bug](), [cloudflare](), [commands](), [kernel](), [retries](), [scripts](), [tcp](), [timeout]() ### AI overview A technical tutorial explains when Linux TCP sockets time out and how TCP keepalives and the TCP_USER_TIMEOUT socket option interact. It discusses connection establishment, SYN retries, kernel behavior, and a possible bug observed on Linux kernel 5.2. ### Source excerpt When TCP sockets refuse to die This article was first published on Cloudflare blog: While working on our Spectrum server, we noticed something weird: the TCP sockets which we thought should have been closed were lingering around. We realized we don't really understand when TCP sockets are supposed to time out! In our code, we wanted to make sure we don't hold connections to dead hosts. In our early code we naively thought enabling TCP keepalives would be enough... but it isn't. ## How to remove duplicate lines from files preserving their order DevFeed: [How to remove duplicate lines from files preserving their order]() Original publisher: [Read original article]() Author: Lazarus Lazaridis Published: 2019-05-16T08:30:00Z Content type: tutorial Language: en Sources: [Lazarus Lazaridis]() Topics: [Script](), [file]() Tags: [approach](), [awk](), [bash](), [featured](), [file](), [files](), [how-to](), [linux](), [programming](), [scripts]() ### AI overview A tutorial explains how to remove duplicate lines from a text file with awk while preserving their original order. It breaks down the associative array, line-occurrence tracking, negation, post-increment behavior, and why other approaches may not preserve order. ### Source excerpt Suppose you have a text file and you need to remove all of its duplicate lines. TL;DR To remove the duplicate lines preserving their order in the file use: awk '!visited[$0]++' your_file > deduplicated_file How it works The script keeps an associative array with indices equal to the unique lines of the file and values equal to their occurrences. For each line of the file, if the line occurrences are zero then it increases them by one and prints the line, otherwise it just increases the occurrences without printing the line. I was not familiar with awk and I wanted to understand how is this accomplished with such a short script (awkward). I did my research and here is what is going on: the awk "script" !visited[$0]++ is executed for each line of the input file visited[] is a variable of type associative array (a.k.a. Map). We don't have to initialize it, awk will do this for us the first time we access it. the $0 variable holds the contents of the line currently being processed visited[$0] accesses the value stored in the map with key equal to $0 (the line being processed), a.k.a. the occurrences (which we set below) the ! negates the occurrences value: In awk, any nonzero numeric value or any nonempty string value is true By default, variables are initialized to the empty string, which is zero if converted to a number That being said: if visited[$0] returns a number greater than zero, this negation is resolved to false. if visited[$0] returns a number equal to zero or an empty string, this negation is resolved to true. the ++ operation increases the variable's value (visited[$0]) by one. If the value is empty, awk converts it to 0 (number) automatically and then it gets increased. Note: the operation is executed after we access the variable's value. Summing up, the whole expression evaluates to: true if the occurrences are zero/empty string false if the occurrences are greater than zero awk statements consist of a pattern-expression and an associated action. ) Original publisher: [Read original article]() Author: Lazarus Lazaridis Published: 2019-05-02T12:30:00Z Content type: tutorial Language: en Sources: [Lazarus Lazaridis]() Topics: [elasticsearch](), [kibana](), [API]() Tags: [elasticsearch](), [how-to](), [kibana](), [nested-objects](), [opensource](), [programming](), [script](), [scripts](), [update]() ### AI overview This tutorial explains how to manage nested objects in Elasticsearch documents using Kibana. It covers defining a nested mapping, indexing a document containing cats, and adding, removing, and updating nested objects through the Update API and scripts. ### Source excerpt In this post we are going to manage nested objects of a document indexed with Elasticsearch. The nested type is a specialised version of the object datatype that allows arrays of objects to be indexed in a way that they can be queried independently of each other. - Nested datatype - Official Elasticsearch reference Prerequisites To follow this post you need: an up and running Elasticsearch instance I use 6.7 here an up and running Kibana instance to interact with Elasticsearch Preparation The document of our index will represent a human and its nested objects will be cats (no surprises). Create the index Open your Kibana dev console and type the following to create the index. # Create the index PUT iridakos_nested_objects { "mappings": { "human": { "properties": { "name": { "type": "text" }, "cats": { "type": "nested", "properties": { "colors": { "type": "integer" }, "name": { "type": "text" }, "breed": { "type": "text" } } } } } } } Human has: a name property of type text a cats property of type nested Each cat has: a colors property of type integer a name property of type text a breed property of type text Add a human In the Kibana console, execute the following to add a human with three cats. # Index a human POST iridakos_nested_objects/human/1 { "name": "iridakos", "cats": [ { "colors": 1, "name": "Irida", "breed": "European Shorthair" }, { "colors": 2, "name": "Phoebe", "breed": "European" }, { "colors": 3, "name": "Nino", "breed": "Aegean" } ] } Confirm the insertion with: GET iridakos_nested_objects/human/1 You should see something like this: { "_index": "iridakos_nested_objects", "_type": "human", "_id": "1", "_version": 1, "found": true, "_source": { "name": "iridakos", "cats": [ { "colors": 1, "name": "Irida", "breed": "European Shorthair" }, { "colors": 2, "name": "Phoebe", "breed": "European" }, { "colors": 3, "name": "Nino", "breed": "Aegean" } ] } } Done, moving on. Managing nested objects Add a new nested object Suppose that iridakos got a new Persian ## How to alias and navigate to directories with autocomplete in Linux DevFeed: [How to alias and navigate to directories with autocomplete in Linux]() Original publisher: [Read original article]() Author: Lazarus Lazaridis Published: 2019-04-10T13:00:00Z Content type: tutorial Language: en Sources: [Lazarus Lazaridis]() Topics: [Shell](), [Script](), [Command-line interface](), [Linux](), [Utility Software](), [Scripting, bash]() Tags: [aliases](), [bash](), [completion](), [directory](), [how-to](), [installation](), [linux](), [opensource](), [productivity](), [programming](), [script](), [scripts](), [shell](), [tools](), [tutorial]() ### AI overview This tutorial introduces goto, a shell utility for navigating to registered directory aliases with autocomplete. It explains installation, alias management, navigation, cleanup, help, version commands, and directory-stack features. ### Source excerpt I use the terminal a lot and in my day to day work I tend to navigate to the same bunch of directories. There are some awesome tools out there (like autojump or z) but sometimes, especially when the directories are similarly named, there is a need to be explicit to navigate to the proper one. I decided to write a script to overcome this issue and to avoid having to edit my .bash* files to manage aliases each time I wanted to add or remove a directory. goto goto is a shell utility to quickly navigate to aliased directories with autocomplete (tab completion). goto repo at GitHub User registers directory aliases, for example: goto --register dev /home/iridakos/development and then cds to that directory with: goto dev Find below documentation on the script but make sure you check the script's documentation page for updates. Sorry for the name, I know it brings back memories but it's not what it seems :) Installation To install goto all you have to do is clone the repository locally: git clone https://github.com/iridakos/goto.git navigate to it cd goto and execute: sudo ./install You need to restart your shell after installation. Usage Change to an aliased directory Register an alias Unregister an alias List aliases Expand an alias Cleanup Help Version Extras Push before changing directories Revert to a pushed directory Change to an aliased directory To change to an aliased directory, type: goto Example goto dev Register an alias To register a directory alias, type: goto -r or goto --register Example goto -r blog /mnt/external/projects/html/blog or goto --register blog /mnt/external/projects/html/blog Notes goto expands the directories hence you can easily alias your current directory with: goto -r last_release . and it will automatically be aliased to the whole path. Pressing the tab key after the alias name, you have the default directory suggestions by the shell. Unregister an alias To unregister an alias, use: goto -u < ## Things I Don't Know as of 2018 DevFeed: [Things I Don't Know as of 2018]() Original publisher: [Read original article]() Published: 2018-12-28T00:00:00Z Content type: opinion Language: en Sources: [Dan Abramov]() Topics: [Unix](), [Programming](), [Bash](), [Shell](), [Assembly](), [Code]() Tags: [assembly](), [bash](), [beginners](), [code](), [commands](), [junior-developers](), [languages](), [programming](), [scripts](), [shell](), [streams](), [unix]() ### AI overview A personal commentary on the programming topics the author does not know well as of 2018, including Unix commands, Bash, shell scripting, and low-level languages. It argues that experienced developers can acknowledge knowledge gaps without devaluing their expertise. ### Source excerpt We can admit our knowledge gaps without devaluing our expertise. ## Perfect locality and three SystemTap scripts DevFeed: [Perfect locality and three SystemTap scripts]() Original publisher: [Read original article]() Author: Marek Published: 2017-11-05T23:00:00Z Content type: article Language: en Sources: [Marek Majkowski]() Topics: [Linux Kernel](), [Linux](), [Script](), [Cloudflare]() Tags: [2017](), [article](), [blog](), [cloudflare](), [linux](), [linux-kernel](), [scripts]() ### AI overview An article announcement for a Cloudflare blog post about perfect locality and three SystemTap scripts. It describes the post as a continuation exploring the REUSEPORT feature in the Linux kernel. ### Source excerpt Perfect locality and three SystemTap scripts 06 November 2017 I've published an article on the Cloudflare blog: This is a continuation of the previous piece where I try to understand REUSEPORT Linux kernel feature. ## PostgreSQL Conference US, 2016 DevFeed: [PostgreSQL Conference US, 2016]() Original publisher: [Read original article]() Published: 2016-04-17T23:00:00Z Content type: article Language: en Sources: [Dimitri Fontaine]() Topics: [PostgreSQL](), [backups](), [data](), [Script]() Tags: [adoption](), [association](), [automated](), [awareness](), [backup](), [backups](), [community](), [conference](), [data](), [postgresql](), [recovery](), [resources](), [scripts](), [training]() ### AI overview This PostgreSQL Conference US 2016 presentation explains why backups should be tested and why automated recovery is more useful than relying only on backup scripts. Its focus is the ability to recover data when a serious failure occurs. ### Source excerpt You'd better have tested backups explains why you must implement an automated recovery solution rather than merely backup scripts. Noboday cares about backups, as such. What everybody cares about is the actual ability to recover data in case when the worst happens... ## Writing Shell Scripts DevFeed: [Writing Shell Scripts]() Original publisher: [Read original article]() Published: 2016-04-08T21:03:11Z Content type: tutorial Language: en Sources: [Signs of Triviality]() Topics: [Script](), [Shell]() Tags: [avoid](), [pitfalls](), [scripts](), [shell](), [writing]() ### AI overview A set of general guidelines for writing clean, reliable shell scripts and avoiding common pitfalls. ### Source excerpt Writing clean, realiable shell scripts is not rocket science. Here are a few general guidelines to avoid common pitfalls and increase the reliability of your scripts. [Next page]()