X-Git-Url: https://git.r.bdr.sh/rbdr/mobius/blobdiff_plain/6988a0571d5d37ea0f38ee3e4066533158f608bc..f428cd7b08e68d650d4bf669cfc618f5fab998b4:/README.md diff --git a/README.md b/README.md index 799a903..97e2575 100644 --- a/README.md +++ b/README.md @@ -1,83 +1,231 @@ + + # Mobius -Cross-platform command line [Hotline](https://en.wikipedia.org/wiki/Hotline_Communications) server and client +Mobius is a cross-platform command line [Hotline](https://en.wikipedia.org/wiki/Hotline_Communications) server implemented in Golang. + +- **Project Goal:** Make it simple to run a Hotline server on macOS, Linux, and Windows, with full compatibility for all popular Hotline clients. -[![CircleCI](https://circleci.com/gh/jhalter/mobius/tree/master.svg?style=svg&circle-token=7123999e4511cf3eb93d76de98b614a803207bea)](https://circleci.com/gh/jhalter/mobius/tree/master) -# Installation +## Installation -### Mac OS X +Mobius is distributed through a single binary. -#### Client +Depending on your platform and preferences, you can acquire the binary in the following ways: - brew install jhalter/mobius-hotline-client/mobius-hotline-client +### Build from source -#### Server +1. Install [Go](https://go.dev) if needed +2. Run `make server` - brew install jhalter/mobius-hotline-client/mobius-hotline-client +### Download pre-built release -### Linux +See [Releases](https://github.com/jhalter/mobius/releases) page. -Download a compiled release for your architecture from the Releases page -### Windows +### Docker - TODO +To run a Hotline server with a default, sample configuration with ports forwarded from the host OS to the container: -# Build + docker run --rm -p 5500:5500 -p 5501:5501 ghcr.io/jhalter/mobius:latest -To build from source, run -`make build` +You can now connect to localhost:5500 with your favorite Hotline client and play around, but all changes will be lost on container restart. -# Features +To serve files from the host OS and persist configuration changes, you'll want to set up a [bind mount](https://docs.docker.com/storage/bind-mounts/) that maps a directory from the host into the container. -* Hotline 1.2.3 +To do this, create a directory in a location of your choice on the host OS. For clarity, we'll assign the path to the `HLFILES` environment variable and re-use it. -## Usage +Then run the docker command with `-v` and `-init` like so: -### Precompiled binaries -To get started quickly, download the precompiled binaries for your platform: +``` +export HLFILES=/home/myuser/hotline-files +mdkir $HLFILES -* [Linux]() -* [Mac OS X]() +sudo docker run \ + --pull=always \ + --rm \ + -p 5500:5500 \ + -p 5501:5501 \ + -v $HLFILES:/usr/local/var/mobius/config \ + ghcr.io/jhalter/mobius-hotline-server:latest \ + -init +``` -## Compatibility +It's a good security practice to run your server as a non-root user, which also happens to make editing the configuration files easier from the host OS. -The server has been tested with: - * Hotline Client version 1.2.3 - * Hotline Client version 1.8.2 - * Hotline Client version 1.9.2 - * Nostalgia +To do this, add the `--user` flag to the docker run arguments with a user ID and group ID of a user on the host OS. -### Build from source +`--user 1001:1001` + +### Homebrew + +For macOS the easiest path to installation is through Homebrew, as this works around Apple's notarization requirements for downloaded pre-compiled binaries by compiling the binary on your system during brew installation. + +To install the server: + + brew install jhalter/mobius-hotline-server/mobius-hotline-server + +After installation `mobius-hotline-server` will be installed at `$HOMEBREW_PREFIX/bin/mobius-hotline-server` and should be in your $PATH. + +The server config directory will be created under `$HOMEBREW_PREFIX/var/mobius`. + +To start the service: + +`brew services start mobius-hotline-server` + + +## Server Configuration + +After you have a server binary, the next step is to configure the server. + +### Configuration directory + +Mobius stores its configuration and server state in a directory tree: + +``` +config +├── Agreement.txt +├── Files +│   └── hello.txt +├── MessageBoard.txt +├── ThreadedNews.yaml +├── Users +│   ├── admin.yaml +│   └── guest.yaml +├── banner.jpg +└── config.yaml +``` + +If you acquired the server binary by downloading it or compiling it, this directory doesn't exist yet! But you can generate it by running the the server with the `-init` flag: + +`./mobius-hotline-server -init -config example-config-dir` + +Brew users can find the config directory in `$HOMEBREW_PREFIX/var/mobius`. + +Within this directory some files are intended to be edited to customize the server, while others are not. + +--- + +* 🛠️ Edit this file to customize your server. +* ⚠️ Avoid manual edits outside of special circumstances (e.g. remove offending news content). + +--- + +🛠️ `Agreement.text` - The server agreement sent to users after they join the server. + +🛠️ `Files` - Home of your warez or any other files you'd like to share. + +⚠️ `MessageBoard.txt` - Plain text file containing the server's message board. No need to edit this. + +⚠️ `ThreadedNews.yaml` - YAML file containing the server's threaded news. No need to edit this. + +⚠️ `Users` - Directory containing user account YAML files. No need to edit this. + +🛠️ `banner.jpg` - Path to server banner image. + +🛠️ `config.yaml` - Edit to set your server name, description, and enable tracker registration. + + +### User accounts + +The default installation includes two users: + +* guest (no password) +* admin (default password admin). + +User administration should be performed from a Hotline client. Avoid editing the files under the `Users` directory. + +## Run the server + +By default running `mobius-hotline-server` will listen on ports 5500/5501 of all interfaces with info level logging to STDOUT. + +Use the -h or -help flag for a list of options: + +``` +$ mobius-hotline-server -h +Usage of mobius-hotline-server: + -bind int + Base Hotline server port. File transfer port is base port + 1. (default 5500) + -config string + Path to config root (default "/usr/local/var/mobius/config/") + -init + Populate the config dir with default configuration + -interface string + IP addr of interface to listen on. Defaults to all interfaces. + -log-file string + Path to log file + -log-level string + Log level (default "info") + -stats-port string + Enable stats HTTP endpoint on address and port + -version + Print version and exit +``` + + +To run as a systemd service, refer to this sample unit file: [mobius-hotline-server.service](https://github.com/jhalter/mobius/blob/master/cmd/mobius-hotline-server/mobius-hotline-server.service) + +## (Optional) HTTP API + +The Mobius server includes an optional HTTP API to perform out-of-band administrative functions. + +To enable it, include the `--api-addr` flag with a string defining the IP and port to listen on in the form of `:`. + +Example: `--api-addr=127.0.0.1:5503` + +⚠️ The API has no authentication, so binding it to localhost is a good idea! + +#### GET /api/v1/stats + +The stats endpoint returns server runtime statistics and counters. + +``` +❯ curl -s localhost:5603/api/v1/stats | jq . +{ + "ConnectionCounter": 0, + "ConnectionPeak": 0, + "CurrentlyConnected": 0, + "DownloadCounter": 0, + "DownloadsInProgress": 0, + "Since": "2024-07-18T15:36:42.426156-07:00", + "UploadCounter": 0, + "UploadsInProgress": 0, + "WaitingDownloads": 0 +} +``` + +#### GET /api/v1/reload + +The reload endpoint reloads the following configuration files from disk: + +* Agreement.txt +* News.txt +* Users/*.yaml +* ThreadedNews.yaml +* banner.jpg - make build +Example: +``` +❯ curl -s localhost:5603/api/v1/reload | jq . +{ + "msg": "config reloaded" +} +``` -# TODO +#### POST /api/v1/shutdown -* Implement 1.5+ protocol account editing -* Implement folder transfer resume -* Implement file transfer queuing -* Map additional file extensions to file type and creator codes -* Implement file comment read/write -* Implement user banning -* Implement Maximum Simultaneous Downloads -* Maximum simultaneous downloads/client -* Maximum simultaneous connections/IP -* Implement server broadcast -* Implement statistics: - * Currently Connected - * Downloads in progress - * Uploads in progress - * Waiting Downloads - * Connection Peak - * Connection Counter - * Download Counter - * Upload Counter - * Since +The shutdown endpoint accepts a shutdown message from POST payload, sends it to to all connected Hotline clients, then gracefully shuts down the server. +Example: -# TODO - Someday Maybe +``` +❯ curl -d 'Server rebooting' localhost:5603/api/v1/shutdown -* Implement Pitbull protocol extensions \ No newline at end of file +{ "msg": "server shutting down" } +```