Responding to requests via simple route matching is built in to Go's net/http standard library package. Just register the path prefixes and callbacks you want invoked and then call the ListenAndServe to have the default request handler invoked on each request. For example:
package main
import (
| import logging | |
| from celery.app.defaults import DEFAULT_TASK_LOG_FMT, DEFAULT_PROCESS_LOG_FMT | |
| class CeleryTaskFilter(logging.Filter): | |
| def filter(self, record): | |
| return record.processName.find('Worker') != -1 |
| # Simple No-ip.com Dynamic DNS Updater | |
| # | |
| # By Nathan Giesbrecht (http://nathangiesbrecht.com) | |
| # | |
| # 1) Install binary as described in no-ip.com's source file (assuming results in /usr/local/bin) | |
| # 2) Run sudo /usr/local/bin/noip2 -C to generate configuration file | |
| # 3) Copy this file noip2.service to /etc/systemd/system/ | |
| # 4) Execute `sudo systemctl daemon-reload` | |
| # 5) Execute `sudo systemctl enable noip2` | |
| # 6) Execute `sudo systemctl start noip2` |
Details:
Versions are denoted using a standard triplet of integers: MAJOR.MINOR.PATCH. The basic intent is that MAJOR versions are incompatible, large-scale upgrades of the API. MINOR versions retain source and binary compatibility with older minor versions, and changes in the PATCH level are perfectly compatible, forwards and backwards.
Docker on BTRFS is very buggy and can result in a fully-unusable system, in that it will completely butcher the underlying BTRFS filesystem in such a way that it uses far more disk space than it needs and can get into a state where it cannot even delete any image, requiring one to take drastic actions up to and including reformatting the entire affected BTRFS root file system.
According to the official Docker documentation:
btrfs requires a dedicated block storage device such as a physical disk. This block device must be formatted for Btrfs and mounted into /var/lib/docker/.
In my experience, you will still run into issues even if you use a dedicated partition. No, it seems it requires a standalone
| # https://docs.docker.com/engine/admin/systemd/ | |
| Many Linux distributions use systemd to start the Docker daemon. This document shows a few examples of how to customize Docker’s settings. | |
| Starting the Docker daemon | |
| Once Docker is installed, you will need to start the Docker daemon. | |
| $ sudo systemctl start docker | |
| # or on older distributions, you may need to use | |
| $ sudo service docker start | |
| If you want Docker to start at boot, you should also: |
| # https://docs.docker.com/engine/admin/systemd/ | |
| Many Linux distributions use systemd to start the Docker daemon. This document shows a few examples of how to customize Docker’s settings. | |
| Starting the Docker daemon | |
| Once Docker is installed, you will need to start the Docker daemon. | |
| $ sudo systemctl start docker | |
| # or on older distributions, you may need to use | |
| $ sudo service docker start | |
| If you want Docker to start at boot, you should also: |
| #!/usr/bin/env python | |
| ''' | |
| Simple and functional REST server for Python (2.7) using no dependencies beyond the Python standard library. | |
| Features: | |
| * Map URI patterns using regular expressions | |
| * Map any/all the HTTP VERBS (GET, PUT, DELETE, POST) | |
| * All responses and payloads are converted to/from JSON for you |
| # !/bin/bash | |
| # Step 1. Install pyenv | |
| git clone https://github.com/pyenv/pyenv.git ~/.pyenv | |
| echo 'export PYENV_ROOT="$HOME/.pyenv"' >> ~/.bashrc | |
| echo 'export PATH="$PYENV_ROOT/bin:$PATH"' >> ~/.bashrc | |
| echo -e 'if command -v pyenv 1>/dev/null 2>&1; then\n eval "$(pyenv init -)"\nfi' >> ~/.bashrc | |
| # Step 2. Install missing headers for all the Python modules to be built |
There are two main modes to run the Let's Encrypt client (called Certbot):
Webroot is better because it doesn't need to replace Nginx (to bind to port 80).
In the following, we're setting up mydomain.com.
HTML is served from /var/www/mydomain, and challenges are served from /var/www/letsencrypt.