From a50a82f98585fc830aeddef687981a708de87615 Mon Sep 17 00:00:00 2001 From: Nathan Steel Date: Sat, 15 Apr 2023 15:23:04 -0400 Subject: [PATCH] Un-"todo" SoC 'guide' --- guides/guide-to-server-hosting.html | 2 +- guides/vm-seperation-of-concerns.html | 1 - 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/guides/guide-to-server-hosting.html b/guides/guide-to-server-hosting.html index 0e6bb65..ffb5fac 100644 --- a/guides/guide-to-server-hosting.html +++ b/guides/guide-to-server-hosting.html @@ -52,7 +52,7 @@
  • Setup a bridged adapter
  • TODO:Install a virtual machine
  • TODO:Virsh cheatsheet
  • -
  • TODO:Example of Separation of Concerns (SoC)
  • +
  • Example of Separation of Concerns (SoC)
  • Nginx Webserver

    diff --git a/guides/vm-seperation-of-concerns.html b/guides/vm-seperation-of-concerns.html index f9ddef1..e210c46 100644 --- a/guides/vm-seperation-of-concerns.html +++ b/guides/vm-seperation-of-concerns.html @@ -79,7 +79,6 @@

    Why not use a dedicated server for each concern?

    You can! No-one's going to stop you, but unless each concern requires (i.e. needs the dedicated hardware/isolation) its own dedicated server, it's hugely redundant. Again NAS as an example, would be good for a dedicated machine, as it'll be safer if there's no additional chance it goes down due to failure of an unrelated service.

    -

    Virtual Machines are wonderful, as they allow you to make use of more powerful/high spec machines while minimising the wasted usage...