Status Update - 9/2/2016



  • Another month, another large amount of work.

    The last 2 weeks have been filled with a lot of work achieved and a lot of decisions being made. We have continued to work on the new daemon, and are much closer to it being in an alpha state for functionality testing. We have been able to deploy the daemon to our dev version of the panel and validate that it at least functions, which is a great start, but we still have a lot of work to do before it is ready.

    We have created 2 milestones that will demonstrate when we expect the alpha release to occur:
    https://github.com/PufferPanel/PufferPanel/milestone/14
    https://github.com/PufferPanel/pufferd/milestone/1

    Both of those we hope to be ready by the end of this month, and so we are excited to see what the new daemon will be doing for us.

    The major focus of the new daemon is an emphasis on flexibility as a whole, and so the core design is built around each server doing what they need, not a generic "end-all" solution that Scales was using. Each server uses a configuration file to drive how it functions, adding much needed flexibility to servers. Each server type is defined from those templates, which is copied (for now) when a new server is created. This means that Server A can define extra java arguments or even use a different version of Java compared to server B. The panel is going to get updates that allows for administrators to control this data, but this may not be done with the first release.

    We have temporarily removed the tracking of the stats of a server as it is an extra feature of the daemon, and is not a focus on the first release. You may notice additional features missing as the new daemon does not currently handle those yet, but we will be working to restore what functionality that we can as the daemon progresses.

    We are very pleased with how the daemon is progressing, and hope to keep this daemon for the foreseeable future. The language that we chose to use does not support a traditional plugin architecture, but we have found that the design we have chosen allows for enough customization to the servers to be acceptable for most use cases. We will instead have the UI build on top of this and expose that extra functionality that is sometimes needed, and using the daemon's API to achieve that.

    A good example would be the auto-accept EULA for MC servers. We would not be coding this on the daemon itself, but having the panel determining this on starting/installing the server (as installing is now done via the user and not via the server creation, a huge change as well), and prompting the user to accept it. When it would, it would upload the eula.txt to the server so that it "accepts". That would be how the daemon could indirectly support it, but not require any special code on the daemon to handle it. Plugin management could follow along with that, being driven by the panel's UI. This is our plan, but time will tell to determine how it eventually is implemented.

    A few key changes to recap in the event it was not mentioned in previous updates:

    • No docker support on initial release. We need to look at the docker implementation from the ground up and design the daemon to handle this correctly, instead of how Scales did it (which was hackily and poorly done). The current design of the daemon should support us adding this in, but we want to make sure we do it correctly the first time.
    • No IP/port allocation on the daemon yet. This is something we are still deciding how to handle correctly, as it should be up the daemon to properly manage this, but we have yet to decide on a way which is both user and admin friendly to manage.
    • SSL is no longer required on the daemon. The new daemon will not require HTTPS/SSL in general, but if you do not use it, then something is wrong. OAuth2 SHOULD use SSL, and so is something that should be enabled when you configure the node. We did notice that SSL caused problems at times, and so the new daemon has it configure-able, but if you disable it, we cannot offer support for it.
    • The panel now handles talking to the daemon. One significant change is that now most of the panel functions are instead being handled by the panel itself, which talks to the daemon. This means that now, the user talks to the panel for most functionality (the console being one of the few direct daemon calls). We chose this path because it simplified the OAuth2 implementation, and also helps fix the plague of issues where the SSL was involved in talking to the daemon. The daemon API is still publicly accessible, but now users do not talk to it directly when they use the panel.


  • Finally an update..



  • @falceso said in Status Update - 9/2/2016:

    Finally an update..

    Considering I have done a post like this once a month.... thanks for the very rude "support".



  • Don't listen to them. If they cared then they would see all the stuff you have worked on constantly in the dev branch on github.

    Aside from that point, I will make sure to provide feedback in the form of issues on github when I notice things to aid in getting pufferd out of alpha



  • @LordRalex Pls man, ignore these people, because, exept someone, anyone here estimate all the programmers behind this panel



  • @LordRalex said in Status Update - 9/2/2016:

    @falceso said in Status Update - 9/2/2016:

    Finally an update..

    Considering I have done a post like this once a month.... thanks for the very rude "support".

    I meant that in a good way. I'll go rephrase it I guess...

    Yay! Now we have less stress when people complain about ssl.



  • @MattBSG said in Status Update - 9/2/2016:

    Don't listen to them. If they cared then they would see all the stuff you have worked on constantly in the dev branch on github.

    Aside from that point, I will make sure to provide feedback in the form of issues on github when I notice things to aid in getting pufferd out of alpha

    I did not leave a bad comment it was "Finally we have an update to fix problems. "



  • Everyone please move your topics about me to a private message. As that is not required for this thread. You may post your be confidence about the development here.



  • Looking forward to the releasing of a completely new pufferpanel in future.
    Thank you for the hard working:3
    (Sorry,my English is poor)



  • Thank you for keep informated all us about deveploment ^^, a question, all stuffs make for now are upgradable to this vesion?



  • @xion87 said in Status Update - 9/2/2016:

    Thank you for keep informated all us about deveploment ^^, a question, all stuffs make for now are upgradable to this vesion?

    We do not have an update system right now, because the new daemon is vastly different in how it operates compared to scales.

    I hope to get one, but I don't think it's going to be viable really.



  • @LordRalex Maybe it's possilbe by using the github files...
    It could be possible to make a file that contains the version of the actual version, and if the github one is higher, it clone the repo and do it's things...
    But that's just an idea...


Log in to reply
 

Looks like your connection to PufferPanel Community was lost, please wait while we try to reconnect.