chmod +x ./clear_docker_container_logs.shUsage: ../clear_docker_container_logs.sh [-c ""]| { | |
| "variables": { | |
| "name": "coreos-baseimage", | |
| "release": "stable", | |
| "iso_checksum": "", | |
| "iso_checksum_type": "none", | |
| "disk_size": "40000", | |
| "cpus": "4", | |
| "memory": "2048", | |
| "boot_wait": "15s", |
| version: "3" | |
| services: | |
| roach1: | |
| container_name: roach1 | |
| image: cockroachdb/cockroach:v1.1.3 | |
| command: start --insecure | |
| ports: | |
| - "26257:26257" | |
| - "8080:8080" | |
| volumes: |
| 1) Install cloudflared using homebrew: | |
| brew install cloudflare/cloudflare/cloudflared | |
| 2) Create /usr/local/etc/cloudflared/config.yaml, with the following content | |
| proxy-dns: true | |
| proxy-dns-upstream: | |
| - https://1.1.1.1/dns-query | |
| - https://1.0.0.1/dns-query |
How to configure your Mac to use DNS over TLS in five easy steps:
Install Stubby with Homebrew (https://dnsprivacy.org/wiki/display/DP/DNS+Privacy+Daemon+-+Stubby):
brew install stubby
Edit the configuration file:
This is a basic collection of things I do when setting up a new headless ubuntu machine as a webserver. Following the steps below should give you a reasonable secure server with HTTP/2 support (including ALPN in chrome) and the fast NGINX server. I am happy to add things so leave a comment.
After creating the server (droplet on DigitalOcean) log in with
This document details how I setup LE on my server. Firstly, install the client as described on http://letsencrypt.readthedocs.org/en/latest/using.html and make sure you can execute it. I put it in /root/letsencrypt.
As it is not possible to change the ports used for the standalone authenticator and I already have a nginx running on port 80/443, I opted to use the webroot method for each of my domains (note that LE does not issue wildcard certificates by design, so you probably want to get a cert for www.example.com and example.com).
For this, I placed config files into etc/letsencrypt/configs, named after <domain>.conf. The files are simple:
Prerequisites : the letsencrypt CLI tool
This method allows your to generate and renew your Lets Encrypt certificates with 1 command. This is easily automatable to renew each 60 days, as advised.
You need nginx to answer on port 80 on all the domains you want a certificate for. Then you need to serve the challenge used by letsencrypt on /.well-known/acme-challenge.
Then we invoke the letsencrypt command, telling the tool to write the challenge files in the directory we used as a root in the nginx configuration.
I redirect all HTTP requests on HTTPS, so my nginx config looks like :
server {
| # Before Tests | |
| before_script: | |
| - bash ci/docker_install.sh > /dev/null | |
| - composer self-update | |
| - composer install --prefer-dist > /dev/null | |
| - cp .env.gitlab .env | |
| - php artisan key:generate | |
| - php artisan migrate:refresh | |
| # Services |