Fully-featured ban server compliant with the new Rust (game) server's Centralized Banning feature written in Go + GORM/SQLite.

• GET /api/status - For checking if the API is alive
• GET /api/rustBans/count - For getting the registered ban count
• GET /api/rustBans/<SteamID64> - For checking for banned SteamIDs (mostly used by the game server)
• POST /api/rustBans - For adding account bans
• DELETE /api/rustBans/<SteamID64> - For removing account bans

• Secure the POST and DELETE endpoints with a token or access key;
• HTTPS support;
• Include Go test files;
• Database importing and exporting;
• Use limiter middleware just to be safe;
• Create endpoint that returns all bans (might wanna implement pagination tho);

• There's a Postman collection available for importing here, which contains basic tests to validate the API's operation. (open the link and use Ctrl + S to save the file)

GET /api/status shall always return { "status": "ok" } with status code 200.

GET /api/rustBans/count returns the JSON-encoded ban count. In case of internal errors, the API returns 500 and the JSON-encoded error.

GET /api/rustBans/<SteamID64> first validates the provided SteamID, returning the status code 400 and the JSON-encoded error message Invalid SteamID64. if it's not valid. Otherwise, it returns the JSON data as specified in the Rust wiki with status code 200 if the SteamID has been found. If it wasn't, it returns 404 with the JSON-encoded error SteamID64 not found.. In case of internal errors, the API returns 500 and the JSON-encoded error.

POST /api/rustBans requires a JSON body to be sent through, using the same format as described in the Rust wiki:

{
    "steamId": "76561198060722078",
    "reason": "Too handsome",
    "expiryDate": 1609698084
}

The provided SteamID64 is also validated, returning the status code 400 and an error message if the validation fails. It then checks if the ban already exists. If so, it gets updated and SteamID64 updated. is returned with status code 200. Otherwise, the record is created and the API returns the JSON-encoded message SteamID64 banned. with the status code 201. In case of internal errors, it returns 500 and the JSON-encoded error.

DELETE /api/rustBans/<steamID64> also validates the provided SteamID64, returning the status code 400 and a JSON-encoded error if validation fails. If it's valid, the status code 200 is returned with the JSON-encoded message SteamID64 unbanned. if the SteamID has been removed successfully. If the SteamID doesn't exist, the API returns 404 with the JSON-encoded error SteamID64 not banned.. In case of internal errors, it also returns 500 and the JSON-encoded error.