Tutorial Starbound Server UI

The oldest windows OS supported by my platform is Windows XP Service Pack 3 or later.

 

Updated to version 1.2

• Added manual backup feature
• Backup will wait up to 30 seconds per locked file to unlock during backup
• Added configurable backup path
• Maximum log lines is now configurable
• Added status information area

 

Any chance to get a Update soon?

 

As the holiday activities die down I'll be testing out the UI against the latest patch to make sure everything is working as intended. I've been prototyping the headless and service versions of the program and I'm shooting to have them completed in a week or so. This will also alow me to begin development on the web version. Once I am comfortable with those the next on my list will be a Linux port. The Mac version is on hold until I can get a testing box, although I expect it will require just a few tweaks from the Linux version and should go quickly.

 

Update version 2.0: SSUI has been split into two individual programs, the Controller and the Manager.
The Controller is tasked with controlling the starbound server, collecting and storing information about the server, and relaying that information over the network or local machine to managers.
The Manager is tasked with displaying the information relayed from the controller and serves as an interface for controlling the server.

The Controller can be ran as a stand-alone program, or installed as a windows service.

I have included a FAQ with additional information about the controller/manager setup.

 

This seems well made... but the issue is theirs already 2-3 programs that do the same thing with more features and an established userbase. Maybe look into working with one of them via github instead of remaking the wheel?

 

well... i think people like having the idea they developed the program.. not "contributed" i understand the feeling that maybe perhaps why their not doing so. The initial developers who thought of that are considered the founders, and they usually get most if not all of the credit, the contributors really just... are as the name suggests. Contributors. Starrybound lacks 7 features i'd like to see in a console, and some things icers console can do that theirs cannot. The thing thats also lacking is the fact that icers console for example can also hold up against new starbound updates, instead of needing to be reworked to work with future versions. Im assuming when this big update is pushed out it will resolve alota issues with our server side, and we'll really see whos console holds up, the one that hasn't been updated for some time and will most likely function or the one that has a team of devs, that need to keep updating it continually to get it to function with newer builds?

This console here has a great idea, if they teamed up with icer i can see that console going far, and considering starrybound also made their source code available, if icer and whom ever he decides to team up with would basically invest more time in the project i can definitely see it superseeding if not holding up against the test of time when the wrapper is left unattended for awhile. Oh... and if you hold up starrybound against others... you gotta think... whos running a company thats investing alota time in this R&D for the project, and who is doing it out of personal hobby.

 

No matter what IP address i put in it tries to connect to localhost

 

True, however I prefer to write and maintain my own management system with as many or as few features as I see useful.

Thanks for pointing that out @raykazi, the underlying socket needed a manual reset to update its properties. It has been fixed in the latest version to automatically take care of that for you.

 

I agree, and most of these programs consume people because it is way to much for one person to do. Then they stop managing it because they burn out and dont delegate to helpers.

 

I don't know if I'm late here (also, I hate necro-posting), but if you want to send a "SIGINT" (Ctrl+Break) to a process, you can get the PID of it, and then pass it to SendSignal programatically.