Skip to content

Instantly share code, notes, and snippets.

View AlexAtkinson's full-sized avatar

Alex Atkinson AlexAtkinson

  • Toronto
View GitHub Profile
@AlexAtkinson
AlexAtkinson / .bashrc
Last active May 17, 2024 20:46
BASH Aliases
# .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"
@AlexAtkinson
AlexAtkinson / GithubActions.md
Last active May 8, 2024 21:54
GitHub Actions Cheat Sheet

Github Actions Cheat Sheet

Useful References

Dynamically linking Github objects is immensely useful. This table contains some good examples:

Linking Github Objects
@AlexAtkinson
AlexAtkinson / Domain Names, DNS & URLs for DevOps & Friends.md
Last active May 7, 2024 23:01
Domain Names, DNS, and URLs for DevOps & Friends

Domain Names, DNS, and URLs for DevOps & Friends

Table of Contents

@AlexAtkinson
AlexAtkinson / JIRA_Workflows.md
Last active May 2, 2024 15:03
Jira Workflow Examples

Jira Workflow Examples

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.

Structure

First off, DO NOT have workflows that looks like this:

Awful JIRA Workflow (From Atlassian)

@AlexAtkinson
AlexAtkinson / GOACCESS-AWS-ELB.md
Last active April 12, 2024 16:02
Analyzer AWS ELB logs (s3) with goaccess

GoAccess ELB Logs

Setup

Assuming you have an AWS account and a Load Balancer that's logging to S3, the only other things you'll need are:

  • s3 cli
  • goaccess
    • NOTE: Scroll down. You don't have to build from source.
  • goaccessrc file to map the log format. Create the file ~/.goaccessrc
@AlexAtkinson
AlexAtkinson / BASH_Cheatsheet.md
Created April 10, 2024 04:38
BASH Cheatsheet
@AlexAtkinson
AlexAtkinson / Evernote_Alternative.md
Last active April 4, 2024 13:40
Free Evernote Alternative

Evernote Icon Evernote Alternative - Obsidian Evernote Icon

This is my free Evernote alternative.

Tech Stack

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.

@AlexAtkinson
AlexAtkinson / check_failover_dhcp.ps1
Created April 2, 2024 14:08
PS1 From The Past: Nagios DHCP Failover Check
# ----------------------------------------------------------------------
# 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
#
@AlexAtkinson
AlexAtkinson / advanced_markdown.md
Last active March 11, 2024 14:48
Advanced Markdown Usage Cheatsheet

Advanced Markdown Usage Cheatsheet

Github Flavoured Markdown

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.

Examples

@AlexAtkinson
AlexAtkinson / Artifacting.md
Last active March 8, 2024 16:02
A quick DevOps primer on archive artifacting for the SDLC.

Artifacting

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: '\_.'.