$ docker compose -f acmesh.yaml up -d
ACME_HOME_DIR=./acme.sh
# API Key 可以在以下頁面建立: | |
# https://max.maicoin.com/api_tokens/new | |
# | |
MAX_API_KEY= | |
MAX_API_SECRET= |
#!/bin/sh | |
# Author: https://github.com/AlexCzar | |
# License: Apache 2.0 | |
# This script can be used as a launcher for alacritty-inside-tabbed | |
# It monitors window manager events and when detects that tabbed has | |
# lost focus, script will minimize tabbed. | |
# If alacritty-in-tabbed is not running, it will launch it, if it is | |
# running but isn't focused, script will give it focus, if it is running | |
# and is focused, script will minimize it. |
package main | |
import ( | |
"github.com/prometheus/client_golang/prometheus" | |
"github.com/prometheus/client_golang/prometheus/promhttp" | |
"log" | |
"math/rand" | |
"net/http" | |
"time" |
Let's start by creating entry for server in docker-compose.yaml
:
version: '2'
# version 2 of docker-compose is not "old" version, it's the actual version,
# see below for explanation:
# https://stackoverflow.com/a/53636006/961092
services:
pre required SSH access | |
## Download and install acme.sh | |
acme.sh is a full implementation of a LetsEncrypt client but that doesn't depend on Python/pip/virtualenv/etc, and that doesn't require root -- exactly what we need, since we don't have root an a shared GoDaddy server, and we can't install new software outside of our home directory. | |
`curl https://get.acme.sh | sh` | |
Now log out and SSH back in so acme.sh's install is complete in every way (include the Bash alias). | |
##Get GoDaddy API Key | |
Visit `https://developer.godaddy.com/keys/` |
Docker can be confusing to PC and Windows users because many tutorials on that topic assume you're using a Linux machine.
As a Linux user, you learn that Volumes are stored in a part of the host filesystem managed by Docker, and that is /var/lib/docker/volumes
. When you're running Docker on a Windows or Mac OS machine, you will read the same documentation and instructions but feel frustrated as that path don't exist on your system. This simple note is my answer to that.
When you use Docker on a Windows PC, you're typically doing one of these two things:
The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
let regex; | |
/* matching a specific string */ | |
regex = /hello/; // looks for the string between the forward slashes (case-sensitive)... matches "hello", "hello123", "123hello123", "123hello"; doesn't match for "hell0", "Hello" | |
regex = /hello/i; // looks for the string between the forward slashes (case-insensitive)... matches "hello", "HelLo", "123HelLO" | |
regex = /hello/g; // looks for multiple occurrences of string between the forward slashes... | |
/* wildcards */ | |
regex = /h.llo/; // the "." matches any one character other than a new line character... matches "hello", "hallo" but not "h\nllo" | |
regex = /h.*llo/; // the "*" matches any character(s) zero or more times... matches "hello", "heeeeeello", "hllo", "hwarwareallo" |