nws/nws-site
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

changed branding to nws

Browse source
This commit is contained in:
Nicholas Orlowsky 2024-08-29 15:29:37 -05:00
parent cec9ceff7b
commit 061e74bc1a
Signed by: nickorlow
GPG key ID: 838827D8C4611687
11 changed files with 286 additions and 225 deletions
Download patch file Download diff file Expand all files Collapse all files

36
templates/blogs/11-08-2023-postmortem.html
View file

@ -1,27 +1,27 @@
<h1>SMC Incident Postmortem 11/08/2023</h1>
<h1>NWS Incident Postmortem 11/08/2023</h1>
<p>
On November 8th, 2023 at approximately 09:47 UTC, SMC suffered
On November 8th, 2023 at approximately 09:47 UTC, NWS suffered
a complete outage. This outage resulted in the downtime of all
services hosted on SMC and the downtime of the SMC Management
Engine and the SMC dashboard.
services hosted on NWS and the downtime of the NWS Management
Engine and the NWS dashboard.
</p>
<p>
The incident lasted 38 minutes after which it was automatically
resolved and all services were restored. This is SMC' first
resolved and all services were restored. This is NWS' first
outage event of 2023.
</p>
<h2>Cause</h2>
<p>
SMC utilizes several tactics to ensure uptime. A component of
NWS utilizes several tactics to ensure uptime. A component of
this is load balancing and failover. This service is currently
provided by Cloudflare at the DNS level. Cloudflare sends
health check requests to SMC servers at specified intervals. If
health check requests to NWS servers at specified intervals. If
it detects that one of the servers is down, it will remove the
A record from entry.nws.nickorlow.com for that server (this domain
is where all services on SMC direct their traffic via a
is where all services on NWS direct their traffic via a
CNAME).
</p>
@ -31,34 +31,34 @@
error, but rather an HTTP timeout. This is an indication that the
server may have lost network connectivity. When Cloudflare detected that the
servers were down, it removed their A records from the
entry.nws.nickorlow.com domain. Since SMC Pennsylvania servers
entry.nws.nickorlow.com domain. Since NWS Pennsylvania servers
have been undergoing maintenance since August 2023, this left no
servers able to serve requests routed to entry.nws.nickorlow.com,
resulting in the outage.
</p>
<p>
SMC utilizes UptimeRobot for monitoring the uptime statistics of
services on SMC and SMC servers. This is the source of the
statistics shown on the SMC status page.
NWS utilizes UptimeRobot for monitoring the uptime statistics of
services on NWS and NWS servers. This is the source of the
statistics shown on the NWS status page.
</p>
<p>
UptimeRobot did not detect either of the Texas SMC servers as being
UptimeRobot did not detect either of the Texas NWS servers as being
offline for the duration of the outage. This is odd, as UptimeRobot
and Cloudflare did not agree on the status of SMC servers. Logs
on SMC servers showed that requests from UptimeRobot were being
and Cloudflare did not agree on the status of NWS servers. Logs
on NWS servers showed that requests from UptimeRobot were being
served while no requests from Cloudflare were shown in the logs.
</p>
<p>
No firewall rules existed that could have blocked the healthcheck traffic from Cloudflare
for either of the SMC servers. There was no other configuration
for either of the NWS servers. There was no other configuration
found that would have blocked these requests. As these servers
are on different networks inside different buildings in different
parts of Texas, their networking equipment is entirely separate.
This rules out any failure of networking equipment owned
by SMC. This leads us to believe that the issue may have been
by NWS. This leads us to believe that the issue may have been
caused due to an internet traffic anomaly, although we are currently
unable to confirm that this is the cause of the issue.
</p>
@ -82,7 +82,7 @@
</p>
<p>
SMC will also investigate other methods of failover and load
NWS will also investigate other methods of failover and load
balancing.
</p>

2
templates/blogs/goodbye-nws.html
View file

@ -2,7 +2,7 @@
<p>
<b>
Nick Web Services (NWS) is now Sharpe Mountain Compute (SMC).
Nick Web Services (NWS) is now Nick Web Services (NWS).
</b>
</p>

2
templates/dashboard.html
View file

@ -1,2 +1,2 @@
<h1>Under Construction</h1>
<p>The dashboard isn't ready yet! Use the <a href="https://nws.nickorlow.com/dashboard">old website</a> for now!</p>
<p>The new dashboard isn't ready yet! Nobody but me used it anyways!</p>

10
templates/index.html
View file

@ -1,14 +1,12 @@
{%- import "uptime_table.html" as scope -%}
<div>
<p style="margin-bottom: -9px;"><i>Nick Web Services is now</i></p>
<h1 style="margin-bottom: 0px;margin-top: 0px;">Sharpe Mountain Compute</h1>
<h1 style="margin-bottom: 0px;margin-top: 0px;">Nick Web Services</h1>
<p style="margin-top: 0px;">Pottsville, PA - Philadelphia, PA - Austin, TX</p>
<a href="https://nws.nickorlow.com">[ Old Website (NWS Branded) ]</a>
<p>
Sharpe Mountain Compute is a hosting service based out of the Commonwealth of Pennsylvania
Nick Web Services is a hosting service based out of the Commonwealth of Pennsylvania
and the State of Texas.
We are committed to achieving maximum uptime with better performance and a lower
cost than any of the major cloud services.
@ -23,6 +21,10 @@ We operate four datacenters located across three cities in two states. This infr
all year) for 2023 and 100% uptime for 2024 (YTD).
</p>
<p>
In 2024, YTD we have surpassed both Vercel and Github Pages in total uptime
</p>
<h2>Compare us to our competitors!</h2>
{% call scope::uptime_table(uptime_infos) %}
</div>

22
templates/layout.html
View file

@ -1,7 +1,19 @@
<!DOCTYPE html>
<html lang="en">
<head>
<title>Sharpe Mountain Compute</title>
{% if let Some(title) = page_title %}
<title>{{ title }}</title>
{% else %}
<title>Nick Web Services</title>
{% endif %}
{% if let Some(desc) = page_desc %}
<meta name="{{ desc }}" />
{% else %}
<meta name="Nick Web Services" />
{% endif %}
<link rel="stylesheet" href="/assets/style.css">
<link rel="icon" type="image/x-icon" href="/assets/favicon.ico">
<meta name="viewport" content="width=device-width, initial-scale=1" />
@ -27,16 +39,10 @@
<hr />
<div style="display: flex; justify-content: space-between;">
<div>
<p style="margin-bottom: 0px; margin-top:0px;"><b>Sharpe Mountain Compute</b></p>
<p style="margin-bottom: 0px;margin-top: 0px;">
<small><i>formerly Nick Web Services (NWS)</i></small>
</p>
<p style="margin-bottom: 0px; margin-top:0px;"><b>Nick Web Services</b></p>
<p style="margin-bottom: 0px;margin-top: 0px;">
<small>Copyright &#169; <a href="https://nickorlow.com">Nicholas Orlowsky</a> 2024</small>
</p>
<p style="margin-bottom: 0px;margin-top: 0px;">
<small><i>"We're getting there" - SEPTA</i></small>
</p>
</div>
<div>
<img class="flag-img" src="/assets/flag-images/us.png" title="The United States of America"/>

11
templates/system_status.html
View file

@ -4,17 +4,22 @@
<h2>Datacenter Status</h2>
<p>
The status of each of Sharpe Mountain Compute's 4
The status of each of Nick Web Services's 4
datacenters.
</p>
{% call scope::uptime_table(dctr_uptime_infos) %}
<p>
Notice: Due to leasing issues, the Philadelphia datacenter will be offline until
at least May or August 2025 or it may be discontinued as an NWS location.
</p>
<h2>Service Status</h2>
<p>
The status of services people host on Sharpe Mountain Compute.
The status of services people host on Nick Web Services.
Note that the uptime and performance of services hosted on
Sharpe Mountain Compute may be affected by factors not controlled by us such as
Nick Web Services may be affected by factors not controlled by us such as
bad optimization or buggy software.
</p>