Explore >> Select a destination
|
You are here 
|
blog.dataumbrella.org | ||
| | | | |
www.trickster.dev
|
|
| | | | | Code level discussion of web scraping, gray hat automation, growth hacking and bounty hunting | |
| | | | |
sanctum.geek.nz
|
|
| | | | | [AI summary] The article provides comprehensive guidance on various aspects of shell scripting and system administration. It covers best practices for using cron jobs, managing shell configuration files, customizing the shell prompt, and handling command exit statuses effectively. Key points include setting up cron tasks, organizing shell configuration with .d directories, trimming directory paths in prompts, and improving script readability by avoiding the use of $? directly. | |
| | | | |
citizen428.net
|
|
| | | | | Yesterday I ended up writing an impromptu guide to Bash error handling on a PR, so I decided to polish it a bit and turn it into an actual post. The goal: whenever our release script encounters an error, send a notification to a Slack channel. We won't look into the latter part in this post, as it was handled by some Ruby code using the slack-notifier gem. Instead we'll look into what was necessary to make this work in Bash. | |
| | | | |
www.github.com
|
|
| | | my blog, with astro. Contribute to Krayorn/blog development by creating an account on GitHub. | ||
