- In order to install and configure your Mac, you need to be an Administrator on your computer. Either, contact Paul or Charlie, and they will create an account for you.
#!/usr/bin/python3 | |
import cmd, json, sys, traceback | |
from collections import defaultdict | |
from dataclasses import dataclass | |
from typing import List, Dict | |
import requests | |
# This is part of Suhail's talk on the Infrastructure and Ops Superstream | |
# track for O'Reilly |
#!/usr/bin/env python | |
import argparse | |
def main(command_line=None): | |
parser = argparse.ArgumentParser('Blame Praise app') | |
parser.add_argument( | |
'--debug', | |
action='store_true', | |
help='Print debug info' |
#!/usr/bin/env python | |
import argparse | |
def main(command_line=None): | |
parser = argparse.ArgumentParser('Blame Praise app') | |
parser.add_argument( | |
'--debug', | |
action='store_true', | |
help='Print debug info' |
Recording Rule Example 1 | |
================================ | |
# Aggregating up requests per second that has a path label: | |
- record: instance_path:requests:rate5m | |
expr: rate(requests_total{job="myjob"}[5m]) | |
- record: path:requests:rate5m | |
expr: sum without (instance)(instance_path:requests:rate5m{job="myjob"}) | |
Recording Rule Example 2 |
##How to check file integrity with shasum
For verifying the integrity (but not authenticity of data, i.e., who authored it or the origin of the file) of a file, it is necessary to run a checksum function on the file which will output a value and compare it to a previously stored checksum value; if it matches we can be relatively confident that the file hasn't been tampered with or altered.
You might be asked to verify a file's sha1sum or sha2sum–all this means is calculating and verifying the cryptographic sha1 or sha2 hash value or digest included in the file.
###Various commands and methods for verifying shasum 1 or 2:
Organic:
In terminal run:
When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
const Article = require('../../../../app/models/article');
Those suck for maintenance and they're ugly.
I wanted to build a home lab to get some experience with how Kubernetes works in a multi-architecture, multi-OS environment. Here's the worklog. I'll probably turn it into a blog later :)