Skip to content

Instantly share code, notes, and snippets.

Veraticus / skin.yml
Created Jan 13, 2020
Dracua-inspired k9s theme
View skin.yml
foreground: &foreground "#f8f8f2"
background: &background "#282a36"
current_line: &current_line "#44475a"
selection: &selection "#44475a"
comment: &comment "#6272a4"
cyan: &cyan "#8be9fd"
green: &green "#50fa7b"
orange: &orange "#ffb86c"
pink: &pink "#ff79c6"
purple: &purple "#bd93f9"
Veraticus / topbeat.template.json
Last active Aug 17, 2016 — forked from boeboe/topbeat.template.json
Default topbeat template for elastic search
View topbeat.template.json
"template" : "topbeat-*",
"settings" : {
"index" : {
"refresh_interval" : "5s"
"mappings" : {
"_default_" : {
"dynamic_templates" : [ {

Maze of the Blue Medusa

The City

Decadent, dark, huge. It has other names but all its inhabitants just call it "the City." The City is old -- historians have different stories about its founding, and they only agree it was hundreds and hundreds of years ago. It has a nominal government, but actually wealth and magic are the true rulers here. Some of you might live in the City, some of you might be visiting, but all of you are here right now. And you've just worked together to successfully execute the theft of a spectacularly mediocre painting.

The Painting

False Chanterelle

It is called "False Chanterelle." The artist's name has been lost and it is hundreds of years old, though it has been remarkably perserved. It is extremely valuable, shamefully perverse, mildly significant, and not very good. None of those are the reasons you've stolen it.

View gist:00bbedbba3b61d6bdcb2
### Keybase proof
I hereby claim:
* I am Veraticus on github.
* I am veraticus ( on keybase.
* I have a public key whose fingerprint is 5D55 5FAA CEF1 D7BA DDB1 6552 563D D0E7 A31C 5079
To claim this, I am signing this object:
View statuser.rb
#!/usr/bin/env ruby
# Encoding: utf-8
require 'colorize'
require 'oj'
require 'open3'
class Statuser
View gistify237571.json
"name": "JJ Staging",
"chef_environment": "staging",
"run_list": ["roles::mongodb", "roles::redis", "roles::web", "roles::primary"],
"users": {
"chrislopresto": {
"admin": true,
"comment": "Chris LoPresto",
"ssh_keys": [ "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDvGr3dLkrYom0hZ7CCCJb094xisPt7Fj5CQ7YIAqJJhAvERntxaSQmwWZ6aQmbaFmH32gkeATPaYOKvBWj18+jjf38qxKqj2W3eZH1b1yFLhoqF8M/Vm23gHfgyMWdMdcXq89CWscyBO7e8gVpv3to4qv0OTc6LuJWZTfcH2HcXyYBdVvb3JIz7LqsApE4fONhieKhyoHn1DVPprp8gAUdPRyIOa1JQpPydelmkquYXN45sYGy5wrbf1w49+6/uHl6TLwtXrwDOzQflsyIqd3FeNVe/sPYhccWKZibS7T2ngk29mAhC5QwuI7VMq1+qK5WgZwdOfgNiAqW8876Cl4/ chrislopresto@ChrisMacBookProRetina.local" ]
View gistify649653.txt
Hey James,
Thanks for submitting this invoice! We'll get you paid as soon as possible.
I am concerned about the hours you quote, however. You didn't commit code to any branch of any Empirical project from August 15th to September 3rd -- I am sure you were seeing clients and testing API work during that time, but logging 50 hours of time with absolutely no code committed, no documentation created, and no activity in chat makes your hours difficult to verify.
To reflect the work you did seeing the client and doing testing, I'd agree to 10 hours for the period from August 25th to September 3rd.
Given the large volume of your commits and high activity in the client chatroom from September 12th to September 14th, it is readily apparently you worked over the weekend -- and did quite a lot of work as well! Up until I provided my ultimatum to you on September 12th, however, it seemed like your work velocity was roughly the same as it had been on September 4th and 5th. I think it slightly more accurate to say you
View gistify567101.txt
On Sep 15, 2014, at 4:43 PM, Xxxx wrote:
This app is horrible. Only 8 invitations to choose from- already deleted it
Xxxxx Xxxxxx
Enviado con amor de mi iPhone
On Sep 15, 2014, at 5:46 PM, Joel Kraut <> wrote:
View gistify31374.txt
[2014-09-07T21:49:47+00:00] WARN:
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
SSL validation of HTTPS requests is disabled. HTTPS connections are still
encrypted, but chef is not able to detect forged replies or man in the middle
To fix this issue add an entry like this to your configuration file:
# Verify all HTTPS connections (recommended)
You can’t perform that action at this time.