diff options
| author | Bradley Taunt <bt@btxx.org> | 2024-06-08 13:43:37 -0400 |
|---|---|---|
| committer | Bradley Taunt <bt@btxx.org> | 2024-06-08 13:43:37 -0400 |
| commit | 16d28628aca9b2d356de31c319f5e7bc0f5b2b02 (patch) | |
| tree | 11947abb71e38cbe75116871694a44c33d257763 /build/setting-up-free-ssl | |
| parent | dcfb172704f3afb68a30425029ec834be2883274 (diff) | |
Remove incorrectly generated files, fix up markdown articles
Diffstat (limited to 'build/setting-up-free-ssl')
| -rw-r--r-- | build/setting-up-free-ssl/index.html | 11 |
1 files changed, 2 insertions, 9 deletions
diff --git a/build/setting-up-free-ssl/index.html b/build/setting-up-free-ssl/index.html index 24079d6..04d4239 100644 --- a/build/setting-up-free-ssl/index.html +++ b/build/setting-up-free-ssl/index.html @@ -3,11 +3,12 @@ <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> + <meta name="color-scheme" content="dark light"> <link rel="icon" href="data:,"> <title>Setting Up a Free SSL</title> <link href="/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" /> <link href="/rss.xml" type="application/rss+xml" rel="alternate" title="RSS feed for blog posts" /> -<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style> +<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}blockquote{background:rgba(0,0,0,0.1);border-left:4px solid;padding-left:5px;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style> </head> <nav> @@ -16,25 +17,17 @@ <main> <h1 id="setting-up-a-free-ssl">Setting Up a Free SSL</h1> - <p>2018-08-07</p> - <p>I never had to worry about SSL certificates when I originally hosted my blog through Github Pages, but since switching over to Surge.sh I lost my ability to utilize <code>https</code> protocol.</p> - <p>Luckily, Cloudflare offers a very simple way to implement SSL on your website - and it’s free!</p> - <h3 id="ssl-in-3-easy-steps">SSL in 3 easy steps</h3> - <ol> <li>You will need to have a Cloudflare account - you can setup one here. Be sure to select the ‘Free’ pricing plan (unless you want some extras features)</li> <li>Follow the process on updating your nameservers to the proper Cloudflare servers and wait for your domain to update the changes. (This can take up to 24 hours)</li> <li>From the main Cloudflare dashboard navigate to the Crypto tab. Then under the SSL section, select “Flexible” from the dropdown.</li> </ol> - <h3 id="enjoy-your-newly-secure-site">Enjoy your newly secure site</h3> - <p>That’s it! Give it a bit of time and soon your website will support <code>https</code> and best of all it costs you nothing!</p> - <p>I suggest checking out the other interesting features Cloudflare offers while your playing with the dashboard as well. They have a lot of impressive options that can really improve the overall performance of your site / web app.</p> <footer role="contentinfo"> <h2>Menu Navigation</h2> |