twoBoots

## gist:f514c28c584c146fc9d1dbae4591b8e2

      
              1 file
            
          
              0 forks
            
          
                0 comments
              
            
              0 stars
            
          
                twoBoots
                / gist:f514c28c584c146fc9d1dbae4591b8e2
            
            
              Created
              November 13, 2019 00:48
                — forked from CristinaSolana/gist:1885435
            
              
                Keeping a fork up to date
              
          
    1. Clone your fork:

git clone git@github.com:YOUR-USERNAME/YOUR-FORKED-REPO.git

2. Add remote from original repository in your forked repository:

cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream


## letsencrypt_2017.md

      
              1 file
            
          
              0 forks
            
          
                0 comments
              
            
              0 stars
            
          
                twoBoots
                / letsencrypt_2017.md
            
            
              Created
              August 1, 2017 01:52
                — forked from cecilemuller/letsencrypt_2020.md
            
              
                How to setup Let's Encrypt for Nginx on Ubuntu 16.04 (including IPv6, HTTP/2 and A+ SLL rating)
              
          
    How to setup Let's Encrypt for Nginx on Ubuntu 16.04 (including IPv6, HTTP/2 and A+ SLL rating)

There are two main modes to run the Let's Encrypt client (called Certbot):

Standalone: replaces the webserver to respond to ACME challenges
Webroot: needs your webserver to serve challenges from a known folder.

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.