Kether.pl Website Server

This project is the backend server for the Kether.pl website, a homepage for the Polish community-driven Left 4 Dead 2 ZoneMod-based server. It's built using Rust and leverages various libraries for web services, game server querying, and database management.

Features

• L4D2 Server Information:
  • Retrieves and provides live information about L4D2 servers, including:
    • Server name
    • Current map
    • Number of players and bots
    • Player details (name, score, duration)
  • Supports querying specific servers by IP and port.
  • Includes a hardcoded endpoint for the Kether.pl L4D2 server.
• Steam Integration:
  • Fetches Steam user data (name, avatar, profile URL, etc.) using the Steam Web API (to display to the logged-in user on the website).
  • Checks if a user owns Left 4 Dead 2 on their Steam account (a check for login purposes on our website).
• Database Management:
  • Uses SQLite for persistent data storage.
  • Manages the following data:
    • Binds: Custom in-game keybinds with author and text.
    • Bind Suggestions: User-submitted bind suggestions.
    • Commands: Server commands with descriptions.
    • Bind Votings: User votes on bind suggestions.
  • Provides RESTful API endpoints for CRUD (Create, Read, Update, Delete) operations on database entities.
• RESTful API:
  • Built with the Rocket web framework.
  • Provides a comprehensive set of API endpoints for interacting with the server's features.
  • Supports CORS (Cross-Origin Resource Sharing) to allow requests from the Kether.pl frontend (running on localhost:3000 and kether.pl).
• Security:
  • Includes basic bot detection by logging requests to common attack paths (e.g., /phpmyadmin, /wordpress, /.git).
  • Redirects root path (/) to the Kether.pl frontend.
• Configuration:
  • Uses an KISS.ini configuration file to manage settings like:
    • Database path
    • Database relative directory flag
    • Steam Web API key
• Command-Line Interface (CLI):
  • Allows querying L4D2 servers directly from the command line.
  • Starts the RESTful server service.
• Error Handling:
  • Robust error handling for database operations, Steam API calls, and game server queries.
  • Returns appropriate HTTP status codes (e.g., 404 Not Found, 400 Bad Request, 500 Internal Server Error) for API requests.
• Logging:
  • Logs suspect IP addresses and paths to suspects.log for potential bot activity.
  • Logs database errors to the console for debugging.

Dependencies

• Rocket: Web framework for building the RESTful API.
• gamedig: Library for querying game servers.
• steam-rs: Library for interacting with the Steam Web API.
• diesel: ORM (Object-Relational Mapper) for database interactions.
• r2d2: Connection pooling for the database.
• rocket_cors: CORS support for the Rocket web server.
• clap: Command-line argument parsing.
• ini: Configuration file parsing.
• colored: Terminal output coloring.

Getting Started

1. Install Rust: If you don't have Rust installed, follow the instructions on the official Rust website (https://www.rust-lang.org/tools/install).

2. Clone the Repository:

   git clone <repository_url>
   cd Kether.pl-website-server

3. Create KISS.ini: Create a KISS.ini file in the project's root directory (or it will be created automatically on first run).

   • Set the database_path to the desired location and name of your SQLite database file.
   • Set database_relative_dir to true if the database is in the same directory as the executable.
   • Obtain a Steam Web API key from Steam and set it in steam_web_api_key.

4. Run Database Migrations: Requires diesel-cli to be installed. Either through cargo install diesel-cli or your OS's package manager (if supported).

   diesel setup
   diesel migration run

5. Build and Run:

   cargo build --release
   cargo run --release -- --service

   • --service starts the RESTful server.
   • Without --service, you can use the CLI to query L4D2 servers.
   • Example: cargo run --release -- query -i 51.83.217.86 -p 29800

   Or deploy the executable: target/release/Kether_Internal_Services_Server with the database, config, and optionally a systemd-user service (put the first three under $HOME/Kether_Internal_Services_Server, systemd service requires screen to be installed). And run

   Kether_Internal_Services_Server/Kether_Internal_Services_Server -s

6. Access the API:

   • Once the server is running, you can access the API endpoints at http://localhost:3001/api/... (or the port you configured).

License

This project is licensed under the GPL-3.0-only license.