From 1aae4345fb0e84b989e05b73040974f62ffee413 Mon Sep 17 00:00:00 2001 From: Nathan Steel Date: Tue, 16 Aug 2022 15:25:32 +0100 Subject: [PATCH] Style tables - Add colour/styling to table - Change SoC table to be full width --- blog/vm-seperation-of-concerns.html | 22 +++++++++++----------- main.css | 20 ++++++++++++++++++++ 2 files changed, 31 insertions(+), 11 deletions(-) diff --git a/blog/vm-seperation-of-concerns.html b/blog/vm-seperation-of-concerns.html index c48425b..839d4ee 100644 --- a/blog/vm-seperation-of-concerns.html +++ b/blog/vm-seperation-of-concerns.html @@ -38,36 +38,36 @@

Some people will seperate each service into their own VM, however I don't believe this to be efficient (in all cases).

What I recommend is to take your server needs, and break them down into logical blocks, adding each of these blocks to their own VMs. This will keep certain things contained alone, as you want them seperated as much as possible (NAS, etc).

- + - + - + - + - + - - + + - - + + - + - +
Concern/VMServices
Concern/VMServices
Production Web ServerProduction Web Server Nginx PHPCertBotCertBot
Staging Web ServerStaging Web Server Nginx PHP CertBotmariaDBmariaDB
NASOpenMediaVaultNASOpenMediaVault
SQL servermariaDBSQL servermariaDB
Torrent BoxTorrent Box Transmission VPN (to external) Sonarr RadarrOmbiOmbi
diff --git a/main.css b/main.css index 1811aad..b33eb3e 100644 --- a/main.css +++ b/main.css @@ -37,6 +37,26 @@ pre{ padding: 12px; } +/* Table Design */ +table{ + text-align: left; + width: 100%; + border-collapse: collapse; +} +td, th{ + border: 1px solid #222; + padding: 9px 6px; +} +th{ + padding: 12px; + color: white; +} +thead th{ background-color: #191919; } +tbody th{ background-color: #292929; } + +tr:nth-child(even){ background-color: #FEFEFE; } +tr:hover{ background-color: #DEDEDE; } + /* Special Design */ .tag{ font-size: 0.8rem;