v0.6.0

v0.6.0

This release of Wilfred comes with little changes to the end-user, but quite the major rewrite when it comes to the actual code. The CLI has been more clearly separated from the Wilfred core API. Each method has been rewritten to be more consistent and each method has its own set of exceptions that it now can raise. Most of the exception catching is now done within the UI, which makes a lot more sense. There are still some changes left before we can seriously start working on an extension system but this is a good start. This release also introduces the --force command as well as the ability to reset back to default startup command. See full changelog below.

Changelog

• Added #47 Added --force/-f flags to wilfred kill and wilfred delete (forces actions without confirmation).
• Added #50 Added ability to reset back to default startup command (remove custom startup command).
• Changed Enforce 20 character length limit on server names.
• Changed #42 Major refactor, separate the CLI from the core API and rewrite some of the core methods to be more consistent. With this, the Wilfred API now has it's own set of exceptions that it raise. The exceptions are no longer caught within the methods themselves and instead within the UI (a lot more predictable and makes a lot more sense).
• Fixed #49 Fixed a bug that caused Wilfred to crash if a container stopped running between the statement that checks if the server is running and the statement that actually retrieves the log in wilfred console.