Refactoring towards a release

While tracking down some issues in some of the cmdlets, I came to the conclusion that it may be a good idea to rebuild all the scripts prior to a release. There’s a lot of missing bits and pieces in various cmdlets, which came about due to the nature of the project. Initially, a cmdlet was going to be very simple, but over time, the template became 8kb in size. From here on out, I can either keep the 8kb template and rebuild each script, or extract the necessary bits from each script and strip all comments out so each script is only the necessary bits to grab that particular set of files. In any case, one of these will be needed in order to complete the current release.

There’s also the boot functionality that needs to be fully implemented and utilized.

For the time being, BootZilla is in a ‘refactoring’ period of development. A final build is likely to be out by April 2015.

HTTPS support!

While doing some mandatory domain updates, it was decided to invest in an SSL/TLS certificate for the site, for both security and peace of mind. I’ll be changing to few minor things in the next release to utilize https for downloads from the site. Additional work is being done to make logging more useful, and will likely include the use of Awk in the next release to parse logs for errors, which will in turn give better reasons to users as to why a download may have failed or why an extraction may have ended badly (corrupt archive, for instance).