Skip to content

Latest commit

 

History

History
66 lines (41 loc) · 3.17 KB

windows.md

File metadata and controls

66 lines (41 loc) · 3.17 KB
Raw
permalink
/docs/deploying/windows/

Deploying to Windows

Hasn't been fully tested - YMMV

There are 4 primary steps to deploying and running hubot on a Windows machine:

  • node and npm
  • a way to get source code updated on the server
  • setting up environment variables for hubot
  • a way to start hubot, start it up if it crashes, and restart it when code updates

node and npm

To start, your windows server will need node and npm. The best way to do this is with chocolatey using the nodejs.install package. I've found that sometimes the system path variable is not correctly set; ensure you can run node/npm from the command line. If needed set the PATH variable with "setx PATH "%PATH%;C:\Program Files\nodejs" "

Your other option is to install directly from NodeJS and run the current download (v0.12.4 as of this documentation). This should set your PATH variables for you.

Updating code on the server

To get the code on your server, you can follow the instructions at Getting Started on your local development machine or directly on the server. If you are building locally, push your hubot to GitHub and clone the repo onto your server. Don't clone the normal github/hubot repository, make sure you're using the Yo Generator to build your own hubot.

Setting up environment vars

You will want to set up your hubot environment variables on the server where it will run. You can do this by opening an administrative PowerShell and typing the following:

[Environment]::SetEnvironmentVariable("HUBOT_ADAPTER", "Campfire", "Machine")

This is equivalent to going into the system menu -> selecting advanced system settings -> environment vars and adding a new system variable called HUBOT_ADAPTER with the value of Campfire.

Starting, stopping, and restarting hubot

Every hubot install has a bin/hubot script to handle starting up the hubot. You can run this command directly from your hubot folder by typing the following:

.\bin\hubot –adapter campfire

There are a few issues if you call it manually, though.

  • you disconnect, and hubot dies
  • hubot dies, for any reason, and doesn't start again
  • it doesn't start up at boot automatically

To fix this, you will want to create a .ps1 file with whatever name makes you happy that you will call from your hubot directory. There is a copy of this file in the examples directory here. It should contain the following:

Write-Host "Starting Hubot Watcher"
While (1)
{
    Write-Host "Starting Hubot"
    Start-Process powershell -ArgumentList ".\bin\hubot –adapter slack" -wait
}

Remember to allow local unsigned PowerShell scripts if you are using the .ps1 file to run hubot. Run this command in an Administrator PowerShell window.

Set-ExecutionPolicy RemoteSigned

You can set this .ps1 as scheduled task on boot if you like or some other way to start your process.

Expanding the documentation

Not yet fleshed out. Help contribute by submitting a pull request, please?