Last update: Mon Nov 18 05:32:46 UTC 2019 by @luckylittle
# USING YUM TO MANAGE SECURITY ERRATA:
Last update: Mon Nov 18 05:32:46 UTC 2019 by @luckylittle
# USING YUM TO MANAGE SECURITY ERRATA:
Disclaimer: I'm not the original author of this sheet, but can't recall where I found it. If you know the author, please let me know so I give the attribution.
The original author seems to be Charles Edge, here's the original content, as pointed out by @percisely.
Note: Since this seems to be helpful to some people, I formatted it to improve readability of the original. Also, note that this is from 2016, many things may have changed, and I don't use macOS anymore, so I probably can't help in case of questions, but maybe someone else can.
After writing up the presentation for MacSysAdmin in Sweden, I decided to go ahead and throw these into a quick cheat sheet for anyone who’d like to have them all in one place. Good luck out there, and s
An Alexa skill may ask a user a Yes/No question and the response handled by request handlers for the built-in AMAZON.YesIntent
and AMAZON.NoIntent
intents. (This is different than dialog confirmation where Yes/No confirmation is handled by the dialog.)
It’s easy to setup these intents and their respective intent handlers. Just like any intent, declare them in the interaction model:
{
"name": "AMAZON.YesIntent",
"samples": []
},
{
module "combined_acm_certificate" { | |
source = "../../modules/acm_certificate_dns_validated_multi_zone" | |
domain_name = "infra.example.com" | |
zone_to_san = { | |
"infra.example.com" = [ | |
"*.infra.example.com", | |
"*.dev.infra.example.com", | |
"*.staging.infra.example.com", | |
"*.production.infra.example.com", |
#!/bin/sh | |
# Generate self signed root CA cert | |
openssl req -nodes -x509 -newkey rsa:2048 -keyout ca.key -out ca.crt -subj "/C=AU/ST=NSW/L=Sydney/O=MongoDB/OU=root/CN=`hostname -f`/[email protected]" | |
# Generate server cert to be signed | |
openssl req -nodes -newkey rsa:2048 -keyout server.key -out server.csr -subj "/C=AU/ST=NSW/L=Sydney/O=MongoDB/OU=server/CN=`hostname -f`/[email protected]" | |
# Sign the server cert |
export PS1="\[\033[36m\]\u\[\033[m\]@\[\033[32m\]\h:\[\033[33;1m\]\w\[\033[m\] git:(\$(git symbolic-ref HEAD 2> /dev/null | sed 's/refs\/heads\///g')) " | |
When executing interactively, bash displays the primary | |
prompt PS1 when it is ready to read a command, and the | |
secondary prompt PS2 when it needs more input to complete | |
a command. Bash allows these prompt strings to be cus | |
tomized by inserting a number of backslash-escaped special | |
characters that are decoded as follows: | |
\a an ASCII bell character (07) | |
\d the date in "Weekday Month Date" format |
// a list of useful queries for profiler analysis. Starting with the most basic. | |
// 2.4 compatible | |
// | |
// output explained: | |
// | |
{ | |
"ts" : ISODate("2012-09-14T16:34:00.010Z"), // date it occurred | |
"op" : "query", // the operation type | |
"ns" : "game.players", // the db and collection |
So in the README.md I put instructions https://github.com/jbelmont/nosql-workshop/blob/master/README.md | |
Please make sure you have installed docker in your machine. | |
Then pull down mongo image with following command: | |
Install my mongo image: | |
docker pull jbelmont/nosql-mongo-image-with-scripts:v1 |
Action | Run Command | Example |
---|---|---|
Connect to local host on default port 27017 | mongo | mongo |
Connect to remote host on specified port | mongo --host --port | mongo --host 192.168.65.23 --port 27020 |
Connect to a database | mongo / | mongo 192.168.65.23/api |
Show current database | db | db |
Select or switch database | use | use api |
Execute a JavaScript file | load() | load (program.js) |