slack-newspublisher

slack-newspublisher is a Slack bot running with Node in a Docker container in a Google Compute Engine instance. It is a replacement of the old ruby scripts we had in the Amazon cloud.

It serves three different purposes:

• Publish new articles from all of our sites (except test sites) to the #amedia-news channel on Slack for Amedia Utvikling.
• Publish new feature articles from all our sites (except test sites) to the #the-feature channel on Slack for Amedia Utvikling.
• Publish all new Origo article comments onto the #folkedypet channel.

Technology in use

• Node >=8.1.2
• Docker
• Google Datastore (for caching)
• Google Compute Engine (Hosts the running docker image)
• Slack ;)

Development

In order to maintain this project you must have access to the amedia-acp in the Google Cloud. The reason why it ended up there is simply that we had enabled payment on this project earlier on. People on the HappyDesk team can provide access.

Further you got to have the gcloud tool installed locally. Set the default project to amedia-acp and login gcloud auth login

Now you should have access to Google Datastore, Google Container Registry and Google Compute Engine; Which are the services in use.

In development modus the bot will post to the #bot-test channel instead of the standard channels (which are configured in the config/production.json file). It will also use development values from the Google Datastore. So you should not be afraid of messing up anything while testing. However, things might not work as expected if more than one developer are running the bot at the same time.

Running in dev mode

> npm run start

Release and deploy

You must have the Amedia Tools repository installed locally (Read more here https://github.com/amedia/tools).

Release

> amediainternal-releaser release

Deploy

The release script will provide you with the full command. But it will look something like this:

> amediainternal-deploy slack-newspublisher 1.2.0

Where the version of course will vary.