- C-a == Ctrl-a
- M-a == Alt-a
:q close
:w write/saves
:wa[!] write/save all windows [force]
:wq write/save and close
I use Namecheap.com as a registrar, and they resale SSL Certs from a number of other companies, including Comodo.
These are the steps I went through to set up an SSL cert.
The following guide will walk you through creating a bitcoin full node within GKE (Google Container Engine).
By default Bitcoin ABC is used, however this can be swapped for any other node quite easily.
If you wish to run another version of bitcoind, just change the image reference in bitcoin-deployment.yml
. There are tons of images available on the Docker Hub. Better yet, build your own. =)
The source for the included image is available at: https://github.com/zquestz/docker-bitcoin
#!/bin/bash | |
# Copyright © 2017 Google Inc. | |
# Licensed under the Apache License, Version 2.0 (the "License"); | |
# you may not use this file except in compliance with the License. | |
# You may obtain a copy of the License at | |
# | |
# http://www.apache.org/licenses/LICENSE-2.0 | |
# | |
# Unless required by applicable law or agreed to in writing, software |
#!/bin/bash | |
# This script gracefully stops resque workers by issuing the USR2 | |
# signal to the resque-pool manager and then waits for the workers | |
# to be paused before exiting. Resque-pool master process relays | |
# the USR2 signal to the children. | |
# | |
# For reference: | |
# (1) https://github.com/nevans/resque-pool#signals | |
# (2) https://github.com/resque/resque/blob/master/lib/resque/worker.rb#L376-L378 |
#!/bin/bash | |
DOCKER_COMPOSE_FILES='docker-compose1.yml,docker-compose2.yml' | |
DOCKER_COMPOSE_UP_MODE=1 #1|0 | |
DOCKER_COMPOSE_UP_LOG_FILE='/tmp/log.txt' | |
DOCKER_COMPOSE_BUILD_OPTIONS="" #any options for `docker-compose build` | |
DOCKER_COMPOSE_UP_OPTIONS="" #any options for `docker-compose up` | |
DOCKER_COMPOSE_RUN_OPTIONS="" #any options for `docker-compose run` | |
TEST_CONTAINERS="application1=/test.sh,application2=/test2.sh" | |
##### get port remover ##### |
--- | |
apiVersion: v1 | |
kind: ConfigMap | |
metadata: | |
name: metricbeat-config | |
namespace: kube-system | |
labels: | |
k8s-app: metricbeat | |
data: | |
metricbeat.yml: |- |
""" | |
Break up a long recording to fit within the Whisper API's limits, with some | |
overlap, so no words are missed, and then feed to OpenAI Whisper API to | |
transcribe it to .txt file. Written by endolith and ChatGPT-4. | |
""" | |
import openai | |
import math | |
import os | |
import subprocess |
Apologies for the snarky title, but there has been a huge amount of discussion around so called "Prompt Engineering" these past few months on all kinds of platforms. Much of it is coming from individuals who are peddling around an awful lot of "Prompting" and very little "Engineering".
Most of these discussions are little more than users finding that writing more creative and complicated prompts can help them solve a task that a more simple prompt was unable to help with. I claim this is not Prompt Engineering. This is not to say that crafting good prompts is not a difficult task, but it does not involve doing any kind of sophisticated modifications to general "template" of a prompt.
Others, who I think do deserve to call themselves "Prompt Engineers" (and an awful lot more than that), have been writing about and utilizing the rich new eco-system