| async function generateV4SignedPolicy() { | |
| // The ID of your GCS bucket | |
| const bucketName = 'your-unique-bucket-name'; | |
| // The ID of your GCS file | |
| const fileName = 'your-file-name'; | |
| const bucket = storage.bucket(bucketName); | |
| const file = bucket.file(fileName); |
| async function generateV4UploadSignedUrl() { | |
| // The ID of your GCS bucket | |
| const bucketName = 'your-unique-bucket-name'; | |
| // The full path of your file inside the GCS bucket, e.g. 'yourFile.jpg' | |
| // or 'folder1/folder2/yourFile.jpg' | |
| const fileName = 'your-file-name'; | |
| // These options will allow temporary uploading of the file with outgoing | |
| // Content-Type: application/octet-stream header. |
| app.get('/', async (req, res) => { | |
| const bucket = storage.bucket(bucketName); | |
| const file = bucket.file(fileName); | |
| const readStream = file.createReadStream(); | |
| //Pipe data from the read-stream into the HTTP response body | |
| readStream.pipe(res); | |
| }); |
| app.get('/', async (req, res) => { | |
| // Get signed URL with action 'read' | |
| const signedUrl = await getReadSignedUrl(bucketName, videoName, 10); | |
| let output = `<video width="400" controls> | |
| <source src=${signedUrl} type="video/mp4"> | |
| </video>` | |
| res.send(output); | |
| }); |
- right-click on the playing video, select Copy link
- find Wistia video ID in the copied link e.g.
wvideo=tra6gsm6rl- alternative: look for e.g.
hashedId=tra6gsm6rlin the page source
- alternative: look for e.g.
- load
http://fast.wistia.net/embed/iframe/+ video ID in your browser - look for
"type":"original"in the page source and copy the URL from the next line e.g."url":"http://embed.wistia.com/deliveries/129720d1762175bcd8e06dcab926ec76ad38ff00.bin"
- alternative: look for
"type":"hd_mp4_video"
Last updated March 13, 2024
This Gist explains how to sign commits using gpg in a step-by-step fashion. Previously, krypt.co was heavily mentioned, but I've only recently learned they were acquired by Akamai and no longer update their previous free products. Those mentions have been removed.
Additionally, 1Password now supports signing Git commits with SSH keys and makes it pretty easy-plus you can easily configure Git Tower to use it for both signing and ssh.
For using a GUI-based GIT tool such as Tower or Github Desktop, follow the steps here for signing your commits with GPG.
The only way I've succeeded so far is to employ SSH.
Assuming you are new to this like me, first I'd like to share with you that your Mac has a SSH config file in a .ssh directory. The config file is where you draw relations of your SSH keys to each GitHub (or Bitbucket) account, and all your SSH keys generated are saved into .ssh directory by default. You can navigate to it by running cd ~/.ssh within your terminal, open the config file with any editor, and it should look something like this:
Host * AddKeysToAgent yes
> UseKeyChain yes
| <html> | |
| <head> | |
| <script type="text/javascript"> | |
| // A CSRF token is required when making post requests in Django | |
| // To be used for making AJAX requests in script.js | |
| window.CSRF_TOKEN = "{{ csrf_token }}"; | |
| </script> | |
| </head> | |
| <body> | |
| <h2>My Blog Posts</h2> |
Step 1: Generate first ssh key Type the following command to generate your first public and private key on a local workstation. Next provide the required input or accept the defaults. Please do not change the filename and directory location.
workstation 1 $ ssh-keygen -t rsa
Finally, copy your public key to your remote server using scp