diff options
author | Mantas Vilčinskas <hi@mnts.lt> | 2021-04-17 14:18:48 +0300 |
---|---|---|
committer | GitHub <noreply@github.com> | 2021-04-17 14:18:48 +0300 |
commit | 18500f7d6fbef6e31d3a319d3ac209cbd00abb06 (patch) | |
tree | d0d41a7055f2314a92b6f475ece58506280080f1 /exampleSite | |
parent | 48f41399bad4317205026933f018ad2c192d8f08 (diff) | |
parent | 740f8fe924ecda15de73002f648454cf5612142f (diff) |
v5 goes live - #151
Diffstat (limited to 'exampleSite')
-rw-r--r-- | exampleSite/config.yml | 90 | ||||
-rw-r--r-- | exampleSite/content/issues/2019-10-08-testing-new-pipeline.md | 2 | ||||
-rw-r--r-- | exampleSite/content/issues/2021-02-13-maintenance-window.md (renamed from exampleSite/content/issues/2020-06-13-maintenance-window.md) | 13 | ||||
-rw-r--r-- | exampleSite/content/issues/i-testing-cstate-functions.md (renamed from exampleSite/content/issues/2019-10-04-testing-cstate-functions.md) | 2 | ||||
-rw-r--r-- | exampleSite/netlify.toml | 9 | ||||
-rw-r--r-- | exampleSite/vercel.json | 12 |
6 files changed, 109 insertions, 19 deletions
diff --git a/exampleSite/config.yml b/exampleSite/config.yml index 85665f6..1d3149d 100644 --- a/exampleSite/config.yml +++ b/exampleSite/config.yml @@ -89,9 +89,29 @@ defaultContentLanguage: en # version 3. If you are just testing, # localhost should automatically work. # -# Example: https://status.example.com/ +# Example: +# baseUrl: https://status.example.com/ +# +# For testing: +# baseUrl: http://localhost +# +# Broken example: +# baseUrl: / baseURL: https://cstate.mnts.lt +# For features like Last modified, you +# need to use a Git repository. If you +# are using Netlify, you are already +# using Git (with GitHub, GitLab, etc) +# +# So, should Git information be used +# for this website? +# +# We recommend to keep this at `true`. +# BOOLEAN; `true`, `false` +enableGitInfo: true + + ############################################################ # +------------------------------------------------------+ # # | Preferences | # @@ -118,26 +138,30 @@ params: # because you need to set an 'Uncategorized' category. # Or it can be used alongside other categories. # + # These are case sensitive. + # # 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: Empty Category - name: Uncategorized untitled: true # These are your systems. Change them to # change the amount of components. # + # These are case sensitive. + # # For help, see the wiki: # https://github.com/cstate/cstate/wiki/Customization systems: - name: Gateway category: North Coast - name: Backup Gateway - category: East Coast + category: North Coast - name: API description: The guts of the application. category: Uncategorized @@ -154,12 +178,56 @@ params: # # 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 + dateFormat: January 2, 2006 at 3:04 PM UTC + shortDateFormat: 15:04 UTC — Jan 2 + + # Should relative time (x min ago) be used? + # + # IMPORTANT: In the frontmatter, the dates MUST be in + # the UTC time zone for this to work preperly. If you + # use Netlify CMS, all good — the CMS picks UTC time + # by default. Otherwise, there may be very inaccurate + # times if multiple time zones are in your issue files. + # + # FOR YOUR CONSIDERATION: This feature was introduced in + # v5. It may be a breaking change in the case when you + # wish to use relative time but old issues do not have + # UTC time (and therefore are out of sync by ±24 hours) + # + # Read the wiki for more: + # https://github.com/cstate/cstate/wiki/Customization#time + # + # If enabled, will display relative times in places like + # the incident history and summaries instead of using + # dateFormat and shortDateFormat (except for if you use + # the old shortcode). + # + # Default: `true` + # BOOLEAN; `true`, `false` + useRelativeTime: true + + # If enabled, doesn't show seconds on relative times. + # + # With option ON (true): + # "Last checked <1 min ago" + # + # With option OFF (false; default): + # "Last checked 20s ago" + # + # Default: `false` + # BOOLEAN; `true`, `false` + skipSeconds: false + + # Should there be an automatic "Last updated" + # text shown below issues? + # + # Default: `true` + # BOOLEAN; `true`, `false` + enableLastMod: true # What header design should we use? # - # Default: true + # Default: `true` # BOOLEAN; `true`, `false` useLargeHeaderDesign: false @@ -202,7 +270,7 @@ params: # Should we show the logo or the title # of the status page? # - # Default: false + # Default: `false` # BOOLEAN; `true`, `false` useLogo: true @@ -239,7 +307,7 @@ params: # for average downtime on # systems ("/affected/") pages # - # Default: false + # Default: `false` # BOOLEAN; `true`, `false` disableComplexCalculations: false @@ -277,7 +345,7 @@ params: # Default: `true` # BOOLEAN; `true`, `false` alwaysKeepBrandColor: true - + # Introduced in v4.0.1 for consistent # site title text color. # @@ -330,6 +398,10 @@ outputs: - json - rss - svg + term: + - html + - json + - rss outputFormats: svg: diff --git a/exampleSite/content/issues/2019-10-08-testing-new-pipeline.md b/exampleSite/content/issues/2019-10-08-testing-new-pipeline.md index 4f139de..4e9da4f 100644 --- a/exampleSite/content/issues/2019-10-08-testing-new-pipeline.md +++ b/exampleSite/content/issues/2019-10-08-testing-new-pipeline.md @@ -1,7 +1,7 @@ --- title: New Pipeline Rollout date: 2019-10-05 16:24:00 -resolved: false +resolved: true resolvedWhen: 2019-10-05 16:58:00 # Possible severity levels: down, disrupted, notice severity: disrupted diff --git a/exampleSite/content/issues/2020-06-13-maintenance-window.md b/exampleSite/content/issues/2021-02-13-maintenance-window.md index 404ccc4..d6c8b14 100644 --- a/exampleSite/content/issues/2020-06-13-maintenance-window.md +++ b/exampleSite/content/issues/2021-02-13-maintenance-window.md @@ -1,13 +1,14 @@ --- title: Maintenance Window -date: 2020-06-13 15:54:00 -resolved: true -resolvedWhen: 2020-06-13 16:54:00 +#date: 24 Feb 21 12:35 +0200 +date: 2021-02-24 10:35:00 +resolved: false +resolvedWhen: 2021-02-24 12:10:00 # Possible severity levels: down, disrupted, notice -severity: disrupted +severity: notice affected: - - API + - Gateway section: issue --- -*Just began* - We're currently shutting down the network. {{< track "2018-06-13 15:54:00" >}} +*Just began* - We're currently shutting down the network. {{< track "2018-06-13 12:54:00" >}} diff --git a/exampleSite/content/issues/2019-10-04-testing-cstate-functions.md b/exampleSite/content/issues/i-testing-cstate-functions.md index efdf7d7..cf833ac 100644 --- a/exampleSite/content/issues/2019-10-04-testing-cstate-functions.md +++ b/exampleSite/content/issues/i-testing-cstate-functions.md @@ -7,4 +7,4 @@ 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.
\ No newline at end of file +This is essentially a page with a date and title that shows up in the incident history.
\ No newline at end of file diff --git a/exampleSite/netlify.toml b/exampleSite/netlify.toml index d649777..5def631 100644 --- a/exampleSite/netlify.toml +++ b/exampleSite/netlify.toml @@ -4,7 +4,7 @@ functions = "functions" [build.environment] - HUGO_VERSION = "0.48" + HUGO_VERSION = "0.80" [context.production.environment] HUGO_ENV = "production" @@ -14,4 +14,9 @@ command = "hugo -b $DEPLOY_PRIME_URL" [context.branch-deploy] - command = "hugo -b $DEPLOY_PRIME_URL"
\ No newline at end of file + command = "hugo -b $DEPLOY_PRIME_URL" + +[[headers]] + for = "/*.json" + [headers.values] + Access-Control-Allow-Origin = "*"
\ No newline at end of file diff --git a/exampleSite/vercel.json b/exampleSite/vercel.json new file mode 100644 index 0000000..53aef1d --- /dev/null +++ b/exampleSite/vercel.json @@ -0,0 +1,12 @@ +{ + "headers": [ + { + "source": "/(.*)", + "headers": [ + { "key": "Access-Control-Allow-Origin", "value": "*" }, + { "key": "Access-Control-Allow-Methods", "value": "GET,OPTIONS" }, + { "key": "Access-Control-Allow-Headers", "value": "X-CSRF-Token, X-Requested-With, Accept, Accept-Version, Content-Length, Content-MD5, Content-Type, Date, X-Api-Version" } + ] + } + ] +} |