A system to manage multiple different servers on the same system.
Octyne allows running multiple apps on a remote server and providing an HTTP API to manage them. This allows for hosting many web servers, game servers, bots and so on on remote servers without having to mess with SSH, using screen and systemd whenever you want to make any change, in a highly manageable and secure way.
It incorporates the ability to manage files and access the terminal output and input over HTTP remotely. For further security, it is recommended to use HTTPS (see config.json) to ensure end-to-end secure transmission.
retrixe/ecthelion complements octyne by providing a web interface to control servers on octyne remotely.
Octyne depends on two files in the same directory to get configuration from.
Used to configure the servers Octyne should start, Redis-based authentication for allowing more than a single node and HTTPS support. A reverse proxy can also be used for HTTPS if it supports WSS.
NOTE: Remove the comments when creating the file as JSON does not support comments!
{
"port": 42069, // optional, default is 42069
"redis": {
"enabled": false, // whether the authentication tokens should sync to Redis for more than 1 node
"url": "redis://localhost" // link to Redis server
},
"https": {
"enabled": false, // whether Octyne should listen using HTTP or HTTPS
"cert": "/path/to/cert.pem", // path to HTTPS certificate
"key": "/path/to/key.pem" // path to HTTPS private key
},
"servers": {
"test1": { // each key has the name of the server
"enabled": true, // optional, default true, Octyne won't auto-start when false
"directory": "/home/test/server", // the directory in which the server is located
"command": "java -jar spigot-1.12.2.jar" // the command to run to start the server
}
}
}Contains users who can log into Octyne. Use a secure method to hash your passwords as Octyne does not handle account management at the moment.
{
"username": "password hashed with SHA-256"
}