Commit 7fef14c322
refactored the directory structure - reflect these changes in the documentation.
2.4 KiB
Installing As a Windows Service
Loosely based upon the instructions found here. I crafted the following and it provided me with a fully working verdaccio service installation:
- Create a directory for verdaccio
- mkdir
c:\verdaccio
- cd
c:\verdaccio
- mkdir
- Install verdaccio locally (I ran into npm issues with global installs)
- npm install verdaccio
- Create your
config.yaml
file in this location(c:\verdaccio\config.yaml)
- Windows Service Setup
Using NSSM
ALTERNATIVE METHOD: (WinSW package was missing when I tried to download it)
-
Download NSSM and extract
-
Add the path that contains nssm.exe to the PATH
-
Open an administrative command
-
Run nssm install verdaccio At a minimum you must fill in the Application tab Path, Startup directory and Arguments fields. Assuming an install with node in the system path and a location of c:\verdaccio the below values will work:
- Path:
node
- Startup directory:
c:\verdaccio
- Arguments:
c:\verdaccio\node_modules\verdaccio\src\lib\cli.js -c c:\verdaccio\config.yaml
You can adjust other service settings under other tabs as desired. When you are done, click Install service button
- Path:
-
Start the service sc start verdaccio
Using WinSW
- As of 2015-10-27, WinSW is no longer available at the below location. Please follow the Using NSSM instructions above.
- Download WinSW
- Place the executable (e.g.
winsw-1.9-bin.exe
) into this folder (c:\verdaccio
) and rename it toverdaccio-winsw.exe
- Place the executable (e.g.
- Create a configuration file in
c:\verdaccio
, namedverdaccio-winsw.xml
with the following configurationxml verdaccio verdaccio verdaccio node c:\verdaccio\node_modules\verdaccio\src\lib\cli.js -c c:\verdaccio\config.yaml roll c:\verdaccio\
. - Install your service
cd c:\verdaccio
verdaccio-winsw.exe install
- Start your service
verdaccio-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 verdaccio instance to persist between restarts of the server, and also restart itself should there be any crashes of the verdaccio process.