| package main | |
| import ( | |
| "context" | |
| "fmt" | |
| "io/ioutil" | |
| "os" | |
| "github.com/containerd/containerd/content/local" | |
| "github.com/containerd/containerd/images" |
I screwed up using git ("git checkout --" on the wrong file) and managed to delete the code I had just written... but it was still running in a process in a docker container. Here's how I got it back, using https://pypi.python.org/pypi/pyrasite/ and https://pypi.python.org/pypi/uncompyle6
apt-get update && apt-get install gdb
screen ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty
screen -AmdS docker ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty
screen -r docker
# enter, then disconnect with Ctrl-a d
screen -S docker -p 0 -X stuff $(printf root\\r\\n)
screen -r docker
| ### | |
| ### | |
| ### UPDATE: For Win 11, I recommend using this tool in place of this script: | |
| ### https://christitus.com/windows-tool/ | |
| ### https://github.com/ChrisTitusTech/winutil | |
| ### https://www.youtube.com/watch?v=6UQZ5oQg8XA | |
| ### iwr -useb https://christitus.com/win | iex | |
| ### | |
| ### |
| SELECT blocked_locks.pid AS blocked_pid, | |
| blocked_activity.usename AS blocked_user, | |
| now() - blocked_activity.query_start | |
| AS blocked_duration, | |
| blocking_locks.pid AS blocking_pid, | |
| blocking_activity.usename AS blocking_user, | |
| now() - blocking_activity.query_start | |
| AS blocking_duration, | |
| blocked_activity.query AS blocked_statement, | |
| blocking_activity.query AS blocking_statement |
| Dir.glob("#{ENV['HOME']}/Library/Application Support/Viscosity/OpenVPN/*/config.conf").each do |file| | |
| certificate_files = ['ca', 'cert', 'key', 'tls-auth'] | |
| config_dir = File.dirname(file) | |
| connection_name = nil | |
| new_config = [] | |
| File.read(file).lines.each do |line| | |
| line.strip! | |
| if line.start_with?('#viscosity name') |
| #!/bin/bash -eu | |
| tmpdir=$(mktemp -d) | |
| repodir=$(pwd) | |
| # first try to extract parts from the remote | |
| # e.g. github.com/foo/bar/baz | |
| # -> remote = github.com | |
| remote=$(git ls-remote --get-url origin|awk -F ':' '{print $1}'|awk -F '@' ' {print $2}') | |
| # -> path = foo/bar/baz |
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying
Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
| # APISTATUS | |
| # Purpose goes here | |
| # Key goes here (tested, experimental, nonfunctional, and most importantly the equivalent Go abstracted structs/funcs/go routines/jargon jargon which | |
| # provide the functionality | |
| Account: | |
| POST /api/clear_sessions | |
| POST /api/delete_user | |
| GET /api/me.json |
