fixing a ton more broken or redirected resource links

mattmakai · mattmakai · commit 7193d6904e8d · 2021-06-17T10:33:55.000-04:00
diff --git a/content/pages/05-deployment/03-static-content.markdown b/content/pages/05-deployment/03-static-content.markdown
@@ -21,9 +21,9 @@ Django framework calls these two categories *assets* and *media*.
 ## Content delivery networks
 A content delivery network (CDN) is a third party that stores and serves 
 static files. [Amazon CloudFront](http://aws.amazon.com/cloudfront/),
-[Akamai](http://www.akamai.com/), and 
-[Rackspace Cloud Files](http://www.rackspace.com/cloud/public/files/) 
-are examples of CDNs. The purpose of a CDN is to remove the load of static
+[CloudFlare](https://www.cloudflare.com/), [Fastly](https://www.fastly.com/),
+and [Akamai](https://www.akamai.com/) are examples of CDNs. The purpose of 
+a CDN is to remove the load of static
 file requests from web servers that are handling dynamic web content. For
 example, if you have an nginx server that handles both static files and 
 acts as a front for a Green Unicorn WSGI server on a 512 megabyte 
diff --git a/content/pages/05-deployment/04-cdns.markdown b/content/pages/05-deployment/04-cdns.markdown
@@ -29,10 +29,6 @@ servers to improve web app loading speed.
   [django-storages](https://django-storages.readthedocs.io/en/latest/) library
   to deploy static assets for a [Django](/django.html) application to a CDN.
 
-* [Building your own CDN for Fun and Profit](https://pasztor.at/blog/building-your-own-cdn)
-  is a great high-level overview of how CDNs work and shows you how to
-  create your own, albeit simplified CDN.
-
 * [Do not let your CDN betray you: Use Subresource Integrity](https://hacks.mozilla.org/2015/09/subresource-integrity-in-firefox-43/)
   describes the security implications for CDNs with unexpectedly modified
   content and how Subresource Integrity in modern web browsers can mitigate
diff --git a/content/pages/05-deployment/09-paas.markdown b/content/pages/05-deployment/09-paas.markdown
@@ -156,11 +156,6 @@ running to someone else.
   on Google Cloud and posits what they may be paying to run their
   service.
 
-* [PaaS (false) economics](https://blog.drie.co/paas-false-economics-13f72d87b485)
-  gives some quick back-of-the-envelope calculations on why running your
-  applications on a PaaS is obviously going to appear more expensive if you 
-  do not take the cost of your own software engineers into the equation.
-
 * Two blog posts on using AWS Autoscaling in [Automatic replacement of Autoscaling nodes with equivalent spot instances](https://mcristi.wordpress.com/2016/04/21/my-approach-at-making-aws-ec2-affordable-automatic-replacement-of-autoscaling-nodes-with-equivalent-spot-instances/)
   and
   [Autoscaling nodes: seeing it in action](https://mcristi.wordpress.com/2016/04/27/automatic-replacement-of-autoscaling-nodes-with-equivalent-spot-instances-seeing-it-in-action/)
diff --git a/content/pages/05-deployment/23-gunicorn.markdown b/content/pages/05-deployment/23-gunicorn.markdown
@@ -49,7 +49,7 @@ file with the following contents:
     It exposes the WSGI callable as a module-level variable named ``application``.
 
     For more information on this file, see
-    https://docs.djangoproject.com/en/1.8/howto/deployment/wsgi/
+    https://docs.djangoproject.com/en/3.2/howto/deployment/wsgi/
     """
 
     import os
@@ -115,7 +115,7 @@ perform the request handling. Each worker is independent of the controller.
   screenshots along the way with what to expect while you are configuring
   the deployment server.
 
-* The [Django](https://docs.djangoproject.com/en/1.9/howto/deployment/wsgi/gunicorn/) 
+* The [Django](https://docs.djangoproject.com/en/3.2/howto/deployment/wsgi/gunicorn/)
   and [Flask](http://flask.pocoo.org/docs/latest/deploying/wsgi-standalone/)
   documentation each contain instructions for deploying the respective
   frameworks with Gunicorn.
diff --git a/content/pages/05-deployment/27-continuous-integration.markdown b/content/pages/05-deployment/27-continuous-integration.markdown
@@ -127,11 +127,6 @@ programming language agnostic. Learn more via the following resources or on
   uses well done drawings to show how continuous integration and delivery 
   works for testing and managing data.
 
-* [The real difference between CI and CD](https://fire.ci/blog/the-difference-between-ci-and-cd/)
-  explains what advantages CI provides, what constraints it operates under
-  (such as total build time) to work well, and how that is different from
-  the related but distinct concept of continuous delivery.
-
 * [6 top continuous integration tools](https://opensource.com/business/15/7/six-continuous-integration-tools)
   gives a high level overview of six CI tools from a programming language
   agnostic perspective.
diff --git a/content/pages/05-deployment/28-jenkins.markdown b/content/pages/05-deployment/28-jenkins.markdown
@@ -77,7 +77,3 @@ used to automate building, [testing](/testing.html) and
 * [Automated API testing with Jenkins](https://assertible.com/blog/automated-api-testing-with-jenkins)
   walks through how to use Jenkins to tests your 
   [API](/application-programming-interfaces.html) upon each deployment.
-
-* [Continuous Delivery with Jenkins and Rollbar](https://rollbar.com/blog/continuous-delivery-with-jenkins/)
-  is a tutorial on using Jenkins for continuous integration paired with
-  [Rollbar](/rollbar.html) for tracking deployments and errors.
diff --git a/content/pages/05-deployment/32-configuration-management.markdown b/content/pages/05-deployment/32-configuration-management.markdown
@@ -59,17 +59,6 @@ management and application deployment tool built in Python.
   is a fantastically detailed introduction on using Ansible to set up
   servers.
 
-* [Ansible Text Message Notifications with Twilio SMS](https://www.twilio.com/blog/2014/05/ansible-text-messages-notifications-with-twilio-sms.html)
-  is my blog post with a detailed example for using the Twilio module in
-  core Ansible 1.6+.
-
-* [Python for Configuration Management with Ansible slides](http://www.insom.me.uk/post/pycon-talk.html) 
-from PyCon UK 2013
-
-* [First Steps with Ansible](http://labs.qandidate.com/blog/2013/11/15/first-steps-with-ansible/)
-
-* [Red Badger on Ansible](http://red-badger.com/blog/2013/06/29/ansible/)
-
 * [Getting Started with Ansible](http://lowendbox.com/blog/getting-started-with-ansible/)
 
 * [An introduction to Ansible](https://davidwinter.me/introduction-to-ansible/)
diff --git a/content/pages/05-deployment/38-serverless.markdown b/content/pages/05-deployment/38-serverless.markdown
@@ -188,21 +188,10 @@ have varying degrees of support for Python. AWS Lambda has
 production-ready support for Python 2 and 3.7, while Azure and Google Cloud
 have "beta" support with unclear production-worthiness. The following
 resources are some comparison articles to help you in your decision-making
-process for which platform to learn.
-
-* [Serverless at scale](https://blog.binaris.com/serverless-at-scale/)
-  compares the "Big 3" AWS, Azure and Google Cloud in serverless performance.
-  The author provides some nice data around average response times and 
-  outliers.
-
-* [Serverless hosting comparison](https://headmelted.com/serverless-showdown-4a771ca561d2)
-  is a broad overview of documentation, community, pricing and other
-  notes for the major platforms as well as IBM OpenWhisk and 
-  the [Fission.io](https://fission.io/) project.
-
-* [Microsoft Azure Functions vs. Google Cloud Functions vs. AWS Lambda](https://cloudacademy.com/blog/microsoft-azure-functions-vs-google-cloud-functions-fight-for-serverless-cloud-domination-continues/)
-  presents an overview of Azure Functions and how they compare to
-  Google Cloud Functions and AWS Lambda.
+process for which platform to learn. 
+[Microsoft Azure Functions vs. Google Cloud Functions vs. AWS Lambda](https://cloudacademy.com/blog/microsoft-azure-functions-vs-google-cloud-functions-fight-for-serverless-cloud-domination-continues/)
+presents an overview of Azure Functions and how they compare to
+Google Cloud Functions and AWS Lambda.
 
 
 ### Serverless vendor lock-in?
