-
Notifications
You must be signed in to change notification settings - Fork 1
Plans
Gael Ribes edited this page Jul 22, 2014
·
2 revisions
This plan may become outdated at any time, I will try to keep it as updated as possible but the latest document can be viewed on Google Docs here.
The plan for our system architecture can be view on Google Docs here, don't worry it's nice and colourful!
- Responsive - Make it nice on mobile
- Should only list plugins not server mods
- Should be always online/working
- Support section/dedicated support team
- Categories
- Ability to completely customise which stats are displayed
- Responsive Graphs - Highcharts
- JSON API - Possibly REST
- Ability to sort plugins by server population or by number of servers running the plugin.
- Will probably use this template.
- System Values:
- Java Version
- Operating System
- Architecture
- CPU and # cores available (Relevant for VPS)
- RAM (Could be difficult but should be feasible)
- Plugin Values:
- Custom Plugin Values
- Plugin Version
- Version history/distribution
- Server Values:
- Server Unique ID (Untraceable to server)
- Server Mod (Bukkit, Cauldron, Forge, Glowstone, Spout, Spigot etc)
- Server Mod Version
- Server Location - Country
- Online/Offline Mode
- Player Count
- Authentication for proof of plugin ownership (DBO/Curse API)
- Kitten picture error messages
- Ability to filter displayed data
- Filter specific versions (Maybe a regex for allowed version strings?)
- Filter out specific servers, or just allow easy reporting of abuse (someone faking data)
- API Server
- Report Server - Where data is sent to from the servers
- Web Server, will communicate with API for data
- Database Server - Where the data is stored, It needs to go somewhere