status/config.yml
2020-07-24 19:35:09 +02:00

331 lines
8.7 KiB
YAML
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

############################################################
# +------------------------------------------------------+ #
# | Basic metadata | #
# +------------------------------------------------------+ #
############################################################
# What is your status page called?
# Shows up in the browser bar and meta tags
title: Status Page
# Should posts, which have a publish date
# from the future, be built? Useful for
# sharing upcoming maintenance, etc.
#
# We recommend to keep this at `true`.
# BOOLEAN; `true`, `false`
buildFuture: true
# What language do you want to use for the
# html[lang] definition?
#
# Does not change language of site
# itself.
#
# Default: `en`
# ISO 639-1 defines abbreviations.
#
# See: https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes
# Also: https://www.w3schools.com/tags/ref_language_codes.asp
languageCode: en
# What translation file should cState use?
# You can also define whether missing
# translations should get placeholders.
#
# For defaultContentLanguage—
# Default: `en`
#
# For enableMissingTranslationPlaceholders—
# do not set it to true for languages other
# than English! When tested with Lithuanian,
# it would add unnecesary placeholders to
# values that were intentionally empty.
defaultContentLanguage: en
# What is the hostname or path to the root?
# Where is the site hosted?
#
# ❗ cState & Hugo dont support '/' in
# production use. It will break RSS
# feeds and breaks permalinks since
# version 3. If you are just testing,
# localhost should automatically work.
#
# Example: https://status.example.com/
baseURL: https://status.papey.fr
############################################################
# +------------------------------------------------------+ #
# | Preferences | #
# +------------------------------------------------------+ #
############################################################
params:
# Before setting up your systems, you need
# to first define at least one category.
#
# Categories are shown in the order that
# you define in this config file.
#
# Categories can have a:
# - name
# - description
# - closed boolean `closed: true`
# That would collapse the category upon first load
# and the user can expand by clicking on the category
# (Requires JavaScript.)
# - untitled boolean `untitled: true`
# This would complerely hide the name of the category.
# This is useful, if you do not want to use categories
# because you need to set an 'Uncategorized' category.
# Or it can be used alongside other categories.
#
# For help, see the wiki:
# https://github.com/cstate/cstate/wiki/Customization
categories:
- name: Fediverse
- name: Bots
- name: Services
- name: Blogs
- name: Sites
- name: Servers
closed: true
# These are your systems. Change them to
# change the amount of components.
#
# For help, see the wiki:
# https://github.com/cstate/cstate/wiki/Customization
systems:
# Servers
- name: bilbo
description: scw.papey.fr
category: Servers
- name: balrog
description: scw2.papey.fr
category: Servers
# Bots
- name: gamble-bot (VAL & PL)
description: Gamble-bot instance deployed on Val & PL Twitch channel
category: Bots
- name: gamble-bot (Bandit)
description: Gamble-bot instance deployed on Bandit Twitch channel
category: Bots
- name: trostani (Forgeron)
description: Trostani instance deployed on Forgeron Discord guild
category: Bots
- name: trostani (MtG L&C)
description: Trostani instance deployed on MtG L&C Discord guild
category: Bots
- name: o2m-metalorgie
description: o2m instance deployed on Metalorgie Discord guild
category: Bots
- name: o2m-lebruit
description: o2m instance deployed on Le Bruit Discord guild
category: Bots
- name: o2m-entrepod
description: o2m instance deployed on Entrepod guild
category: Bots
- name: gia-gladii
description: GIA instance deployed on TBGladii Twitch channel
category: Bots
# Services
- name: pbin.papey.fr
description: Private Bin instance
category: Services
- name: bobuncer.papey.fr
description: ZNC IRC Bouncer
category: Services
- name: stdio.space
description: Personnal Gitea instance
category: Services
- name: drone.github.papey.fr
description: Personnal Drone CI instance
category: Services
# Fediverse
- name: metrics.papey.fr
description: Public instance used to present Fediwatcher capabilities
category: Fediverse
- name: palom.be
description: Plume instance focused on novels
category: Fediverse
# Blogs
- name: kancer.club
description: Personnal blog
category: Blogs
- name: blog.papey.fr
description: Tech blog
category: Blogs
# Sites
- name: papey.fr
description: Main homepage
category: Sites
- name: brain.papey.fr
description: A place to store all my notes
category: Sites
# What date format to use?
#
# Hugo formatting docs:
# https://gohugo.io/functions/format/#hugo-date-and-time-templating-reference
#
# Technical: GOLANG/HUGO .Date.Format & dateFormat
#
# dateFormat Default: "January 2, 2006 at 3:04 PM"
# shortDateFormat Default: "15:04 — Jan 2"
dateFormat: January 2, 2006 at 3:04 PM
shortDateFormat: 15:04 — Jan 2
# What header design should we use?
#
# Default: true
# BOOLEAN; `true`, `false`
useLargeHeaderDesign: false
# Should incident history be separated
# like in an archive view?
#
# Note: This WILL disable pagination.
#
# Default: `yearly`
# STRING; `monthly`, `yearly`, `none`
incidentHistoryFormat: "yearly"
# Disable dark mode
#
# If your OS and browser support the
# `prefers-color-scheme` media query,
# cState will automatically switch to
# a darker user interface.
#
# cState uses its built-in colors for
# most of the interface to ensure
# a good user experience.
#
# Default: `false`
# BOOLEAN; `true`, `false`
disableDarkMode: true
# Should we show the logo or the title
# of the status page?
#
# Default: false
# BOOLEAN; `true`, `false`
useLogo: true
# Where is the logo located, if one is
# present at all?
#
# Recommended: png is best used for
# images like logos.
#
# Recommended: png, bmp, jpg, or gif
# for best browser support!
logo: /img/ok.png
# This is the description that is shown
# on the footer and meta tags.
#
# Default: We continuously monitor the status of our services and if there are any interruptions, a note will be posted here.
description: I try to keep things up and running but I have life and server ressources constraints.
# Tabs on homepage
# Uncomment to enable.
#
# Format:
customTabs:
- name: Homepage
link: https://papey.fr
- name: Github
link: https://github.com/papey
- name: Gitea
link: https://git.stdcall.me
# Disable complex server-side
# calculations that may impact
# your build performance
#
# Disables math calculations
# for average downtime on
# systems ("/affected/") pages
#
# Default: false
# BOOLEAN; `true`, `false`
disableComplexCalculations: true
# Incident posts shown
# in one page
#
# NUMERIC; Default: `10`
incidentPostsPerPage: 10
# Colors throughout cState
#
# We recommend using HEX
# (with the # symbol).
#
# Defaults:
#
# brand: "#0a0c0f"
# ok: "#008000"
# disrupted: "#cc4400"
# down: "#e60000"
# notice: "#24478f"
brand: "#ffffff"
ok: "#008000"
disrupted: "#cc4400"
down: "#e60000"
notice: "#24478f"
# If the status page shows that
# there are disruptions or outages
# happening, should it keep the
# brand header color or drop it
# and use the status indication
# colors that were just defined?
#
# Default: `true`
# BOOLEAN; `true`, `false`
alwaysKeepBrandColor: false
# Introduced in v4.0.1 for consistent
# site title text color.
#
# If you do not use the logo, what color
# should the site text color be?
#
# Removing this option will not force
# any site text color. This is likely
# unwanted behavior.
#
# Default: `white`
# STRING; `white`, `black`, or nothing
headerTextColor: white
# These options affect the core of cState.
# Please do not change them if you do not
# know what you are doing.
theme: cstate
preserveTaxonomyNames: true
taxonomies:
affected: affected
outputs:
page:
- html
section:
- html
- rss
home:
- html
- rss
- json
- svg
outputFormats:
svg:
isPlainText: true
mediaType: image/svg+xml