This setup is for remote users to connect into an office/home LAN using a VPN (ipsec). This is based on (but not the same as) the strongSwan documentation and this guide: https://raymii.org/s/tutorials/IPSEC_vpn_with_Ubuntu_16.04.html
I used strongSwan 5.5.1.
apt-get install -y strongswan strongswan-pki
Disclaimer: This piece is written anonymously. The names of a few particular companies are mentioned, but as common examples only.
This is a short write-up on things that I wish I'd known and considered before joining a private company (aka startup, aka unicorn in some cases). I'm not trying to make the case that you should never join a private company, but the power imbalance between founder and employee is extreme, and that potential candidates would
No, seriously, don't. You're probably reading this because you've asked what VPN service to use, and this is the answer.
Note: The content in this post does not apply to using VPN for their intended purpose; that is, as a virtual private (internal) network. It only applies to using it as a glorified proxy, which is what every third-party "VPN provider" does.
This document details how I setup LE on my server. Firstly, install the client as described on http://letsencrypt.readthedocs.org/en/latest/using.html and make sure you can execute it. I put it in /root/letsencrypt.
As it is not possible to change the ports used for the standalone authenticator and I already have a nginx running on port 80/443, I opted to use the webroot method for each of my domains (note that LE does not issue wildcard certificates by design, so you probably want to get a cert for www.example.com and example.com).
For this, I placed config files into etc/letsencrypt/configs, named after <domain>.conf. The files are simple:
| pushd . &> /dev/null | |
| cd /tmp | |
| git clone --depth=1 https://github.com/tmikolov/word2vec | |
| cd word2vec | |
| sed -i -e 's/malloc.h/stdlib.h/g' *.c | |
| make | |
| rm *.c* *.txt makefile LICENSE | |
| cp * /usr/local/bin | |
| popd &> /dev/null |
If your system is running slowly, perhaps a process is using too much CPU time and won't let other processes run smoothly. To find out which processes are taking up a lot of CPU time, you can use Apple's Activity Monitor.
The CPU pane shows how processes are affecting CPU (processor) activity:
I've sniffed most of the Tinder API to see how it works. You can use this to create bots (etc) very trivially. Some example python bot code is here -> https://gist.github.com/rtt/5a2e0cfa638c938cca59 (horribly quick and dirty, you've been warned!)
| # encoding: UTF-8 | |
| # Place in config/deploy.rb | |
| # See: https://gist.github.com/joost/9343156 | |
| # Adapted to work with rbenv | |
| namespace :rails do | |
| desc "Open the rails console on primary app server" | |
| task :console do | |
| on roles(:app), primary: true do | |
| rails_env = fetch(:stage) | |
| execute_interactively "#{bundle_cmd} #{current_path}/script/rails console #{rails_env}" |
| #!/bin/bash | |
| # | |
| # git-is-ancestor, by Simon Whitaker | |
| # | |
| # Suggested usage | |
| # | |
| # Store this file somewhere, make it executable, then alias | |
| # it to git is-ancestor by putting this in your $HOME/.gitconfig: | |
| # | |
| # [alias] |
| #! /usr/bin/env ruby | |
| require 'foreman/cli' | |
| require File.expand_path(File.dirname(__FILE__)) + '/foreman_export_systemd.rb' | |
| Foreman::CLI.start |
