You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once you've made changes and committed them in your fork, preferably on a nicely named branch with descriptive commit messages, you can move on to [Creating a Pull Request](#creating-a-pull-request).
12
14
@@ -32,9 +34,9 @@ In [`nginx-config/directive/bubbly_rock-hard-ssl.conf`](https://github.com/eusta
Various headers are delivered from various configuration files. This list should help source any undesired headers you see being sent. Some headers can be sent from multiple locations.
Copy file name to clipboardExpand all lines: README.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@
8
8
9
9
If you want an instant A+ score on Qualys [SSL Labs](https://www.ssllabs.com/ssltest/analyze.html?d=lewisgoddard.me.uk) and A score on [SecurityHeaders.io](https://securityheaders.io/?q=lewisgoddard.me.uk&followRedirects=on), then this is what you'll need to do. You won't need any familiarity with [Certbot](https://github.com/certbot/certbot), [Let's Encrypt](https://letsencrypt.org/), the ACME spec, or SSL in general, just basic Nginx configuration.
10
10
11
-
**1. Install Certbot and Clone Bubbly**
11
+
## 1. Install Certbot and Clone Bubbly
12
12
13
13
We'll start off by cloning the project into the home folder with git.
14
14
@@ -18,7 +18,7 @@ sudo apt install git certbot &&
18
18
git clone https://github.com/eustasy/Bubbly
19
19
```
20
20
21
-
**2. Generate Statics**
21
+
## 2. Generate Statics
22
22
23
23
Generate the static keys once per server.
24
24
@@ -30,15 +30,15 @@ As it will warn, this might take a while.
30
30
31
31
Have a seat.
32
32
33
-
**3. Copy config blocks**
33
+
## 3. Copy config blocks
34
34
35
35
When you've gone and made something in the 15 minutes that could well take, or you've just set up a new SSH session, copy the Nginx configuration over to the Nginx area.
36
36
37
37
```bash
38
38
~/Bubbly/bubbly_copy-configs.sh
39
39
```
40
40
41
-
**4. Configure & Enable Verification**
41
+
## 4. Configure & Enable Verification
42
42
43
43
Copy the verification site template and replace the instances of `example.com` in the file with your actual domain name.
Alternatively, you can simply add `include location/bubbly_well-known-passthrough.conf;` to an existing site you want to continue working while we upgrade.
58
58
59
-
60
-
**5. Fetch Certificates**
59
+
## 5. Fetch Certificates
61
60
62
61
Fetch your certificates like this:
63
62
@@ -69,7 +68,7 @@ It will ask for the root password, and an email address, so hang around, it shou
69
68
70
69
Certbot will set up a systemd timer that runs `certbot renew` automatically twice a day. The `--deploy-hook` passed by the script is stored in `/etc/letsencrypt/renewal/example.com.conf`, so Nginx will be reloaded automatically after each successful renewal — no cron job or manual renewal needed.
71
70
72
-
**6. Start using the Certificates**
71
+
## 6. Start using the Certificates
73
72
74
73
Copy the live site template alongside the verify config you already have. You'll need to more carefully review the `[OPTION]`s in this file, as you'll also need to change the certificate location to match the domain name you requested. Consider taking a look at the `[OPTION]`s and `[WARNING]`s in other linked config files.
0 commit comments