centauricloud / centauricloud Goto Github PK

View Code? Open in Web Editor NEW

15.0 15.0 5.0 518 KB

A fully open-source cloud for minecraft servers

Home Page: https://centauricloud.net

License: GNU General Public License v3.0

Java 100.00%

bungeecord centauri cloud clustering loadbalancing minecraft spigot

centauricloud's Introduction

CentauriCloud

CentauriCloud is a fully open source system to manage your minecraft server network. CentauriCloud offers an extensible module system to enhance it with your own functionality. You can easily configure every part to fit your needs.

Module system

The module system allows you to write your own modules to extend system-core functionality. You can get started with developing your own module by checking out the wiki pages.

Official modules (supported by Centauri Developer Team)

*requires Cloud Rest API to work

Rules for Pull Requests

Create clearly understandable commits
Squashing or Rebasing is forbidden
Document some complicated things, but not everything

centauricloud's People

Contributors

Stargazers

Watchers

Forkers

lordotut m0ttii weefle itztoxicgaming jimmyr57000

centauricloud's Issues

Library folder

Own folder for libraries like MongoDB

Messenger Bots

Implementing messenger bots for different platforms would be super helpful to keep track of the network. The user should be able to configure which notifications should be sent. A grace period where no messages get sent would be helpful too. At least these three messenger platforms should be supported

Discord
Slack
Telegram
Each platform should be individually configurable

Angular2 Web

We will use Angular2 for out frontend framework

Client netty impl.

Implement netty into the client

Bungeecord-Connector compatibility trouble

It seems like the connector has problems with the compatibility of the latest version of Bungeecord. The Connector cant initialize the Logger. #

Ip Black/White list

Party system

The goal is to build a flexible party system based on permissions (for premium users, etc.)

Method to read console from given server

Update templates on daemon-side

2c51ab1#diff-1cca041072514c6232b7a6359a320c35R207

Send new zipped templates and decompress

Dynamically un-/loading modules/libs with API at runtime

Packets Handling

Handle packets correctly. Yet, one packet needs to be implemented everywhere

Method to get and set content of given file

Start bungee automatically

Downloadable Modules

Index Webserver for modules, and let users download them

Update old configs without re-copy the default config

At this moment, users have to delete their config, if they want to update the master. Only re-creating creates new keys.

We have to "update" the configuration with new keys without create new code for every key/value.

Ban system

The plan is to build a central ban system supported by a database of choice

When an bungeecord connects to master send him all currently known spigot servers

Daemon

Creating a Daemon for starting up spigot servers

Implement logging

A logging implementation would be great for debugging and live systems. How far this should be taken is open for discussion.
Think the best way to do this is writing a own "Logger" module. The configuration for this module should be as flexible as possible. The user should be able to say which events should get logged and how they are logged (console, file, remote dest., etc).

Round-Robin compatibility(MultiBungee)

Implement Communication between multiple bungeecord instances

Method to get version of Cloud

Send command to server (API)

Implement Cloud-API for modules

Implement an basic api for modules

BungeeCord impl.

Implement BungeeCord-Plugin

Implement basic packets

Imlement all basic packets for server to cloud communication

Shared files improvements

Shared files would be much more useful if they were a little bit more flexible. Currently they are being copied, with the same name. This makes it impossible to have multiple plugin configurations (for example a worldedit config for a lobby template and one for a buildserver template). It would be much more useful if it was possible to specify the source and the target filename instead of the source and the target filename being exactly the same.

Unfortunately, I guess this is not possible by using properties configuration. But a JSON configuration would do the job just fine.

{
  "sharedFiles": {
    "source-config.yml": "plugins/plugin/config.yml"
  }
}

report escalation - Notify team members if a report is pending for too long
statistics - Check the statistics about your opened/closed reports

The whole system should work in cooperation with #34