/CloudIncidentStatus

CloudIncidentStatus is a open-source status and incident communication tool.

Primary LanguageHTMLBSD 3-Clause "New" or "Revised" LicenseBSD-3-Clause

                    Dependencies Contributions welcome

CloudIncidentStatus

CloudIncidentStatus is a opensource status and incident communication tool.

If you ask how could CloudIncidentStatus help you? Below you will find some information.

With this tool you will inform your customers about the issues on your product and you will turn a bad situation into a great customer experience.

Build customer trust with this tool. Allow them to know when an incident occurs or a scheduled maintenance will take place, they will get a notification via email.

ScreenShots

Overview

  • Components List of your services
  • Scheduled Maintenace
  • Inform your clients about issues
  • Subscriber notifications via email
  • Clients can see in real-time the status of components
  • Clients can see in real-time the status of an issue
  • Set a status for what’s impacted
  • Display historic uptime services
  • Faster incident comms
  • More customer trust
  • Less time wasted
  • Skip all the "It is my service down?", questions
  • A friendly Admin interface and easy to use
  • A friendly User interface.
  • and more, your customers will thank you.

Requirements

If you don't have an external VPS, you can buy one from Webland.ro and managed with ClusterCS.com.

How to install

Step 1
$ cd /home/statuspage/
$ git clone https://github.com/alexandrucanavoiu/CloudIncidentStatus .
Step 2

By default CloudIncidentStatus comes with a .env.example file. You will need to rename this file as .env You will change the default values with your own (like database name, database user, database password, etc)

Step 3
$ find ./ -type f -exec chmod 644 {} +
$ find ./ -type d -exec chmod 755 {} +
Step 4
$ composer update
$ php artisan key:generate
Step 5
$ php artisan migrate
$ php artisan db:seed --class=Settings
$ php artisan db:seed --class=ComponentStatuses
$ php artisan db:seed --class=Users
$ php artisan db:seed --class=IncidentStatus
$ php artisan db:seed --class=Footer
Step 6

You need to run Queue in background (See the command "screen" from linux). This will be used for Subscriber Emails when an Incident or Maintenance is created.

$ php artisan queue:work --queue=Incidents,Maintenance --tries=1
Step 7
Admin page: www.yourdomain.org/login
username: demo@example.org
password: demo

Professional Installation

I offer a professional installation of this tool. Please contact me at alex.canavoiu@marketingromania.ro

Security Vulnerabilities

It is an open-source software. If you discover a security vulnerability please contact me or you can come with a solution by contributing at the project.