Dynamically linking Github objects is immensely useful. This table contains some good examples:
Linking Github Objects# .bashrc QoL adds. | |
# Ultra lazy... | |
alias urc='source ~/.bashrc' | |
# Save history immediately | |
shopt -s histappend | |
#PROMPT_COMMAND="history -a;$PROMPT_COMMAND" | |
# https://askubuntu.com/questions/67283/is-it-possible-to-make-writing-to-bash-history-immediate | |
export PROMPT_COMMAND="history -a; history -c; history -r; $PROMPT_COMMAND" |
This GIST is here simply to demonstrate some workflows I've found helpful in guaranteeing a well-developed backlog for iteration teams. That said, workflows can be as simple or as complex as you need for your organization/project. At scale though, it's highly desirable to have a backlog as beautifully maintained as your products as their qualities are interdependent. And you'll see this point surface in retrospectives/feedback over time.
First off, DO NOT have workflows that looks like this:
🗒️ +(...) is part of extended globs, you need to enable them explicitly with
shopt -s extglob
🗒️ expansions support glob -NOT- regex
https://www.gnu.org/savannah-checkouts/gnu/bash/manual/bash.html#Shell-Expansions https://www.gnu.org/savannah-checkouts/gnu/bash/manual/bash.html#Pattern-Matching
This is my free Evernote alternative.
There are three components of this solution: the note taking app, cloud-sync utility, and the optional cloud storage.
NOTE: If you don't need more than 2GB of cloud storage, you can get away with simply putting the vault in Dropbox and accessing from all your devices. NO NEED FOR SYNCTHING. Otherwise, read on.
# ---------------------------------------------------------------------- | |
# File: check_failover_dhcp.ps1 | |
# Description: NRPE Nagios Check for Windows Server 2012 DHCP Failover Servers | |
# https://exchange.nagios.org/directory/Plugins/Network-Protocols/DHCP-and-BOOTP/Windows-2012-DHCP-Failover-and-Scope-Health-Check/details | |
# | |
# Checks: Failover State | |
# Failover Mode | |
# Scope State of Each Scope | |
# Scope Statistics (PercentInUse) of Each Scope | |
# |
Github markdown is not strictly markdown (though, what is...?), and is referred to as Github Flavoured Markdown, making previewing .md files necessary to ensure you're getting what you intend.
Use the GitHub Markdown Preview extension.
RELATED: Versioning.md
This primer on artifacting demonstrates how to package files as zip and tar.gz, leverage a .artifactignore file similar to .gitignore, and generate and use a checksum file.
Artifacting is the process of packaging a project for distribution and/or release, and is essential to the SDLC as it mitigates many risks in both producing and consuming software products. Aside from archives, there are binaries and other language specific formats and frameworks that have their own packaging methods, but they are outside of the scope of this document. If you're interested, the serverless packaging mechanism is a good demonstration of some of the same concpets discussed here.
Generally artifacts should conform to a standard naming scheme such as: '\_.'.