Given that your key has expired.
$ gpg --list-keys
$ gpg --edit-key KEYID
Use the expire command to set a new expire date:
| // https://medium.com/@mlowicki/http-s-proxy-in-golang-in-less-than-100-lines-of-code-6a51c2f2c38c | |
| // #!/usr/bin/env bash | |
| // case `uname -s` in | |
| // Linux*) sslConfig=/etc/ssl/openssl.cnf;; | |
| // Darwin*) sslConfig=/System/Library/OpenSSL/openssl.cnf;; | |
| // esac | |
| // openssl req \ | |
| // -newkey rsa:2048 \ | |
| // -x509 \ |
Situation: Some commit (on master, but not necessarily head of master) has broken things, but it's a big commit and it's not clear what part broke things.
% git checkout master
% git checkout -b bisect-branch
% git revert <offending commit>(test here to make sure reverting fixed your problem)
% git bisect startExample on how to run locally an AWS Lambda via API Gateway using localstack.
Based on...
There are numerous reasons you may need to use multiple SSH keys for accessing GitHub and BitBucket
You may use the same computer for work and personal development and need to separate your work.
When acting as a consultant, it is common to have multiple GitHub and/or BitBucket accounts depending on which client you may be working for.
You may have different projects you're working on where you would like to segregate your access.
| upstream ws_server { | |
| server 127.0.0.1:8080; | |
| } | |
| server { | |
| listen 80; | |
| server_name 10.1.2.225; | |
| location / { | |
| proxy_pass http://ws_server/; |