ayan4m1

Pterodactyl on CentOS 7

# remove wifi card firmwares
yum remove -y iwl*-firmware
yum update -y

# install extra repos and yum-config-manager
yum install -y epel-release yum-utils http://rpms.remirepo.net/enterprise/remi-release-7.rpm
yum-config-manager --disable remi-php54

ayan4m1

Elder Scrolls Online Mods

• MiniMap
• Multi Quest Tracker
• Dustman
• Enchant Maker
• Potion Maker
• Master Merchant
• Loot Summary and Statistics
• Ingredients

ayan4m1

// ==UserScript==
// @name         FastTech Stock Checker
// @namespace    http://phreak.space/
// @version      0.0.2
// @description  Show the stock info on the FastTech search page.
// @author       ayan4m1 <andrew@bulletlogic.com>
// @match        https://www.fasttech.com/search*
// @match        https://www.fasttech.com/category/*
// @require      https://code.jquery.com/jquery-3.3.1.min.js
// @require      https://gist.githubusercontent.com/BrockA/2625891/raw/9c97aa67ff9c5d56be34a55ad6c18a314e5eb548/waitForKeyElements.js

ayan4m1

How to adjust PG/VG ratio

One of the more common questions that comes up when talking about short fills is how to reach a given PG/VG ratio. The short fill bottle has a VG/PG ratio, and you might have your nicotine in PG, VG, or some combination of the two. Let’s work through a few examples to see how you can easily get your desired final ratio.

Example 1: All-PG or all-VG nicotine

We’ll start with the simplest case first. Let’s say you have a 60ml short fill bottle with 45ml of 70/30 VG/PG liquid in it to start. Your nicotine is 100% PG.

In this scenario, you cannot end up with a 70/30 finished product unless you pre-mix your nicotine to also be 70/30 or remove some of the flavor base from the short fill bottle.

ayan4m1

alias git-recent-branches="git for-each-ref --sort=committerdate refs/heads/"
alias git-update-master="git fetch --all && git checkout master && git rebase upstream/master && git push origin master"
alias gfa="git fetch --all"
alias gco="git checkout"

ayan4m1

# generated by Slic3r 1.3.0 on 
bed_shape = -112.5x-72.5,112.5x-72.5,112.5x72.5,-112.5x72.5
before_layer_gcode = T0;\nM109 S[bed_temperature] T0; set bed temperature\nM104 S[temperature_0] T0; set extruder temperature
between_objects_gcode = 
end_gcode = M73 P100 ; end build progress\nG162 X Y F2500; home X and Y axes\nM18; disable all stepper motors\nM109 S0 T0; set bed temperature to 0\nM104 S0 T0; set extruder temperature to 0
extruder_offset = 50x0,0x0
gcode_flavor = sailfish
has_heatbed = 1
host_type = octoprint
layer_gcode = 

ayan4m1

NOTE: Click the "Raw" button in the upper right corner of this pane to get a template you can copy into Reddit. Thanks to /r/DIY_ejuice and /u/ConcreteRiver for commentary and the original format respectively!

Hardware: Describe your build (coil diameter, material, wicking, and resistance), atomizer (model), and device (model and settings) information.

Mixing: Describe everything required to reproduce the liquid you used to test. VG/PG ratio and percentage(s) at a minimum, ideally with notes about handling and/or steeping.

Flavor profile: Describe the quantitative and qualitative aspects of the concentrate. Pay particular attention to the experience that the flavor(s) impart.

Throat hit: Describe quantitatively (a ten point scale is common) and qualitatively (what your throat feels like during and after a hit).

ayan4m1

{
  "[javascript]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode"
  },
  "[yaml]": {
    "editor.defaultFormatter": "redhat.vscode-yaml"
  },
  "[cpp]": {
    "editor.wordBasedSuggestions": false,
    "editor.suggest.insertMode": "replace",

ayan4m1

Redis Desktop Manager for Windows

Yes, it's been done already. No, it's still not particularly easy. You do not need to use either Qt Creator or VS2015.

I am building on information found here, here, and here. Thanks to these folks and the contributors to RDM.

With this document, I sought to "trim the fat" from these other guides and prove that VS2015 itself was not in fact necessary - just its tooling.

Prerequisites

ayan4m1

// ==UserScript==
// @name         Average allocation in Rally
// @namespace    https://rally1.rallydev.com/
// @version      0.1
// @description  Find the average allocation from the Team Status page of Rally
// @author       ayan4m1 <andrew@bulletlogic.com>
// @require      https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
// @require      https://gist.githubusercontent.com/BrockA/2625891/raw/waitForKeyElements.js
// @match        https://rally1.rallydev.com/
// @grant        none