I like to browse the deep web to keep myself updated about it's happenings but finding the urls gets annoying. Here are a few interesting links:
$! --- The exception information message set by 'raise'. | |
$@ --- Array of backtrace of the last exception thrown. | |
$& --- The string matched by the last successful match. | |
$` --- The string to the left of the last successful match. | |
$' --- The string to the right of the last successful match. | |
$+ --- The highest group matched by the last successful match. | |
$1 --- The Nth group of the last successful match. May be > 1. | |
$~ --- The information about the last match in the current scope. | |
$= --- The flag for case insensitive, nil by default. | |
$/ --- The input record separator, newline by default. |
f3read "/Volumes/NO NAME" | |
F3 read 7.1 | |
Copyright (C) 2010 Digirati Internet LTDA. | |
This is free software; see the source for copying conditions. | |
SECTORS ok/corrupted/changed/overwritten | |
Validating file 1.h2w ... 2097152/ 0/ 0/ 0 | |
Validating file 2.h2w ... 2097152/ 0/ 0/ 0 | |
Validating file 3.h2w ... 2097152/ 0/ 0/ 0 | |
Validating file 4.h2w ... 2097152/ 0/ 0/ 0 |
$ terraform apply | |
google_container_cluster.primary: Refreshing state... (ID: worklark-cluster) | |
google_compute_firewall.default: Refreshing state... (ID: http-https) | |
google_container_node_pool.primary_pool: Refreshing state... (ID: us-central1-a/worklark-cluster/worklark-node-pool) | |
An execution plan has been generated and is shown below. | |
Resource actions are indicated with the following symbols: | |
+ create | |
Terraform will perform the following actions: |
# Based on https://gist.github.com/jhass/a5ae80d87f18e53e7b56 | |
AllCops: | |
TargetRubyVersion: 2.4 | |
DisplayCopNames: true | |
Include: | |
- '**/Rakefile' | |
- '**/config.ru' | |
Exclude: | |
- '**/Guardfile' |
// Edit these! | |
const accountSid = ''; | |
const authToken = ''; | |
const numbers = []; | |
const message = ""; | |
// script to send the message | |
const client = require('twilio')(accountSid, authToken); |
Verifying my Blockstack ID is secured with the address 1EpVLrG8PnYbXi261WjkidMo1iBswqfniV https://explorer.blockstack.org/address/1EpVLrG8PnYbXi261WjkidMo1iBswqfniV |
I recently got the opportunity to kickstart a project from the ground up. I didn't want to overload my non-technical client with recurring billing for services he wouldn't need. I ended up taking the time to implement a CI/CD environment that deploys to Heroku for free. My client only has to pay for his production Heroku dyno, the rest of the build pipeline is either free or, in the case of the staging environment, running on the free tier.
While I was about to start a new project this weekend, I decided to take a moment to document my process to help myself and you with future projects. I'll outline some of my favorite practices for deployment environments and why I follow them. In this article we'll be hosting the code for a Ruby on Rails application I'm building, for a personal project, at GitLab.com. We'll be using their shared runners for CI/CD and deploying to Heroku in staging and p
require 'droplet_kit' | |
token = '' # paste your token here | |
client = DropletKit::Client.new(access_token: token) | |
# if your droplets are named john-1, john-2, john-3 | |
# @param spelledlike [String] type 'john' | |
# @return [Array<String>] ids of the killed droplets | |
def killem(spelledlike) | |
client.droplets.all.select {|e| e.name.include? spelledlike} |
/interface ethernet | |
set 0 name=WAN1 | |
set 1 name=WAN2 | |
set 2 name=WAN3 | |
set 3 name=WAN4 | |
set 4 name=Local | |
/ip address | |
add address=192.168.0.1/24 interface=Local | |
add address=192.168.1.65/24 interface=WAN1 |