A Marvelous Open Source Status Page System

Overview

⚠️ WARNING: This the branch for the next planned version (v1): it's unstable and under active development. For the latest stable version, go to the master branch

Travis version License

Support us

Statusfy

Statusfy

A marvelous Open Source Status Page system

Statusfy is a Status Page System, easy to use and completely Open Source. You can easily create a fast System, Static Generated, and easily deploy it to a variety of hosting services.

A Statusfy site is a Web Application, created on top of Eleventy, Netlify CMS and Tailwind CSS. It is used Eleventy to make a quick and useful abstraction of the system generation, Netlify CMS to dynamically define the System Editor, and Tailwind CSS to rapidly define the default themes.

Features

  • Systems Definition
  • Incidents Reports
  • Progressive Web App (PWA) Support
  • Google Analytics Integration
  • Multi-language support
  • A default theme with:
    • Responsive layout
    • Easy Customization
    • Beautiful Design
  • SEO Friendly
  • Hosting flexibility

Sponsoring

I love Open Source Projects, I use them every day and Statusfy is one of my contribution to the community. Statusfy is created and maintained by me, a Full Stack Developer, but my resources are limited. If you want to support my work and help me to continue developing this Amazing Project, please donate, I will appreciate it ❤️ .

This is how we use the donations:

  • Allow the core team to work on Statusfy.
  • Support external projects in the ecosystem.
  • Cover any other expense.
  • Thank contributors if they invested a large amount of time in contributing.

Partners

Become a Partner and get your logo with a link to your site on the README on Github, every page of https://marquez.co/docs/statusfy and, the project home page (https://marquez.co/statusfy) and each blog post related to Statusfy. [Become a Partner]

Sponsors

Become a Sponsor and get your logo on the README on Github with a link to your site. [Become a Sponsor]

Backers

Support me with a monthly donation and help me continue my activities. It means a lot to me ❤️ . [Become a Backer]

Getting started

It’s pretty easy to get started with Statusfy. Install it globally with npm:

Make sure you have npx installed (npx is shipped by default since npm 5.2.0)

# change the working directory
cd existing_folder

# run the initialization command
npx @statusfy/cli init

# and install your local dependencies
npm install  # OR yarn install

Create a new incident with this command:

npm run new-incident # OR yarn new-incident

and launch the development server with:

npm run start # OR yarn start

You can later also generate the final Website with:

npm run generate # OR yarn generate

More information in the Documentation.

Development

⚠️ You must at least use node >= 10.

# install dependencies
yarn
# serves Statusfy's own demo
yarn demo:dev 
# make sure your code change passes the test
yarn test

More information in the Contributing Guide. You can also build and run Statusfy in a free online workspace using Gitpod:

Open in Gitpod

Demo

A Demo application is at https://statusfy.marquez.co.

Documentation & Community Support

Professional Support

This project is sponsored by me, a Full Stack Developers. If you require Professional Assistance on your project(s), please contact me at https://marquez.co.

Contributing

Please make sure to read the Contributing Guide before making a pull request.

Code of Conduct

Everyone participating in this project is expected to agree to abide by the Code of Conduct.

License

Code released under the Apache License 2.0.

Issues
  • Create official Docker image

    Create official Docker image

    Feature request

    • [x] I confirm that this is a feature request rather than a question.

    What problem does this feature solve?

    The use of Docker greatly simplifies the process of deploying and updating web applications. Having an official Docker image would allow people to seamlessly integrate Statusfy into their software stack.

    What does the proposed API look like?

    N/A

    How should this be implemented in your opinion?

    I think it would be best if you set up automated builds so that you don't have to manually push the Docker image every time you make a change.

    Are you willing to work on this yourself?**

    Yes.

    enhancement 
    opened by whalehub 23
  • feat: Run in Docker Container (Best Practices) Documentation

    feat: Run in Docker Container (Best Practices) Documentation

    Feature request

    Create a section in the documentation how to best run in a Docker Container Environment.

    What problem does this feature solve?

    Container will be the "only" way to run applications in the future. It seems the current statusfy commands are however not suited for this:

    At least to my current knowledge, i would implement containerizing by mounting the "content" folder with the incidents to the host. So I can simply create and modify the files/incidents via a script or manually. So I would not be using the "new-incident" command (as this command is not available outside the container). This would however then require "npx statusfy build & npx statusfuy start" , in other words a reloading in the contianer. But this very hard to implement properly and leads to downtimes. Currently there is no "reloading" command (that could be triggered via a cronjob or that does the reloading itself).

    I am a newbie with nuxt/vue: One solution for automatic reloading seems to run the app with "npx statusfy dev" in the container. What security implications and leakages does this have? Can someone please comment on this if this is the way to go and also include a short paragraph about best practices in the documentation about containerized usage. Thanks! And thanks for statusfy, really love it!

    wontfix 
    opened by ichtestemalwieder 12
  • Incident displayed under incorrect date

    Incident displayed under incorrect date

    • [x] I confirm that this is a issue rather than a question.

    Bug report

    Version

    0.3.0-alpha.4

    Steps to reproduce

    1. Create an incident with the date 2019-02-25T20:00:00.000Z on a server with timezone UTC.
    2. View the Statusfy page on a computer with the timezone set to GMT+5 or greater (e.g. Pacific/Auckland)

    What is expected?

    The incident showing up under the Feb 26, 2019 heading.

    What is actually happening?

    The incident showing up under the Feb 25, 2019 heading.

    Screenshot of bug

    Other relevant information

    Note that the date itself of the incident is correctly shown in the current timezone, just not the location of the incident under the headings.

    • Your OS: macOS 10.14.3
    • Node.js version: 8.10.0
    • Browser version: Version 72.0.3626.109 (Official Build) (64-bit)
    • Browser timezone: Pacific/Auckland
    • Server timezone: UTC
    • Is this a global or local install? Local
    • Which package manager did you use for the install? NPM
    bug pinned 
    opened by DanielGibbsNZ 12
  • Comments on the Scheduled maintenance feature in 0.2.1

    Comments on the Scheduled maintenance feature in 0.2.1

    Feature request

    I finally managed to update to 0.2.1 (had to force the version on npm) and added a couple of scheduled maintenance items for testing. I have the following comments:

    • [x] I confirm that this is a feature request rather than a question.

    How should this be implemented in your opinion?

    1 - Adding a scheduled maintenance item is quick and simple, good work 2 - As previously mentioned, I'd rather have the "Scheduled maintenance" section displayed above the current status section. Reason is simple: as soon as you have more than a few systems listed, the "Scheduled maintenance" section requires scrolling and will be missed by many

    image

    3 - The Date/Time at which the Scheduled maintenance will happen is not visible enough. It should be made very large/visible, at least as much as the maintenance title 4 - I added some text to the event but that text is not visible anywhere:

    ---
    title: Server upgrade
    date: '2018-12-13T14:34:46.338Z'
    scheduled: '2018-12-15T12:00:00.000Z'
    duration: 30
    severity: under-maintenance
    affectedsystems:
      - site
      - helpdesk
      - documentation
    resolved: false
    ---
    
    Our hosting company has required that our main server is rebooted for software updates.
    
    ::: update under-maintenance | 2018-12-13T14:45:46.338Z
    We have been informed that the expected duration of the maintenance is now 60mn.
    :::
    
    <!--- language code: en -->
    

    The text "Our hosting company..." and the update text are not visible anywhere. You can't even click through to get to the details of the event like on regular incidents - although I would not want that either, that's not very handy. See point #5 below

    5 - I would suggest each incident, whether standard or scheduled maintenance, displays the title, then the first 2or 3 lines of description and then a button can be clicked to expand in place (don't go to another page) to view the full text content of the incident including description and any subsequent update.

    Looking forward to your comments, thanks for the update.

    Best regards

    Are you willing to work on this yourself?**

    enhancement pinned 
    opened by weeblr 12
  • Add 'delete-incident' and 'edit-incident' command

    Add 'delete-incident' and 'edit-incident' command

    Feature request

    • [x] I confirm that this is a feature request rather than a question.

    What problem does this feature solve?

    • You don't have to delete the incident file for each language manually. Currently you have to delete every file for each language by hand. This is pretty annoying and confusing if you use more than one language.

    • You don't have to edit the incident file for each language manually. Small example: You create a new incident and you are using 4 languages (which means you have 4 files). Now you want to change the value of 'resolved' because the incident was solved. Currently you have to open and edit every file for each language and change the value by hand.

    (The new commands are especially useful if you use more than one language!)

    What does the proposed API look like?

    How should this be implemented in your opinion?

    Add 2 new commands:

    npm run delete-incident # OR yarn delete-incident
    

    and

    npm run edit-incident # OR yarn edit-incident
    

    -- After running one of those commands you will be asked a few questions. Examples: delete-incident:

    • Please select the incident. (enter id?) Or select an incident from this list: (list of available incidents)
    • Do you really want to delete this incident? (yes/no)

    edit-incident:

    • Please select the incident. (enter id?) Or select an incident from this list: (list of available incidents)
    • Which value do you want to change?
    • ...

    Are you willing to work on this yourself?**

    No.

    enhancement 
    opened by dennishzg 11
  • Update consola in group packages to the latest version 🚀

    Update consola in group packages to the latest version 🚀

    The dependency consola was updated from 1.4.4 to 2.0.0.

    This version is not covered by your current version range.

    If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.


    Release Notes for Koala wakes up! (v2.0.0)

    This is a major rewrite of consola with 49 changed files, 5,250 additions and 1,558 deletions!

    Hope you enjoy the new release and waiting for improvement suggestions. 💖

    Semi-Braking

    • Removed some extra types like done and ready and added a new silent level. See types.js.
    • The log methods signature is improved. Either a logObj or a series of arguments which will be directly passed to util.format like the normal console. ((logObject)(args...)`)
    • Use badge style for the fancy reporter when log level is below 2 (error, fatal and warning)
    • add, remove and withScope methods renamed to addReporter, removeReporter and withTag with aliases for backward compatibility (Thanks to @aldarund for early testing)

    Improvements

    • Significant improvements for both Fancy and Basic reporters
    • Better stack trace highlights and formatting
    • Tree-shakable ESM (When using dist/* files) (Thanks to @clarkdo)
    • Significant install size improvements by removing lodash dependency (Thanks to @timneutkens)
    • Significant performance improvements by writing to the streams once for each log (Thanks to @pimlie)

    New features

    • Browser support
    • Support pause/resume
    • Support wrapping consola and stdin/stdout to make everything fancy.
    • Log level can be adjusted using CONSOLA_LEVEL environment variable.
    Commits

    The new version differs by 142 commits.

    There are 142 commits in total.

    See the full diff

    FAQ and help

    There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


    Your Greenkeeper bot :palm_tree:

    greenkeeper 
    opened by greenkeeper[bot] 10
  • Missing scheduled maintenance handling

    Missing scheduled maintenance handling

    Feature request

    • [x] I confirm that this is a feature request rather than a question.

    Scheduled maintenance: I'm just giving a test run to your project. That went fine but I could not find any way to handle scheduled maintenance, ie have "incidents" be in the future but still be listed in some way, independently from the past incidents history.

    Likewise, there's no way to easily display one or more messages to visitors, although it's not a requirement as scheduled maintenance is.

    What problem does this feature solve?

    A status page cannot really be used if you can't announce upcoming maintenance windows, their expected start time duration and update them when maintenance is happening.

    What does the proposed API look like?

    How should this be implemented in your opinion?

    Are you willing to work on this yourself?**

    enhancement 
    opened by weeblr 10
  • An in-range update of eslint-plugin-jest is breaking the build 🚨

    An in-range update of eslint-plugin-jest is breaking the build 🚨

    The devDependency eslint-plugin-jest was updated from 22.5.1 to 22.6.0.

    🚨 View failing branch.

    This version is covered by your current version range and after updating it in your project the build failed.

    eslint-plugin-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

    Status Details
    • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

    Release Notes for v22.6.0

    22.6.0 (2019-05-22)

    Features

    Commits

    The new version differs by 9 commits.

    • 14d83ef feat(rules): add no-commented-out rule (#262)
    • 83ff198 chore: migrate no-jest-import to typescript (#259)
    • 718c08c chore: upgrade @typescript-eslint
    • ca2aa27 chore: port lowercase-name to TypeScript (#258)
    • 3df0058 chore(ci): run danger with lts version of node
    • 48e3a59 chore: precompile with babel (#257)
    • 8670804 chore: bump deps
    • 05eb11a chore: fix lint error
    • dff6446 docs: link to eslint-plugin-jest-formatting

    See the full diff

    FAQ and help

    There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


    Your Greenkeeper Bot :palm_tree:

    greenkeeper 
    opened by greenkeeper[bot] 10
  • Statusfy breaks when in a subfolder

    Statusfy breaks when in a subfolder

    • [x] I confirm that this is a issue rather than a question.

    Bug report

    When installed in a subfolder (ie https://status/example.com/company1), several things break as links to assets or other pages do not expect this.

    Version

    0.3.0.beta1 (also with previous 0.2.x)

    Steps to reproduce

    Install in a subfolder

    What is expected?

    All links work normally.

    What is actually happening?

    • Logo is a 404, it links to /static/img/xxxx.png instead of /subfolder/static/img/xxxx.png or use a fully qualified link
    • Link to History is a 404

    They all link to /xxxx instead of /subfolder/xxxx.

    Other relevant information

    1. I'd suggest the baseURL is used to prefix all those links. Best would be to automatically determine the subfolder by separating the domain from the baseUrl. Or else a secondary config option can be added, ie baseURL = https://status.example.com + baseFolder = /company_A/department_1

    2. Using a subfolder is common when hosting pages on Gitlab

    • Your OS: N/A
    • Node.js version: N/A
    • Browser version: N/A
    • Is this a global or local install? N/A
    • Which package manager did you use for the install? N/A
    opened by weeblr 10
  • `statusfy start` failed

    `statusfy start` failed

    • [x] I confirm that this is a issue rather than a question.

    Bug report

    Version

    ^0.2.1

    Steps to reproduce

    1. Download the following repository https://github.com/gruselhaus/status.gruselhaus.com
    2. npm install
    3. npm start

    What is expected?

    Server should start.

    What is actually happening?

    The script hangs on ℹ Reading configuration from config.js.

    bildschirmfoto 2019-02-25 um 18 03 12

    Other relevant information

    • Repository: https://github.com/gruselhaus/status.gruselhaus.com
    • Your OS: macOS 10.14.3
    • Node.js version: 11.10.0
    • Browser version: -
    • Is this a global or local install? Both failed
    • Which package manager did you use for the install? [email protected]
    bug 
    opened by gruselhaus 9
  • Failed at the @fortawesome/fontawesome-common-types@0.2.35 postinstall script.

    Failed at the @fortawesome/[email protected] postinstall script.

    When running npx statusfy init I run into following error:

    error errno 1 error @fortawesome/[email protected] postinstall:node attribution.jserror Exit status 1 error Failed at the @fortawesome/[email protected] postinstall script. error This is probably not a problem with npm. There is likely additional logging output above. verbose exit [ 1, true ]

    opened by Pagefreak 0
  • chore(deps): bump browserslist from 4.16.0 to 4.16.6

    chore(deps): bump browserslist from 4.16.0 to 4.16.6

    Bumps browserslist from 4.16.0 to 4.16.6.

    Changelog

    Sourced from browserslist's changelog.

    4.16.6

    • Fixed npm-shrinkwrap.json support in --update-db (by Geoff Newman).

    4.16.5

    • Fixed unsafe RegExp (by Yeting Li).

    4.16.4

    • Fixed unsafe RegExp.
    • Added artifactory support to --update-db (by Ittai Baratz).

    4.16.3

    • Fixed --update-db.

    4.16.2

    4.16.1

    • Fixed Chrome 4 with mobileToDesktop (by Aron Woost).

    4.16

    • Add browserslist config query.

    4.15

    • Add TypeScript types (by Dmitry Semigradsky).

    4.14.7

    • Fixed Yarn Workspaces support to --update-db (by Fausto Núñez Alberro).
    • Added browser changes to --update-db (by @​AleksandrSl).
    • Added color output to --update-db.
    • Updated package.funding to have link to our Open Collective.

    4.14.6

    • Fixed Yarn support in --update-db (by Ivan Storck).
    • Fixed npm 7 support in --update-db.

    4.14.5

    • Fixed last 2 electron versions query (by Sergey Melyukov).

    4.14.4

    • Fixed Unknown version 59 of op_mob error.

    4.14.3

    • Update Firefox ESR.

    4.14.2

    • Fixed --update-db on Windows (by James Ross).
    • Improved --update-db output.

    4.14.1

    • Added --update-db explanation (by Justin Zelinsky).

    ... (truncated)

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 1
  • chore(deps): bump hosted-git-info from 2.8.8 to 2.8.9

    chore(deps): bump hosted-git-info from 2.8.8 to 2.8.9

    Bumps hosted-git-info from 2.8.8 to 2.8.9.

    Changelog

    Sourced from hosted-git-info's changelog.

    2.8.9 (2021-04-07)

    Bug Fixes

    Commits
    Maintainer changes

    This version was pushed to npm by nlf, a new releaser for hosted-git-info since your current version.


    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 1
  • chore(deps): bump ua-parser-js from 0.7.23 to 0.7.28

    chore(deps): bump ua-parser-js from 0.7.23 to 0.7.28

    Bumps ua-parser-js from 0.7.23 to 0.7.28.

    Commits
    • 1d3c98a Revert breaking fix #279 and release as 0.7.28
    • 535f11b Delete redundant code
    • 642c039 Fix #492 LG TV WebOS detection
    • 3edacdd Merge branch 'master' into develop
    • acc0b91 Update contributor list
    • f726dcd Merge branch 'master' into develop
    • 383ca58 More test for tablet devices
    • 7c8aa43 Minor rearrangement
    • 09aa910 Add new device & browser: Tesla
    • 557cc21 More test for latest phones with unique form factor (fold/flip/qwerty/swivel)
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 1
  • chore(deps): bump handlebars from 4.7.6 to 4.7.7

    chore(deps): bump handlebars from 4.7.6 to 4.7.7

    Bumps handlebars from 4.7.6 to 4.7.7.

    Changelog

    Sourced from handlebars's changelog.

    v4.7.7 - February 15th, 2021

    • fix weird error in integration tests - eb860c0
    • fix: check prototype property access in strict-mode (#1736) - b6d3de7
    • fix: escape property names in compat mode (#1736) - f058970
    • refactor: In spec tests, use expectTemplate over equals and shouldThrow (#1683) - 77825f8
    • chore: start testing on Node.js 12 and 13 - 3789a30

    (POSSIBLY) BREAKING CHANGES:

    • the changes from version 4.6.0 now also apply in when using the compile-option "strict: true". Access to prototype properties is forbidden completely by default, specific properties or methods can be allowed via runtime-options. See #1633 for details. If you are using Handlebars as documented, you should not be accessing prototype properties from your template anyway, so the changes should not be a problem for you. Only the use of undocumented features can break your build.

    That is why we only bump the patch version despite mentioning breaking changes.

    Commits

    Commits
    • a9a8e40 v4.7.7
    • e66aed5 Update release notes
    • 7d4d170 disable IE in Saucelabs tests
    • eb860c0 fix weird error in integration tests
    • b6d3de7 fix: check prototype property access in strict-mode (#1736)
    • f058970 fix: escape property names in compat mode (#1736)
    • 77825f8 refator: In spec tests, use expectTemplate over equals and shouldThrow (#1683)
    • 3789a30 chore: start testing on Node.js 12 and 13
    • See full diff in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 1
  • chore(deps): update dependency fs-extra to v10

    chore(deps): update dependency fs-extra to v10

    WhiteSource Renovate

    This PR contains the following updates:

    | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | fs-extra | 9.1.0 -> 10.0.0 | age | adoption | passing | confidence |


    Release Notes

    jprichardson/node-fs-extra

    v10.0.0

    Compare Source

    Breaking changes

    The following changes, although technically semver-major, will not affect the vast majority of users:

    • Ensure correct type when destination exists for ensureLink*()/ensureSymlink*() (#​826, #​786, #​870)
    • Error when attempting to copy*() unknown file type (#​880)
    • Remove undocumented options for remove*() (#​882)
    Improvements
    • Allow changing case of filenames with move*(), even on technically case-insensitive filesystems (#​759, #​801)
    • Use native fs.rm*() for remove*() in environments that support it (#​882, #​806)
    • Improve emptyDir() performance (#​885)
    Bugfixes
    • Ensure copy*()'s filter function is not called more than necessary (#​883, #​809)
    • Fix move*() raising EPERM error when moving a file to the root of a drive on Windows (#​897, #​819)
    Miscellaneous changes

    Configuration

    📅 Schedule: "after 10pm every weekday,before 6am every weekday" (UTC).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    ♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about these updates again.


    • [ ] If you want to rebase/retry this PR, check this box.

    This PR has been generated by WhiteSource Renovate. View repository job log here.

    opened by renovate[bot] 2
  • Configure WhiteSource Bolt for GitHub

    Configure WhiteSource Bolt for GitHub

    Welcome to WhiteSource Bolt for GitHub! This is an onboarding PR to help you understand and configure settings before WhiteSource starts scanning your repository for security vulnerabilities.

    :vertical_traffic_light: WhiteSource Bolt for GitHub will start scanning your repository only once you merge this Pull Request. To disable WhiteSource Bolt for GitHub, simply close this Pull Request.


    What to Expect

    This PR contains a '.whitesource' configuration file which can be customized to your needs. If no changes were applied to this file, WhiteSource Bolt for GitHub will use the default configuration.

    Before merging this PR, Make sure the Issues tab is enabled. Once you merge this PR, WhiteSource Bolt for GitHub will scan your repository and create a GitHub Issue for every vulnerability detected in your repository.

    If you do not want a GitHub Issue to be created for each detected vulnerability, you can edit the '.whitesource' file and set the 'minSeverityLevel' parameter to 'NONE'.


    :question: Got questions? Check out WhiteSource Bolt for GitHub docs. If you need any further assistance then you can also request help here.

    opened by whitesource-bolt-for-github[bot] 2
  • chore(deps): bump ssri from 6.0.1 to 6.0.2

    chore(deps): bump ssri from 6.0.1 to 6.0.2

    Bumps ssri from 6.0.1 to 6.0.2.

    Changelog

    Sourced from ssri's changelog.

    6.0.2 (2021-04-07)

    Bug Fixes

    • backport regex change from 8.0.1 (b30dfdb), closes #19

    Commits
    Maintainer changes

    This version was pushed to npm by nlf, a new releaser for ssri since your current version.


    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 1
  • Ability to add Social Meta Images

    Ability to add Social Meta Images

    Feature request

    • [x] I confirm that this is a feature request rather than a question.

    What problem does this feature solve?

    Ability to add Social Meta Images so they don't look ugly when your share in social media

    What does the proposed API look like?

    --

    How should this be implemented in your opinion?

    Single Meta image for all the pages. Seems this is status page. One Image for all pages.

    Are you willing to work on this yourself?**

    Nope. I have tried to implemented. But I couldn't do it.

    opened by mcnaveen 0
  • chore(deps): update dependency cssnano to v5

    chore(deps): update dependency cssnano to v5

    WhiteSource Renovate

    This PR contains the following updates:

    | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | cssnano | 4.1.10 -> 5.0.6 | age | adoption | passing | confidence |


    Release Notes

    cssnano/cssnano

    v5.0.6

    Compare Source

    Bug Fixes

    postcss-normalize-url: bump normalize-url dependency to 6.0.1 (#​1142) (b60f54bed)

    postcss-ordered-values: preserve columns count (#​1144) (9acd6a2fe3e)

    v5.0.5

    Compare Source

    Bug fixes

    • Preserve alpha channel in color minification
    • Check overlaps more exhaustively when merging rules
    • Do not crash when the input CSS contains relative URLs

    v5.0.4

    Compare Source

    Bug fixes

    v5.0.3

    Compare Source

    v5.0.2

    Compare Source

    Bug Fixes

    v5.0.1

    Compare Source

    v5.0.0

    Compare Source

    Major changes

    • requires Node >= 10.13
    • PostCSS 8 API, so cssnano 5 does not emit warnings when running under PostCSS 8
    • updated to SVGO 2, fixing many SVG minification bugs
    • updated css-value-parser and css-selector-parser, fixing many bugs
    Upgrade notes

    If you use the cssnano JavaScript API, you need to change your code:

    • Replace cssnano.process() with cssnano().process() (notice the () after cssnano)

    • pass cssnano options to cssnano() instead of process()

    cssnano(cssnanoOptions).process(postcssOptions)
    

    Bug fixes

    • fix improperly discarding @font-face declarations #​726
    • partially fix some isues where cssnano did not combine rules when used together with postcss-nested #​1004
    • fix translate3d() minification #​920
    • fix minification of values starting with e #​589, #​984
    • fix minification of percentage vaalues #​962, #​957
    • fix minification of aspect-ratio #​963
    • fix merging of @supports rules #​974
    • fix sorting of longhand and shorthand properties #​535
    • remove vulnerable dependency and always warn with bad SVG input #​1034

    v4.1.11

    Compare Source

    4.1.11
    Bug Fixes

    Configuration

    📅 Schedule: "after 10pm every weekday,before 6am every weekday" (UTC).

    🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

    Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

    🔕 Ignore: Close this PR and you won't be reminded about this update again.


    • [ ] If you want to rebase/retry this PR, check this box.

    This PR has been generated by WhiteSource Renovate. View repository job log here.

    opened by renovate[bot] 3
Releases(v0.5.0)
  • v0.5.0(Dec 18, 2019)

    Performance

    • core: improve performance and reliability

    Bug Fixes

    • core: fix compilation error because of invalid core-js version (5a16424)
    • core: replace <no-ssr> with <client-only> (fcc90e3)
    • docs: add missing information (823ce73)
    • core: fix i18n with right camel case for footer links (766a914)

    Code Refactoring

    • drop support for Node.js v8 (b79f140)

    Minor Features

    • footer links for EU GDPR legal notice and data pricacy statement (22ce441)

    BREAKING CHANGES

    • minimum required Node.js version is 10.x
    Source code(tar.gz)
    Source code(zip)
  • v0.4.3(Aug 22, 2019)

  • v0.4.2(Aug 22, 2019)

  • v0.4.1(Jun 27, 2019)

    Bug Fixes

    • docs: make explicit the under-maintenance definition (b2a41c9)
    • website: remove responsive image from the article "statusfy-release-0-2-0" (fa58780)
    • website: remove unused definitions in the Spanish translation (ae73c45)

    Features

    • website: create blog article "statusfy-release-0-4-0" (b136e7d)
    • website: include the community post in the blog section (5e42ed4)
    • website: remove disqus comments (e4e3bd0)
    Source code(tar.gz)
    Source code(zip)
  • v0.4.0(Jun 13, 2019)

    Bug Fixes

    • core: fix displaying the date of incidents when using the cli #184 (#208) (6e7d26e)
    • core, website: return postcss plugins as an object (5c33b84)
    • docs: fix heading of the page "Guide/PWA" (#219) (eb436af)
    • docs: fix the dimension of the images (83b6705)
    • docs: fix the Firebase SSR reference in the deploy section (2cedb4f)
    • package: update @nuxtjs/sitemap to version 1.0.0 (#183) (75db9c3)
    • package: update intersection-observer to version 0.6.0 (#186) (6e9b3f0)
    • package: update semver to version 6.0.0 (38fdf8a)
    • website: fix the reponsive images placeholder values (d38eb7f)

    Features

    • core: add Italian translation (#179) (e5a80c4) (thanks to jeckodevelopment)
    • use docker multi-stage build (#193) (2b12153)
    • core: support web-push notifications with OneSignal (2adff5e)
    • core, website: upgrade workbox to v4.x (6952de3)
    • docs: create the onsignal section (cc648a0)
    • docs: support sitemap generation and improve SEO (c31c107)

    • For more information on this update, read our blog post.
    • You can join the conversation on Spectrum.
    Source code(tar.gz)
    Source code(zip)
  • v0.3.1(Mar 23, 2019)

    Bug Fixes

    • bug: incorrect context referenct in nuxt (647cab0)
    • website: fix avatar position (821deea)
    • website: fix starting the website when no internet connection is available (2e08200)

    Performance Improvements

    • website: support lazy loading the images from the blog section (136c01a)
    Source code(tar.gz)
    Source code(zip)
  • v0.3.0(Mar 20, 2019)

    Bug Fixes

    • cli: notify the user when the production server is initialized (9973555)
    • cli, core: fix detection of the 'analyze' argument (1981e43)
    • core: display the content for 'Scheduled Maintenance Incidents' (05b0bd1)
    • core: fix referencing the dates lib (0a2fe50)
    • core: fix the font style of the time indicator of each incident (88cb2ae)
    • core: improve dates parsing and formatting (aa32346)
    • docs: fix incorrect flag for start command (#148) (d4b376d)
    • core: fix text wrapping of the system names (637f7bb)
    • core,website: enable subfolder generation on static mode (a94270c)
    • core,website: fix regeneratorRuntime dependencies requirement (2fb0b2e)
    • core: the base url cannot contain a sub-path (e7ce6bc)

    Features

    • cli: create the 'delete-incident' command (8aef1f9)
    • cli: create the 'update-incident' command (a22d72a)
    • core: display the end date of the scheduled incidents (858c3ea)
    • core: support defining the position of the scheduled section in the home page (22c85d2)
    • core, docs: explicitly make YAML as the default front matter format (a3a5675)
    • website: configure @bazzite/nuxt-netlify (7e46bd1)
    • officially support Docker 🤓 (289b296)
    • core: create the "days since latest incident" sub-section in the home page (cbaf025)
    • core: new interface translations:
    • website: migrate the blog section to local markdown files (dfa141c)

    BREAKING CHANGES

    • core: deployments under a subpath (e.g. https://example.com/status/) are no longer supported
    • core, docs: the new-incident command no longer asks for the front matter format (a3a5675)

    • For more information on this update, read our blog post.
    Source code(tar.gz)
    Source code(zip)
  • v0.2.1(Dec 11, 2018)

  • v0.2.0(Dec 11, 2018)

    Bug Fixes

    Features

    • support contributions from Open Collective (257261f)
    • core: create the subscriptions sub-section (b798439)
    • core: support iCalendar generation from scheduled incidents (c139aad)
    • core: support RSS and Atom feeds generation (81371e2)
    • core: support Scheduled Maintenance definition (2edbe9e)
    • core: support sitemap generation (965f496)
    • docs: create the incidents sub-section (cbc5539)
    • docs: create the Notifications sub-section (7fa8959)
    • docs: improve the Contribution Guide (1d9bcdd)
    • docs: support Algolia DocSearch (9cd9bdb)

    • For more information on this update, read our blog post.
    Source code(tar.gz)
    Source code(zip)
  • v0.1.3(Nov 20, 2018)

  • v0.1.2(Nov 20, 2018)

  • v0.1.1(Nov 17, 2018)

    Bug Fixes

    • cli: add the missing "dependencies installation" message when initializing a new project (1841390)
    • cli: fix the new project creation (1cbdf5e)
    • cli: fix the new incident creation (#64)

    Features

    • docs: create the news subscription form (0844d14)
    • website: create the news subscription form (6be629b)
    Source code(tar.gz)
    Source code(zip)
  • v0.1.0(Nov 14, 2018)

Owner
Julio Marquez
☕️ Software Engineer, Entrepreneur & Coffee lover 💻 Full-stack developer 🎨 Amateur designer
Julio Marquez
FHEMApp ist eine Web-Application zur Steuerung deiner Smarthome Umgebung.

FHEMApp ist eine Web-Application zur Steuerung deiner Smarthome Umgebung. Sie wurde als Frontend für den Einsatz mit FHEM(tm) entwickelt. FHE

jens 14 Jul 8, 2021
A framework written in Vue.js for creating command-line like interfaces in web browsers.

promptie A framework for creating command-line like interfaces in web browsers Promptie gives you useful and convenient API's to simulate a CLI like i

Ali Bardakci 80 Mar 8, 2021
webchat via WebSockets/WebRTC that allows messaging/video call/screen sharing

Live demo: pychat.org, video Table of contents About When should I use pychat How to host pychat Run test docker image Run prod docker image Native se

Andrew 172 Jul 23, 2021
A B/S mode system monitor for linux (demo http://199.247.1.240:2048)

中文说明 sysmon Sysmon is a C/S mode system monitor for Linux distribution. With server side daemon, you can remotely watch usage of your system resources

何培勤 110 Jul 26, 2021
Vue.js based REST-ful CRUD system

the project is not supported If you want to contribute to this project please fork from this project or email me to add you to what-crud group Vue CRU

What CRUD! 674 Jul 18, 2021
This is a beautiful Blog with Nuxt.js.

About This is a beautiful Blog with Nuxt.js. Nuxt.js is a powerful and simple open-source framework for building websites on the Jamstack using Vue, a

Gasy Coder 3 May 12, 2021
A beautiful chat rooms component made with Vue.js - compatible with Vue, React & Angular

A beautiful chat rooms component made with Vue.js - compatible with Vue, React & Angular

Antoine Dupont 480 Jul 24, 2021
Web Extension — A new tab page extension with material design and useful features :new: :tada:

Epiboard A new tab page adding a touch of wow and an interface following the lines of the material design. ?? ?? . You can simply and quickly access t

Alex 272 Jul 15, 2021
Linux System Optimizer and Monitoring - https://oguzhaninan.github.io/Stacer-Web

Linux System Optimizer and Monitoring Sponsors Reviews Required Packages curl, systemd PPA Repository (for ubuntu) sudo add-apt-repository ppa:oguzhan

Oguzhan Inan 7.1k Jul 27, 2021
📕 A website simulating linux system's GUI, using theme of Deepin distro.

About GoodManWEN.github.io A website simulating linux system's GUI, using theme of Deepin distro. You can write blogs with markdown and use it to serv

null 1.1k Jul 22, 2021
cms based on mongodb, nodejs, koa, vue and more

jade-press cms based on mongodb, nodejs, koa, vue and more features based on mongodb(database and session), nodejs 6+, koa, vue.js... built in jade ed

null 40 Oct 4, 2020
A mobile first, handwritten, responsive web app for music fans.

neteast-music-vue Deployed link: https://neteast.netlify.com/ It is a mobile first responsive web app for listening music from Neteast cloud platform

Tato 46 Jul 17, 2021
A Vue.js web application for Freedomotic Open IoT framework

fd-vue-webapp A Vue.js client for Freedomotic framework. Scope of the project This repository contains the implementation of a front end client for Fr

Freedomotic 54 Jul 24, 2021