mirror of
https://github.com/linuxserver/cstate.git
synced 2026-02-06 03:58:14 +08:00
removed template issues, added 2 initial (test) issues, initial config changes here
This commit is contained in:
Alex Phillips
parent
ea6bffcc71
commit
4e5ccbb95b
35
config.yml
35
config.yml
@ -43,7 +43,9 @@
|
||||
|
||||
# What is your status page called?
|
||||
# Shows up in the browser bar and meta tags
|
||||
title: Eggsample Status
|
||||
title: "Info :: LinuxServer.io"
|
||||
|
||||
enableCustomHTML: true
|
||||
|
||||
# Should posts, which have a publish date
|
||||
# from the future, be built? Useful for
|
||||
@ -90,7 +92,7 @@ defaultContentLanguage: en
|
||||
# localhost should automatically work.
|
||||
#
|
||||
# Example: https://status.example.com/
|
||||
baseURL: https://cstate.mnts.lt
|
||||
baseURL: https://info.linuxserver.io
|
||||
|
||||
############################################################
|
||||
# +------------------------------------------------------+ #
|
||||
@ -99,6 +101,8 @@ baseURL: https://cstate.mnts.lt
|
||||
############################################################
|
||||
|
||||
params:
|
||||
enableCustomHTML: true
|
||||
|
||||
# Before setting up your systems, you need
|
||||
# to first define at least one category.
|
||||
#
|
||||
@ -121,12 +125,9 @@ params:
|
||||
# For help, see the wiki:
|
||||
# https://github.com/cstate/cstate/wiki/Customization
|
||||
categories:
|
||||
- name: North Coast
|
||||
description: The main servers are located here.
|
||||
closed: true
|
||||
- name: East Coast
|
||||
- name: Uncategorized
|
||||
untitled: true
|
||||
- name: Images
|
||||
description: Information regarding our images
|
||||
- name: Security
|
||||
|
||||
# These are your systems. Change them to
|
||||
# change the amount of components.
|
||||
@ -134,16 +135,10 @@ params:
|
||||
# For help, see the wiki:
|
||||
# https://github.com/cstate/cstate/wiki/Customization
|
||||
systems:
|
||||
- name: Gateway
|
||||
category: North Coast
|
||||
- name: Backup Gateway
|
||||
category: East Coast
|
||||
- name: API
|
||||
description: The guts of the application.
|
||||
category: Uncategorized
|
||||
- name: Media Proxy
|
||||
description: This is the service responsible for serving images, audio, and video. It is reliant on our CDN.
|
||||
category: Uncategorized
|
||||
- name: Deprecations
|
||||
category: Images
|
||||
- name: Vulnerabilities
|
||||
category: Security
|
||||
|
||||
# What date format to use?
|
||||
#
|
||||
@ -161,7 +156,7 @@ params:
|
||||
#
|
||||
# Default: true
|
||||
# BOOLEAN; `true`, `false`
|
||||
useLargeHeaderDesign: false
|
||||
useLargeHeaderDesign: true
|
||||
|
||||
# Should incident history be separated
|
||||
# like in an archive view?
|
||||
@ -277,7 +272,7 @@ params:
|
||||
# Default: `true`
|
||||
# BOOLEAN; `true`, `false`
|
||||
alwaysKeepBrandColor: true
|
||||
|
||||
|
||||
# Introduced in v4.0.1 for consistent
|
||||
# site title text color.
|
||||
#
|
||||
|
||||
@ -1,15 +0,0 @@
|
||||
---
|
||||
title: Issues Sending DMs
|
||||
date: 2017-12-17 16:24:00
|
||||
resolved: true
|
||||
resolvedWhen: 2017-12-17 16:58:00
|
||||
# Possible severity levels: down, disrupted, notice
|
||||
severity: disrupted
|
||||
affected:
|
||||
- API
|
||||
section: issue
|
||||
---
|
||||
|
||||
*Update* - This incident has been resolved.
|
||||
|
||||
*Investigating* - We're aware of an issue affecting sending DMs and viewing online friends. We're online and working on a resolution.
|
||||
@ -1,25 +0,0 @@
|
||||
---
|
||||
title: Unavailable Guilds & Connection Issues
|
||||
date: 2018-04-13 15:54:00
|
||||
resolved: true
|
||||
resolvedWhen: 2018-04-13 17:30:00
|
||||
# Possible severity levels: down, disrupted, notice
|
||||
severity: down
|
||||
affected:
|
||||
- API
|
||||
- Media Proxy
|
||||
section: issue
|
||||
---
|
||||
|
||||
*Post-mortem*
|
||||
|
||||
At approximately 14:01, a Redis instance acting as the primary for a highly-available cluster used by our API services was migrated automatically by Google’s Cloud Platform. This migration caused the node to incorrectly drop offline, forcing the cluster to rebalance and trigger known issues with the way our API instances handle Redis failover. After resolving this partial outage, unnoticed issues on other services caused a cascading failure through Example Chat App’s real time system. These issues caused enough critical impact that Example Chat App’s engineering team was forced to fully restart the service, reconnecting millions of clients over a period of 20 minutes.
|
||||
|
||||
|
||||
---
|
||||
|
||||
*Update* - A fix has been implemented and we are monitoring the results. Looks like this has been fixed. {{< track "2018-04-13 17:30:00" >}}
|
||||
|
||||
*Monitoring* - After hitting the ole reboot button Example Chat App is now recovering. We're going to continue to monitor as everyone reconnects. {{< track "2018-04-13 16:50:00" >}}
|
||||
|
||||
*Investigating* - We're aware of users experiencing unavailable guilds and issues when attempting to connect. We're currently investigating. {{< track "2018-04-13 15:54:00" >}}
|
||||
@ -1,20 +0,0 @@
|
||||
---
|
||||
title: US East Connection Issues
|
||||
date: 2018-04-25 04:13:00
|
||||
resolved: true
|
||||
resolvedWhen: 2018-04-25 04:13:59
|
||||
# Possible severity levels: down, disrupted, notice
|
||||
severity: down
|
||||
affected:
|
||||
- API
|
||||
- Media Proxy
|
||||
- Gateway
|
||||
section: issue
|
||||
---
|
||||
|
||||
*Resolved* -
|
||||
We believe all users experiencing issues have been able to connect at this time. {{< track "2018-05-25 05:54:00" >}}
|
||||
|
||||
*Monitoring* - We believe the connectivity issues are being caused by an isolated ISP issue. We've had reports that swapping to Google DNS servers (see here; https://developers.google.com/speed/public-dns/docs/using) resolves the problem for users. {{< track "2018-05-25 04:40:00" >}}
|
||||
|
||||
*Investigating* - We're aware of reports that users are experiencing connection issues on the East coast of the United States. We're currently investigating these issues, and apologize for any inconvenience it may be causing you. {{< track "2018-05-25 04:13:00" >}}
|
||||
@ -1,13 +0,0 @@
|
||||
---
|
||||
title: Maintenance Window
|
||||
date: 2018-06-13 15:54:00
|
||||
resolved: true
|
||||
resolvedWhen: 2018-06-13 16:54:00
|
||||
# Possible severity levels: down, disrupted, notice
|
||||
severity: disrupted
|
||||
affected:
|
||||
- API
|
||||
section: issue
|
||||
---
|
||||
|
||||
*Just began* - We're currently shutting down the network. {{< track "2018-06-13 15:54:00" >}}
|
||||
@ -1,10 +0,0 @@
|
||||
---
|
||||
title: Testing New cState Features
|
||||
date: 2019-10-04 18:05:00
|
||||
informational: true
|
||||
section: issue
|
||||
---
|
||||
|
||||
There is a new feature in cState version 4 that lets you make what are called _informational_ posts. The main difference is that there will be no _Unresolved_ or _Resolved in under a minute_ text on the pages.
|
||||
|
||||
This is essentially a page with a date and title.
|
||||
@ -1,14 +0,0 @@
|
||||
---
|
||||
title: New Pipeline Rollout
|
||||
date: 2019-10-05 16:24:00
|
||||
resolved: false
|
||||
resolvedWhen: 2019-10-05 16:58:00
|
||||
# Possible severity levels: down, disrupted, notice
|
||||
severity: disrupted
|
||||
affected:
|
||||
- API
|
||||
section: issue
|
||||
---
|
||||
|
||||
There may be disruptions in the rollout.
|
||||
|
||||
@ -1,13 +0,0 @@
|
||||
---
|
||||
title: Maintenance Window
|
||||
date: 2020-06-13 15:54:00
|
||||
resolved: true
|
||||
resolvedWhen: 2020-06-13 16:54:00
|
||||
# Possible severity levels: down, disrupted, notice
|
||||
severity: disrupted
|
||||
affected:
|
||||
- API
|
||||
section: issue
|
||||
---
|
||||
|
||||
*Just began* - We're currently shutting down the network. {{< track "2018-06-13 15:54:00" >}}
|
||||
14
content/issues/2021-02-24-plex-vulnerability.md
Normal file
14
content/issues/2021-02-24-plex-vulnerability.md
Normal file
@ -0,0 +1,14 @@
|
||||
---
|
||||
title: Plex Vulnerability
|
||||
date: 2021-02-24
|
||||
resolved: false
|
||||
# resolvedWhen: 2019-10-05 16:58:00
|
||||
# Possible severity levels: down, disrupted, notice
|
||||
severity: notice
|
||||
affected:
|
||||
- Vulnerabilities
|
||||
- plex
|
||||
section: issue
|
||||
---
|
||||
|
||||
It has come to our attention that some Plex servers are running with a vulnerability: https://forums.plex.tv/t/security-regarding-ssdp-reflection-amplification-ddos/687162
|
||||
12
content/issues/2021-02-24-rutorrent.md
Normal file
12
content/issues/2021-02-24-rutorrent.md
Normal file
@ -0,0 +1,12 @@
|
||||
---
|
||||
title: ruTorrent Deprecated
|
||||
date: 2021-02-24
|
||||
informational: true
|
||||
section: issue
|
||||
affected:
|
||||
- Deprecations
|
||||
- rutorrent
|
||||
- plex
|
||||
---
|
||||
|
||||
Our ruTorrent image is being deprecated. While it will still be available, no new version will be built.
|
||||
Loading…
x
Reference in New Issue
Block a user