commit
5a2974ca2c
|
@ -12,7 +12,7 @@ ENiGMA½ will run on both 32bit and 64bit Windows. If you want to run 16bit door
|
|||
|
||||
1. Upgrade NPM : At this time node comes with NPM 5.6 preinstalled. To upgrade to a newer version now or in the future on windows follow this method. `*Run PowerShell as Administrator`
|
||||
|
||||
`*Inital Install`
|
||||
`*Initial Install`
|
||||
```Powershell
|
||||
Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force
|
||||
npm install -g npm-windows-upgrade
|
||||
|
@ -23,7 +23,7 @@ ENiGMA½ will run on both 32bit and 64bit Windows. If you want to run 16bit door
|
|||
```
|
||||
|
||||
Note: Do not run `npm i -g npm`. Instead use `npm-windows-upgrade` to update npm going forward.
|
||||
Also if you run the NodeJS installer, it will replace the node version.:
|
||||
Also if you run the NodeJS installer, it will replace the node version.
|
||||
|
||||
2. Install [windows-build-tools for npm](https://www.npmjs.com/package/windows-build-tools)
|
||||
`*This will also install python 2.7`
|
||||
|
@ -66,4 +66,4 @@ ENiGMA½ will run on both 32bit and 64bit Windows. If you want to run 16bit door
|
|||
```
|
||||
|
||||
|
||||
6. Profit!
|
||||
6. Look at [Production Installation](/installation/production) for maintaining ENiGMA½ when you are ready to go live.
|
||||
|
|
|
@ -16,10 +16,11 @@ You then need to enable the SSH server in your `config.hjson`:
|
|||
{
|
||||
loginServers: {
|
||||
ssh: {
|
||||
enabled: true
|
||||
enabled: true
|
||||
port: 8889
|
||||
privateKeyPass: YOUR_PK_PASS
|
||||
}
|
||||
privateKeyPem: /path/to/ssh_private_key.pem
|
||||
privateKeyPass: YOUR_PK_PASS
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
|
|
@ -1,4 +1,25 @@
|
|||
---
|
||||
layout: page
|
||||
title: Telnet Server
|
||||
---
|
||||
---
|
||||
|
||||
Telnet is enabled by default on port `8888` in `config.hjson`:
|
||||
|
||||
```hjson
|
||||
{
|
||||
loginServers: {
|
||||
telnet: {
|
||||
enabled: true
|
||||
port: 8888
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Telnet Server Options
|
||||
|
||||
| Option | Description
|
||||
|---------------------|--------------------------------------------------------------------------------------|
|
||||
| `firstMenu` | First menu a telnet connected user is presented with
|
||||
| `enabled` | Enable/disable telnet server
|
||||
| `port` | Configure a custom port for the telnet server
|
||||
|
|
|
@ -21,14 +21,14 @@ There are a few things out of scope of this document:
|
|||
|
||||
## Setup
|
||||
|
||||
1. Enable the websocket in ENiGMA, by adding `webSocket` configuration to the `loginServers` block (create it if you
|
||||
1. Enable the websocket in ENiGMA, by adding `webSocket` configuration to the `loginServers` block in `config.hjson` (create it if you
|
||||
don't already have it defined).
|
||||
|
||||
````hjson
|
||||
loginServers: {
|
||||
webSocket : {
|
||||
port: 8810
|
||||
enabled: true
|
||||
port: 8810
|
||||
securePort: 8811
|
||||
certPem: /path/to/https_cert.pem
|
||||
keyPem: /path/to/https_cert_key.pem
|
||||
|
@ -88,4 +88,4 @@ otherwise.
|
|||
9. If you navigate to http://your-hostname.here/vtx.html, you should see a splash screen like the following:
|
||||
![VTXClient](../assets/images/vtxclient.png "VTXClient")
|
||||
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue