ottonet

Keybase proof

I hereby claim:

• I am ottonet on github.
• I am ottonet (https://keybase.io/ottonet) on keybase.
• I have a public key whose fingerprint is CDAF 0D1F A581 4319 6F74 5674 0542 D924 8F17 7F10

To claim this, I am signing this object:

ottonet

sudo su
mkdir -p /usr/local/share/n98-magerun/modules 
cd /usr/local/share/n98-magerun/modules
git clone [email protected]:AOEpeople/mpmd.git mpmd
git clone [email protected]:aleron75/Webgriffe_Golive.git Golive
git clone [email protected]:kalenjordan/magerun-addons.git kalenjordan
git clone [email protected]:peterjaap/magerun-addons.git peterjaap
git clone [email protected]:yireo/magerun-addons.git yireo
git clone [email protected]:KamilBalwierz/sxmlsv.git sxmlsv
git clone https://github.com/fruitcakestudio/magerun-modman.git

ottonet

server {
    listen 80;
    server_name ~^((?<subdomain>.*)\.)(?<domain>[^.]+)\.(?<tld>[^.]+)$;
    return 301 $scheme://${domain}.${tld};
}

ottonet

server {
    server_name my.lychee.site;
    listen 80;
    root /var/www/my.lychee.site/htdocs;

    access_log /var/www/my.lychee.site/logs/access.log;
    error_log /var/www/my.lychee.site/logs/error.log;

    index index.php index.html;

ottonet

# Script for automatic setup of SOCKS proxy through SSH connection.
# It automatically teardowns SOCKS configuration before stopping.
# It's supposed to work on Mac OS X 10.6+
#
# Author: Adam Stankiewicz (@sheerun)
#

[[ -n "$1" ]] || { echo "Usage: proxy [email protected]"; exit 1; }

# get service GUID and NAME (like Wi-Fi) to set SOCKS proxy

ottonet

1. create a slack webhook integration - copy the webhook url
2. add following to top of ~/.ssh/config

Host *
  PermitLocalCommand yes

3. add LocalCommand to host entry

Host production.example.com
 User ubuntu

ottonet

location /robots.txt { return 200 "### Autogenerated robots.txt\n
# Sitemap
Sitemap: http://$http_host/sitemap.xml

# Basic Crawler setup. We allow for everything
User-agent: *
Allow: /
Crawl-delay: 10

# Then we start disallowing stuff

ottonet

Prerequisites : the letsencrypt CLI tool

This method allows your to generate and renew your Lets Encrypt certificates with 1 command. This is easily automatable to renew each 60 days, as advised.

You need nginx to answer on port 80 on all the domains you want a certificate for and 443 as well if you redirect everything to this port. Then you need to serve the challenge used by letsencrypt on /.well-known/acme-challenge. Then we invoke the letsencrypt command, telling the tool to write the challenge files in the directory we used as a root in the nginx configuration.

I redirect all HTTP requests on HTTPS, so my nginx config looks like :

server {

ottonet

local ret_status="%(?:%{$fg_bold[green]%}➜ :%{$fg_bold[red]%}➜ %s)"
PROMPT='%{$fg[magenta]%}%n%{$reset_color%} at %{$fg[yellow]%}%m%{$reset_color%} ${ret_status}%{$fg_bold[green]%}%p %{$fg[cyan]%}%c %{$fg_bold[blue]%}$(git_prompt_info)%{$fg_bold[blue]%} % %{$reset_color%}'

ZSH_THEME_GIT_PROMPT_PREFIX="git:(%{$fg[red]%}"
ZSH_THEME_GIT_PROMPT_SUFFIX="%{$reset_color%}"
ZSH_THEME_GIT_PROMPT_DIRTY="%{$fg[blue]%}) %{$fg[yellow]%}✗%{$reset_color%}"
ZSH_THEME_GIT_PROMPT_CLEAN="%{$fg[blue]%})"

ottonet

Verifying that +ottonet is my blockchain ID. https://onename.com/ottonet