mesg-pusher v3.0.3

mesg-pusher

MESG Service for Pusher ID: com.mesg.pusher

Contents

• Installation
  • MESG SDK
  • Deploy the Service
• Definitions
  • Tasks
    • trigger
    • triggerBatch
    • channels
    • channel

Installation

MESG SDK

This service requires MESG SDK to be installed first.

You can install MESG SDK by running the following command or follow the installation guide.

npm install -g mesg-cli

Deploy the Service

To deploy this service, go to this service page on the MESG Marketplace and click the button "get/buy this service".

Features

Currently able to use Pusher channels, channel, trigger and triggerBatch features from MESG.

Use case

MESG Applications on different servers communicating together over Pusher notifications.

Example

1. on MESG Application on a server A : use this MESG Service to send notifications over Pusher.

2. on MESG Application on a server B : listen to the notifications emitted by MESG Application on a server A over Pusher.

How to listen in a MESG Application

Install MESG and Pusher dependencies :

yarn add mesg-js pusher-js

Create a socket connection to listen and react to Pusher notifications :

// in a MESG Application
const { application } = require('mesg-js')
const mesg = application()
const Pusher = require('pusher-js')
const pusher = new Pusher('PUSHER_APP_KEY', { cluster: 'PUSHER_CLUSTER', forceTLS: true }) // replace with your credentials
const INSTANCE_HASH = await mesg.resolve('com.mesg.pusher')
const CHANNEL = 'some-channel'
const EVENT = 'some-event'
const CREDENTIALS = { appId: 'PUSHER_APP_ID', key: 'PUSHER_APP_KEY', secret: 'PUSHER_APP_SECRET' } // replace with your credentials
// subscribe to Pusher channel
const channel = pusher.subscribe(CHANNEL)
// on Pusher notification received
channel.bind(EVENT, data => {
  // example : launch MESG service trigger task
  mesg.executeTask({
    instanceHash: INSTANCE_HASH,
    taskKey: 'trigger',
    inputs: mesg.encodeData({ ...CREDENTIALS, channel: CHANNEL, event: EVENT, ...data })
  })
})

Environment variables

Instead of providing Pusher credentials or options on each request, these can be provided via command line arguments or .env file, as shown below in Integration tests.

As usual, user inputs always takes precedence on defined environment variables.

Integration tests

In order to launch them locally you will have to pass the environment variables along with your command, like so :

• via command line arguments :

  export PUSHER_APP_ID=... && export PUSHER_APP_KEY=... && export PUSHER_APP_SECRET=... && export PUSHER_CLUSTER=... && export MESG_ACCOUNT=... && export MESG_PASSPHRASE=... && yarn test

• via .env file :
  • file

    export PUSHER_APP_ID=...
    export PUSHER_APP_KEY=...
    export PUSHER_APP_SECRET=...
    export PUSHER_CLUSTER=...
    export MESG_ACCOUNT=...
    export MESG_PASSPHRASE=...

  • command

    source .env && yarn test

Definitions

Tasks

Task key: trigger

triggers an event on one or more channels

Inputs

Outputs

Task key: triggerBatch

triggers multiple events in a single call (up to 10 per call on the multi-tenant clusters)

Inputs

Outputs

Task key: channels

get the list of the channel within an application that have active subscriptions (also referred to as being occupied)

Inputs

Outputs

Task key: channel

fetch one or some attributes for a given channel

Inputs

Outputs