-
Notifications
You must be signed in to change notification settings - Fork 650
Installing As a Windows Service
Ruben Dario Duarte edited this page Oct 2, 2015
·
11 revisions
Loosely based upon the instructions found here. I crafted the following and it provided me with a fully working sinopia service installation:
- Create a directory for sinopia
mkdir c:\sinopia
cd c:\sinopia
- Install sinopia locally (I ran into npm issues with global installs)
npm install sinopia
- Create your config.yaml file in this location (
c:\sinopia\config.yaml
) - Download WinSW
- Place the executable (e.g.
winsw-1.9-bin.exe
) into this folder (c:\sinopia
) and rename it tosinopia-winsw.exe
- Place the executable (e.g.
- Create a configuration file in
c:\sinopia
, namedsinopia-winsw.xml
with the following configuration
<service>
<id>sinopia</id>
<name>sinopia</name>
<description>sinopia</description>
<executable>node</executable>
<arguments>c:\sinopia\node_modules\sinopia\lib\cli.js -c c:\sinopia\config.yaml</arguments>
<logmode>roll</logmode>
<workingdirectory>c:\sinopia\</workingdirectory>
</service>
- Install your service
cd c:\sinopia
sinopia-winsw.exe install
- Start your service
sinopia-winsw.exe start
Some of the above config is more verbose than I had expected, it appears as though 'workingdirectory' is ignored, but other than that, this works for me and allows my sinopia instance to persist between restarts of the server, and also restart itself should there be any crashes of the sinopia process.