edits to docker-parity and stack (documentation, code reorg)

Author: makevoid

Diff for: stack/Dockerfile-parity

@@ -11,9 +11,9 @@ COPY ./parity/chain/spec.json      spec.json
 COPY ./parity/chain/reserved_peers reserved_peers
 
 ARG PARITY_ID
-ARG AWS_ACCESS_KEY_ID
-ARG AWS_SECRET_ACCESS_KEY
-ARG RESTORE_FILE
+ARG S3_ACCESS_KEY_ID
+ARG S3_SECRET_ACCESS_KEY
+ARG S3_BUCKET_NAME
 
 RUN echo "Building parity${PARITY_ID}..."
 
@@ -23,7 +23,7 @@ COPY ./parity/${PARITY_ID}/parity         ./data/keys/parity
 COPY ./parity/${PARITY_ID}/network.key    ./data/network/key
 
 RUN mkdir ~/.aws
-RUN echo "[default]\naws_access_key_id = $AWS_ACCESS_KEY_ID\naws_secret_access_key = $AWS_SECRET_ACCESS_KEY" > ~/.aws/credentials
+RUN echo "[default]\naws_access_key_id = $S3_ACCESS_KEY_ID\naws_secret_access_key = $S3_SECRET_ACCESS_KEY" > ~/.aws/credentials
 
 RUN apt-get update -y
 RUN apt-get install -y curl bash redis-tools
@@ -32,10 +32,7 @@ RUN apt-get install nodejs -y && \
   rm -rf /tmp/*
 
 COPY ./package* /parity/
-COPY ./docker/entrypoint-parity.sh entrypoint-parity.sh
-COPY ./docker/cron-job.js /parity/
-COPY ./docker/cron-job.sh /parity/
-COPY ./docker/download.js /parity/
+COPY ./backup /parity/
 RUN npm install
 
 ENTRYPOINT [ "bash", "./entrypoint-parity.sh" ]

Diff for: stack/docker/download.js renamed to stack/backup/download.js

@@ -11,7 +11,7 @@ const downloadFile = async () => {
 
   const params = {
     Bucket: 'ab-parity-backups',
-    Key: `base-app-mantle/parity${parityID}/${fileName}`
+    Key: `launchpad-dev/parity${parityID}/${fileName}`
   }
   const backupStream = s3.getObject(params).createReadStream()
   const writeStream = fs.createWriteStream(fileName);

Diff for: stack/docker/entrypoint-parity.sh renamed to stack/backup/entrypoint-parity.sh

@@ -23,6 +23,6 @@ for i in 1 2 3; do
 done
 
 # NOTE: uncomment to activate backups
-# node /parity/cron-job.js
+# node /parity/parity-backup-cron-setup.js
 
 /parity/parity --chain /parity/spec.json --config /parity/authority.toml -d /parity/data

Diff for: stack/docker/cron-job.js renamed to stack/backup/parity-backup-cron-setup.js

@@ -3,27 +3,41 @@ const fs = require('fs')
 const AWS = require('aws-sdk')
 const { exec } = require('child_process')
 
+const BUCKET_NAME = 'ab-parity-backups'
+
 const s3 = new AWS.S3()
 
-// Run task every day at 06:00 (using container timezone)
-cron.schedule('* 06 * * *', () => {
-  console.log('RUNNING PARITY BACKUP TASK...')
+const createFilename = () => {
+  const date = new Date()
+
+  let day = date.getDate()
+  day = day < 10 ? `0${day}` : `${day}`
+
+  let month = date.getMonth() + 1
+  month = month < 10 ? `0${month}` : `${month}`
+
+  const year = `${date.getFullYear()}`
+
+  return `${year}-${month}-${day}.tar.gz`
+}
+
+const runBackup = () => {
+  console.log('Running Parity backup task...')
 
   const parityID = process.env.PARITY_ID
   const backupName = createFilename()
-  const command = `sh cron-job.sh ${backupName}`
+  const command = `sh parity-backup-tar.sh ${backupName}`
 
   const execution = exec(command)
   execution.stdout.on('data', (data) => {
     // Archiving has been completed - we can now upload to S3
     if (data.trim() === 'Archive complete...') {
       const body = fs.readFileSync(`./${backupName}`)
       const params = {
-        Bucket: 'ab-parity-backups',
+        Bucket: BUCKET_NAME,
         Body: body,
-        Key: `base-app-mantle/parity${parityID}/${backupName}`
+        Key: `launchpad-dev/parity${parityID}/${backupName}`
       }
-
       s3.upload(params, (err, data) => {
         if (err) {
           console.log(`S3 upload error: ${err}`)
@@ -33,18 +47,13 @@ cron.schedule('* 06 * * *', () => {
       })
     }
   })
-})
-
-function createFilename() {
-  const date = new Date()
-
-  let day = date.getDate()
-  day = day < 10 ? `0${day}` : `${day}`
+}
 
-  let month = date.getMonth() + 1
-  month = month < 10 ? `0${month}` : `${month}`
- 
-  const year = `${date.getFullYear()}`
+const setupCron = () => {
+  // Run task every day at 06:00 (using container timezone)
+  cron.schedule('* 06 * * *', () => {
+    runBackup()
+  })
+}
 
-  return `${year}-${month}-${day}.tar.gz`
-}
+setupCron()

Diff for: stack/docker/cron-job.sh renamed to stack/backup/parity-backup-tar.sh

@@ -0,0 +1,38 @@
+## Pingdom
+
+This guide has the key points you neeed to set up Pingom 
+
+### Setting up on Slack
+
+Visit [Slack's app manager](https://appliedblockchain.slack.com/apps/manage) for Applied Blockchain.
+
+* Search for **Pingdom** on the list of apps then click on it.
+* Click on **Add Configuration**.
+* Choose the channel to be notified (use either the project's channel or *projectname-notifications*).
+* Click on **Add Pingdom Integration**.
+
+You'll be redirected to a page with more configuration's to add onto Pingdom but for now, all we'll need is the **Webhook URL**.
+
+### Setting up on Pingdom
+
+Visit [Pingdom's Official Website](https://www.pingdom.com/) and login. We should have a shared account on [1Password](https://1password.com/).
+There are a couple of checks you should do before actually integrating the monitoring:
+
+- Go to the **Users and teams** tab then **Users**. If you've not been added already, please do it yourself.
+- Go to the **Users and teams** tab then **Teams**. If your team/project is not added already, please do and add all the appropriate members.
+
+#### Integrating Pingdom
+
+* Go to **Integration** and click on **Integrations** tab.
+* Click on **Add new**. Put an appropriate name to the webhook as well as the **Webhook URL** we've just got from Slack. Click **Save Integration**.
+* Go to **Experience Monitoring** and click on the **Uptime** tab.
+* Click on **Add new**. A window will popup and you should set the appropriate fields for the API healthcheck route:
+  * Name: should be compatible to the project API to be monitored;
+  * Web: HTTP(s);
+  * URL/IP: *https://* *example.io/api/health*;
+    * Optional tab: insert port if needed
+  * Who to alert: check your team or individuals;
+  * Scroll down the window and check *your webhook* you've inserted on the integration's tab.
+  * **Add** the new check you've configured.
+
+You can then try to test the monitoring service by clicking on **Test** within the Uptime window.

Diff for: stack/docs/Pingdom.md

@@ -61,6 +61,6 @@
       "WS_SECRET"       : "OurDashSecret93%",
       "VERBOSITY"       : 3
     }
-  } 
+  }
 
 ]

Diff for: stack/explorer/.keep

@@ -1,7 +1,3 @@
-# Stack
-
-Stack information for deployment with parity nodes, prometheus, grafana and others.
-
 ## Prometheus
 
 Metrics source
@@ -33,7 +29,6 @@ ExecStart=/usr/bin/dockerd -H fd:// \
 docker-compose -f docker-compose.yml -f add-prometheus.yml up
 ```
 
-
 ## Possible Usage
 * Multiple datasource from different metrics datasources (e.g. Postgres, Azure, AWS)
 * Use of Prometheus Alert to sent alerts
@@ -44,14 +39,3 @@ docker-compose -f docker-compose.yml -f add-prometheus.yml up
 ## Known Issues
 * Settting prometheus datasource to be browser
   Prometheus datasource is not accessible via grafana and should be changed to `Browser` instead of `Server`
-
-# Docker Dev
-## How to Use
-
-1. Install docker and docker compose
-2. In a terminal, run `source docker-aliases.sh`
-3. You might need to run `npm i && npm run compile` in the contracts folder if you haven't already.
-4. Start parity only: `mantle-compose up parity`
-5. While parity is running, deploy the contracts(run `npm run deploy` from the contracts folder).
-6. Run `mantle-compose build` to build the api and react images
-7. Stop parity and run `mantle-compose up` to start all the services